it’s works!
Hi everyone, please refer to this guide here: IOHK statement: connecting to network issue and if the problem still persists, please send your log files to the team at https://daedaluswallet.io/faq/
1 Like
Thanks. For the link to FAQ. My problem was that I was always starting my wallet using the file Deadalus.exe then I found the file (in Total Commander) Deadalus.bat and started from there (I think as an Administrator) and finally my wallet launched and synch for the first time.
Please make sure to use the .bat file. The short cut created in Windows would use the .bat file.
Make sure that the computer clock time is matching with the internet time. As posted in another thread, I had trouble setting Internet Time in Windows 7 as I always got Timeout Errors.
What I did was to manually set the Time to match with the time shown in my mobile phone i.e., iPhone in my case. After this setting, Daedalus Wallet connects to the network without any issue.
Nowadays, before starting Daedalus .bat file, I always make sure that the Windows time is matching with the time shown on the mobile phone as the phone shows the network time.
Hope it helps.
Sorry, forum team: but if you want to create a (supporting) community why you refuse to listen to them? Do I talk to brick walls?
I mentioned several times in multiple forum threads and chat channels this confusing thing with the pinned exe in the task bar instead of the bat start script on the desktop.
I wrote this Daedalus Wallet Stuck on “Connecting to Network” because I want to help and support. But after all this repeated, the same issue reporting users, and all our answers, I would say it’s finally time to simply add this 7th paragraph to the Daedalus FAQ. (or is it immutable in a blockchain?)
We all want that as most as possible new members of the Cardano community have a positive first impression. So let’s do it!
3 Likes
I called my internet provider and had them open port 8090 for me, then I
restarted my computer and opened the wallet and left it overnight, when I
checked it in the morning it was open and my ADA we’re there, I immediately
took them out and sent them to an internet wallet bc I don’t trust Daedalus
anymore.
Well I created an account on this forum JUST TO THANK YOU! I’m listening…in fact I had to listen twice as I forgot the first time what your post had said ( about using the bat instead of the exe ) …thanks so much!!!
–now to make sure to UNPIN that darn exe file so Im not back here again in a couple weeks!
1 Like
I followed every suggestion on this thread without success. Here’s the log:
[node.worker.security:WARNING:ThreadId 554] [2018-01-09 00:11:35 UTC] self: could not choose suitable alternative from [NodeId 13.228.52.235:3000:0,NodeId 13.229.193.102:3000:0,NodeId 13.250.124.4:3000:0,NodeId 52.196.16.55:3000:0,NodeId 52.196.113.16:3000:0,NodeId 52.198.222.173:3000:0,NodeId 13.114.169.119:3000:0,NodeId 13.115.1.223:3000:0]
[node.worker.security:ERROR:ThreadId 554] [2018-01-09 00:11:35 UTC] self: enqueue instruction EnqueueAll {enqNodeType = NodeRelay, enqMaxAhead = MaxAhead 1, enqPrecedence = PHigh} failed to enqueue message MsgRequestBlockHeaders Nothing to forwarding sets [[NodeId 13.228.52.235:3000:0,NodeId 13.229.193.102:3000:0,NodeId 13.250.124.4:3000:0,NodeId 52.196.16.55:3000:0,NodeId 52.196.113.16:3000:0,NodeId 52.198.222.173:3000:0,NodeId 13.114.169.119:3000:0,NodeId 13.115.1.223:3000:0]]
[node.worker.subscription:NOTICE:ThreadId 564] [2018-01-09 00:11:35 UTC] subscriptionWorker: lost connection to NodeId 52.198.222.173:3000:0 Exceptional (TransportError ConnectTimeout "Timed out")
[node.worker.subscription:NOTICE:ThreadId 564] [2018-01-09 00:11:35 UTC] subscriptionWorker: subscribing to NodeId 13.114.169.119:3000:100:
Firewall? Are you letting the wallet communicate to the internet?
Yes, it can communicate to the Internet. I also opened the router 8090 port. I was able to receive transfer days ago. So the wallet works fine for you?
Yup, but every time I run the wallet I need to sync my internet time (because my computer clock runs slow) perhaps you need to do this again?
I’m on a Macbook Pro. I’m manually syncing time, but nothing.
Best follow @IOHK_Laurie’s advice,
I tried the following without success:
- Sync clock with NTP server
- Open port 8090 for inbound connections, tested and works
- Test with telnet connecting to nodes with port 3000, also working fine
Thanks.
I, too, had tried everything. Put holes in my firewall, turned off firewall, used and turned off my VPN. Nothing worked. UNTIL I changed my VPN to ExpressVPN (away from Cryptostorm) and voila! Suddenly it was connecting to the network. Maybe my ISP was blocking.
I experienced this issue tonight. Daedalus was working fine. When I added a wallet via recovery phrase, it appeared to hang with a spinner.
I restarted Daedalus, and it said Connecting to network...
I tried
- Syncing clock
- Restarting the computer
- Delete open.lock file in wallet-1.0
- Delete AppData/Roaming/Daedalus/Logs
None of them worked.
The problem was that cardano-node was not listening on localhost:8090. From the log, it looks like Daedalus was desperately trying to connect, but connection was refused.
Finally I removed DB-1.0, Daedalus was able to show that cardano-node is syncing (from 0 
) but at least that means there is connection between Daedalus and cardano-node.
Syncing at 40% now. I will report back if the wallet works after the full resync.
Now both of my wallets are stuck on “Connecting to Network” after they worked fine for a month. I am using Mac OSX 10.13.2 on both my laptop and iMac. Using Daedalus wallet 1.0.3619 on both machines as well. I don’t know why 2 wallets would work correctly for a month and then stop. This is unlike most previous problems/fixes.
Resynced. My wallet works again.
Good description
and exactly what I noted two days ago and tried (or plan) to replicate it.
Before I never hadn’t problems to add an existing wallet via recover phrases.
As @ScotterMonkey continuously asked if the original wallet name matters, I did a test with a consciously different name. Then it happened with the infinite spinner.
Since then I hadn’t time to resync, and replay this scenario, but I already can confirm that restoring the wallet with a different name worked fine. It also worked after this infinite loop and terminated Daedalus app.
Hmmm. My first wallet is named “Test Send” and the wallet I added via recovery phrase is named “test2”.
To be fair, I don’t know if the spinner would go away if I had waited longer. @ScotterMonkey did mention recovery takes ~15 minutes.
It would be helpful if cardano-node and Daedalus can give rescan progress, if that’s what they were doing.
1 Like