Problem
Daedalus is displaying a 'Connecting to Network...' message.
Cause
The 'Cannot Connect to Network' message can be caused by a number of problems. See the list of solutions below and their causes for more details.
Solution
1. Check that your internet connection is active.
3. Wait a few minutes. Often network issues are temporary, if you wait a few minutes the issue may get resolved, if nothing has improved then you will see the "Having Trouble Connecting to the Network?" message and a link prompting you to open a support ticket.
4. Reboot your machine.
5. Reboot your router.
6. Check "Daedalus.exe" and "cardano-node.exe" are listed in the Windows firewall (Windows Only)
7. Blockchain storage consolidation stops, crippling Daedalus
8. Machine clock out of sync with Cardano network
9. Cardano network blocked by ISP
10. Windows Defender blocking connection (Windows only)
11. Flush DNS Cache (Windows only)
See other Known Issues
Comments
7 comments
How about some academic research on the importance of a working wallet? Your competitors don't have this issue. Do you realize how sketchy this is?
I have a Mac OS, reinstalled my wallet but the problem didn't go off. :-(
Can never work since 2017!
Been updating to so many new releases for OSX, but problem persist - cannot connect.
Emailed the log, but not sure will ever get a reply.
I found that if my primary DNS setting was pointing to my local DNS, which at the time was down, it would just continue trying to "connect to network"
(Internet worked fine, just not Daedalus)
My secondary DNS setting was Google's public DNS (8.8.8.8)
When I changed my primary DNS (Windows 10, Network Settings, IP4) back to something public, like googles 8.8.8.8 then it would connect just fine.
Also probably worth doing an IPConfig /FlushDNS if you make a change.
Ray Delaney, Thanks for sharing, I have passed this on to our product team in case we can use it for product enhancement.
Unfortunately I had not found Ray Delaney's comments which would have pointed me in the right direction, and instead stumbled upon the same solution for my own slightly different problem.
After dealing with the "Connecting to Network" black hole for YEARS I finally stumbled upon a solution that works quite solidly and repeatably. I have not received that message since doing this, except when I changed back to test the fix. The magical fix is:
Change your primary DNS server to something large and public, i.e. outside your LAN.
That is all. Seems arbitrary and unnecessary, as DNS *is* working and all other network functions are operable (web browsing, ssh, a dozen other wallets all work fine, etc.) This one step, however, has created a solid connection to the Cardano network.
Of note:
I did not reinstall the wallet to get it to work.
Windows Defender was never running.
Windows Firewall was never enabled.
Running as administrator did not help.
Flushing my DNS cache did not help the situation.
I did not have to delete lock files or mess with file structure at all.
The platform was Windows 7 x64 hosted in a VM in ESXI 6.
Also tested on a bare metal Win7 install that previously did not work (internal DNS server in that case was a Linux Bind server.)
My primary DNS was set to the router, which acts as a DNS forwarder. Changing it to a large public server worked almost immediately. I used 1.1.1.1 which is Cloudflare's (thanks to CF!)
So again, the magical fix for Daedalus (for me) was to change my primary DNS server to 1.1.1.1, and then Restart the node (in Daedalus Network Status panel.)
This was tested by:
- Change my primary DNS back to 192.168.1.1 (secondary DNS remained the same, Comcast Biz DNS server 75.75.76.76)
- Flush DNS cache (ipconfig /flushdns)
- Restart node
- Observe no Cardano network connectivity for ~5 minutes. Cardano Node Status showed in red text "message: ECONNRESET code: ECONNRESET" (makes no sense for a DNS-related issue?)
- Change primary DNS to 1.1.1.1
- Restart node
- Observe near-immediate connectivity to Cardano network
Hope this helps someone out there improve their Daedalus experience!
E
DdzFFzCqrhsfSESrFPNWtSLzrr6wSnUaX6CmMsHDDQBKr6dm8yYS9gokKJs7sAmrknLwXJwSdaoYmbLuJUgiazdkQhNanT2pBBHZ98UF
@Eric Henley Thanks for your insights. This error causes a lot of trouble for the community. If your suggestion is a magic bullet then you have done everyone a great service. I'm going to pass this to our QA department to see if we can check it's applicability to all OS and situations.
Please sign in to leave a comment.