Difference between revisions of "Common support queries"
Jump to navigation
Jump to search
Dgb chilling (talk | contribs) m (→I can't connect to any peers, and cannot sync in Android / iOS: Updated header) |
Dgb chilling (talk | contribs) |
||
Line 23: | Line 23: | ||
addnode digihash.co add | addnode digihash.co add | ||
addnode digiexplorer.info add | addnode digiexplorer.info add | ||
− | addnode | + | addnode explorer-1.us.digibyteservers.io add |
addnode digibyte.host add | addnode digibyte.host add | ||
addnode dgb-peer.nownodes.io add</pre> | addnode dgb-peer.nownodes.io add</pre> | ||
+ | |||
+ | When entering these in, it will not give any "Success" or similar message. No response means it worked, and you should then be connected to that peer. |
Revision as of 20:36, 9 March 2020
I can't connect to any peers, and cannot sync in Android / iOS (Stuck at 5%)
This is likely a DNS issue caused by a lot of budget / freely provided home routers.
You want to do the following steps:
- Turn off your WiFi on your phone
- Power off your device
- Power it back on while connected to JUST mobile-data such as a 3G / 4G data connection
- Fire up the DigiByte mobile app and wait for the syncing to begin
- Once syncing has begun, you can re-join your WiFi
You must do these steps in this order so that when your phone powers on, it asks your mobile-carrier for DNS. Often times home routers will keep providing stale DNS entries to devices such as Cellphones on WiFi, meaning even if you reboot your phone while on WiFi you still won't have much luck.
Why do I have no connection to peers in DigiByte Core?
You likely have a firewall blocking connections, or a DNS issue. You can try bringing up the Debug menu and entering:
addnode seed1.digibyte.io add addnode seed2.digibyte.io add addnode seed3.digibyte.io add addnode seed.digibyte.io add addnode seed.digibyteprojects.com add addnode digihash.co add addnode digiexplorer.info add addnode explorer-1.us.digibyteservers.io add addnode digibyte.host add addnode dgb-peer.nownodes.io add
When entering these in, it will not give any "Success" or similar message. No response means it worked, and you should then be connected to that peer.