It is important to have a good number of connections when working with a cryptocoin wallet. By hovering your mouse over the bar icon the number of connections is shown. At some point (this is rare) you may experience the problem where you start up the wallet and can’t seem to get connected to any peers. When running multiple wallets you may experience some wallets getting a great many connections while others have trouble retaining enough.
If you can’t get any connections your not going to be able to send or receive any transactions or update the block chain. If you have just a few you might experience troubles staying synced with the block chain or have a higher orphan rate. Although an orphan on a PoS block won’t remove the coin weight or the reward you could earn, it can be an issue on a popular PoS coin where the block reward is mostly capped out by the time the block is minted and the difficulty to mint a block is very high. (Most PoS cryptocoins have a block cap mostly for inflation control and to encourage smaller blocks for better health of the block chain)
Occasionally when mining cryptocoins you may experience getting locked out where the other nodes appear to drop you one by one. (I’ve mostly experienced this while solo mining with smaller less popular coins.)
Based on my experiences heres a list of a few things to try if you can’t get any connections:
- Restart the wallet
- Restart the wallet and turn off UPnP
- Shutdown wallet and wait 24 hours and restart – (most bans last 24 hours)
- Shutdown computer and router and get a new public IP
- Shutdown wallet and delete the file “peers.dat” file in the hidden directory (located under the home directory on Linux)
- Post a request on a forum for someone to list some “peers”. Use “addnode” in the debug window to add these peers or put them into your configuration file. You can find the name of the configuration file by looking at the output of the “command line options” detail listing under the debug window. Check for a -conf=<file> listing with the default showing the name of the file.
For increasing connections:
- Try turning on UPnP
- Restart the wallet
- Shutdown and delete “peers.dat” as above but maybe first save any IP addresses of current peers. (You can find information on current peers with “getpeerinfo” in the debug window)
- Find a public listing of current peers and use “addnode” in debug window, or the configuration file to add them.
If you want to limit the number of connections you can pass “-maxconnections=<n>” when starting the wallet or add a line like “maxconnections=<n>” to your configuration file. (Replace <n> with a number like 50 or 70 or whatever)
A large number of fast connections are best both for your wallet to properly function and for the peer to peer network as a whole. Usually with most popular wallets you will seldom have issues and if your more of an investor that doesn’t deal much with earning interest from PoS you might not gain much from reading this post.
With the large number of cryptocoins being issued there is also the chance that the port of a new cryptocoin that your mining conflicts with the port of an already existing cryptocoin on your computer. You can fix this issue by setting the port in the configuration file with “port=18777” or any other free port number. This should allow both wallets to work properly.
However, this can cause issues depending on the software and cause trouble getting connections for the wallets that share the same default port. If you need to restart the router to get a new public IP because one of the wallets has no connections, the order in which you restart the wallets can make a difference. Try starting the wallet that you have changed the port away from the default port first. (or maybe the other way around?). It can be frustrating to restart everything and wind up with a wallet that won’t connect afterward especially where it takes a long time to get everything going again.
I hope this is helpful to everyone and if there is some details or other tips you can think of please free free to post comments below.