Hi,
I’m new to this so no idea what I’m doing at the best of times regarding wallets etc.
I’m using the 4.05 Mainnet and it’s just hanging on ‘connecting to network’ node is not responding or syncing.
Any ideas on how I get it to connect please that doesn’t involve code!
I’m running it on a Mac.
Cheers
Hi!
So modifying config files (manually or by a python script) is considered as code modification in your case?
Yeah, that last sentence was pretty much hieroglyphics to me.
Thanks anyway, I’ll give it a bash.
@laplasz gave you the best solution. Of course you could just wait but it would defeat the purpose of “getting it to connect”…
Yup, think I’ll wait, no idea what I’m doing.
it is worth to spend some time with it… at least you can get support here for any steps to complete…
Do you have a HW wallet? If not, please consider getting one & here is why.
If you already have one, you could connect it to ADALite.io - no blockchain sync is necessary. You can delegate from ADALite as well. Be careful though, they only offer to delegate to their own pool. I’d naturally recommend an approach where you have a good return for your ADA and at the same time “Make the world work better for all”.
Yoroi is also a good choice - here is an overview about it comparing to Daedalus:
Same, I’m using daedalus 4.1.0 and it just seems to lose connection at 94.61% then starts syncing again and loses connection and syncs and loses etc. It’s been 4 days… I did all relevant help menu items and still nothing. Except when I reinstalled it, it synced from 0 to 94.61% in 8 hours. But now it’s on the sync and connection loss cycle again. Sent a support ticket finally after navigating all the technical self help routes.
If it’s a connection issue, it’s hardly on Daedalus but more likely on one of the cardano-node instance, more probably the one you connected to. Could be hardware, could be software, but in any case it’s not on the wallet part.
And by the way there are at least 8 IPv4 addresses behind the default IOHK node domain name, sometimes one of them does not work as expected, that’s why in some cases a simple restart of the software can resolve the issue, or make it appear to be random.
In case you want to verify that, and validate or invalidate this hypothesis, you could temporarily bypass DNS resolution:
topology.yaml file on Daedalus directory.relays-new.cardano-mainnet.iohk.io and replace it with any of these IP addresses: 18.133.108.207, 18.159.8.231, 3.9.116.228, 18.130.187.168, 3.13.80.218, 3.126.150.220, 3.129.199.184 or 204.236.187.238
topology.yaml file back and consider adding more (reliable) nodes to your conf.To get IP addresses for relays-new.cardano-mainnet.iohk.io
$ nslookup relays-new.cardano-mainnet.iohk.io
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: relays-new.cardano-mainnet.iohk.io
Address: 3.129.180.95
Name: relays-new.cardano-mainnet.iohk.io
Address: 3.23.246.240
Name: relays-new.cardano-mainnet.iohk.io
Address: 18.133.43.175
Name: relays-new.cardano-mainnet.iohk.io
Address: 50.18.12.114
Name: relays-new.cardano-mainnet.iohk.io
Address: 18.158.165.66
Name: relays-new.cardano-mainnet.iohk.io
Address: 18.159.90.166
Name: relays-new.cardano-mainnet.iohk.io
Address: 3.13.149.172
Name: relays-new.cardano-mainnet.iohk.io
Address: 18.132.143.123
And as it has been said previously, if you don’t want to trouble you with a local blockchain instance, you might want to opt for a light wallet instead.
Nope, no lite wallets. I have too many and I know full node is where its at. I’m gonna learn to do this. It was 3am I had to sleep. But it’s on baby. I’m not going to sit and collect any more dust while technology escapes my comprehension. This was very extensive but am able to understand what you wrote here.
I will return with my results. Thank you, Ralph!
EDIT: forgot to mention. i sent the ticket using daedalus’s help menu that pops up during the issue. they have the logs i sent them, that they requested. but I will try this in the mean time and let them know asap if i fix it on my own. there’s still the issue of syncing not completing as well.
Hehe, great mindset 
feel free to PM if you need anything…
Raph! So sorry I haven’t replied. The system said I was too noobish still and capped my responses.
Update. I have not had to dive into this walk through just yet. Support informed me it was 8GB I needed. I had 4, apparently I’m blind. lol. So I installed an 8GB card today and we are in business, brother! Might still do this walk through just to speed it all up even more anyway.
Now I can use a browser while daedalus is running. Before it was not responsive much at all.
Also going to swap my low rpm drive for an SSD.
Thank you, Raph. You’re help has also informed me of other aspects I need to consider on my journey here and to always ask questions when I’m stuck. Goodvibes always. Cheers!
Ok, great then. If you ever need to check on available and currently used RAM, you can do
$ free -h
For disk space usage
$ df -h
And SSD are a good choice but do not forget to follow usual good practices to limit wear-off and thus, improve their life expectancy and performance. For instance SSDOptimization - Debian Wiki
Hi, I am having the same problem on one machine (with an AMD proc) but not the other machine (with an Intel proc). Not sure if its a proc issue but the above workaround is not hieroglyphics to me.
Give me a few days to troubleshoot and I will post a reply one way or another.
Ok, so I edited the topology file that this link suggested and while that did get the mainnet to sync faster with the added IP’s, my wallet still was not syncing.
What ended up working for me was to first uninstall Daedalus Mainnet then delete the following folder after uninstall:
C:\Users\USERNAME\AppData\Roaming\Daedalus Mainnet
I noticed that if you just uninstall and reinstall it was still aware of my wallet. Deleting this folder after uninstall and then reinstalling worked properly.
Just had this issue happen with 4.3.1, this fixed it, thank you!