Problem:
Some wallets stop functioning because their IP is banned by the network. Occasionally after a fork, the old client version get banned because they are on an incorrect chain. When they can’t sync, they can’t function.
Solution:
Add connections manually within the clients.
If you are experiencing a lack of connections, in an old or newly installed client simply follow the instructions below:
From the File > Settings menu, ‘Open Wallet Configuration File’
The main wallet file called wagerr.conf file will open. Copy the following lines to the bottom of the wagerr.conf text file.
Copy:
addnode=139.99.99.168
addnode=sg.wagerr.com
addnode=la.wagerr.com
addnode=ny.wagerr.com
addnode=nl.wagerr.com
addnode=au.wagerr.com
addnode=jp.wagerr.com
To the wagerr.conf text file, so it looks like:
*Each addnode address should appear on a separate line.
Leave any other data in place.
Save the wagerr.conf file
Restart the client…
After some time you will start to see connections from the seeders on the network.
Once the blockchain is fully synchronized, please remove the addnode lines. They are not required anymore (as you have active connections now). Removing the addnodes lines will free up slots to other newly connecting peers on the network.
When you remove the addnodes, remember to save the wallet.conf file and restart client for changes to take place.
-
Wagerr Home: https://wagerr.com
Wagerr Discord: https://discord.gg/tkcXS34
Wagerr Telegram: https://t.me/wagerrcoin
Wagerr Github: https://github.com/wagerr/wagerr/releases
Wagerr Electron GitHub: https://github.com/wagerr/wagerr-electron-app
Wagerr Twitter: https://twitter.com/wagerrx
Wagerr Facebook: https://www.facebook.com/wagerr/
Technical Support: support@wagerr.com
Comments
0 comments
Article is closed for comments.