if you experience connectivity issues with Daedalus there is a work around by adding working peers to the config file. I wrote a short tutorial how to solve the problems step by step:
If you are not sure yet who to delegate with, check out our Germany based stake pools Hermes (HRMS) and Hermina (HRMA).
Please let me know if there is anything unclear with the guide,
Worked for me, thanks a lot @wunderbaer
Didn’t stay in sync for long though… Might go through the procedure again later…
try restarting it before changing peers again
That did it, I was able to change my delegation, thanks again!
Saved me time! Much Thanks!!
Excellent post! Fixed my Daedalus wallet connection problems - Thanks!
I tried that and am still not able to reconnect. Been 2 days now
First try simply failed to connect. Second try is stuck at 7%.
Third try gets to 99% and then stalls.
Fourth try finally got it synced!
Great post… Didn’t work though. I made sure the JSON was formatted correctly. Tried it with some of the IP’s and ID’s, other times with all the listings… Daedalus just kept bouncing between ‘Connecting’ and ‘Disconnecting’… I gotta’ say; I know this is a ‘testnet’, but the way IOHK just leaves us hanging with this bunk ‘wallet’ issue speaks volumes… It’s kinda’ like they don’t give a sh… I don’t hear anything official from IOHK. Wasn’t a fix supposed to be released on the 29th? SOS…
This is not actually a wallet issue. The connectivity issues are with the underlying Rust node.
The reason this has not been resolved sooner is that engineers (who had worked really hard to deliver this thing) were on much deserved leave.
My understanding is that this is being worked on.
jormungandr-config.yaml is a YAML file. The JSON format is but a proper subset of YAML format. But jormungandr uses the YAML format parser to read the file, so it’s perfectly safe to reformat the whole content of a file as a proper YAML:
- format: plain
- address: "/ip4/184.108.40.206/tcp/3000"
- address: "/ip4/220.127.116.11/tcp/3000"
- address: "/ip4/18.104.22.168/tcp/3000"
- address: "/ip4/22.214.171.124/tcp/3000"
- address: "/ip4/126.96.36.199/tcp/3000"
- address: "/ip4/188.8.131.52/tcp/3000"
- address: "/ip4/184.108.40.206/tcp/3000"
- address: "/ip4/220.127.116.11/tcp/3000"
- address: "/ip4/18.104.22.168/tcp/3000"
In this form, inserting peers from the https://adapools.org/peers page will be as easy as copy+paste the fragment below
This, would be a Royal improvement!
On top of this (while waiting for new Daedalus - Rewards version release), you can get the latest version of Jormungandr from:
Search and download the correct version for your OS (https://superuser.com/questions/173788/how-to-find-the-architecture-of-os-installed). In my case, it was windows-msvc:
Unzip it and replace the next files in the installation folder of “Daedalus - Rewards v1” (for Windows: “C:\Program Files\Daedalus - Rewards v1”):
Don’t forget to make a backup of the installation folder first, in case it doesn’t work.
Adapools made it easier:
We updated the tutorial as well and added the information how to update the node + wallet backend! Plus you can find another peer at the very bottom that might not be as overloaded as the adapools ones (at least for now)
I tried this to fix just a sync issue and now my Daedalus ITN does not work at all. No connections at all.
I’m on a Mac running the latest Catalina. The first problem I had was permissions on the file to change it. Then I had an ownership issue. Next I had the same problems right up the file system to all enclosing items. Changed all those. Now it does not work at all.
This is too complicated and too time consuming it is certainly not beta quality software.