4.0.6 "Not connected"

[noospheer]

Not able to connect to any server in 4.0.6.... Same issue in Ubuntu 22 and Windows 10

Clean install, standard wallet, recovering from seed. Standalone 4.0.6 in Windows 10, and running ./run_electrum_nmc in Ubuntu 22.

It just sits with big red circle, saying "Not connected", in both instances, regardless of automatic server selection or choosing one directly. There's no network traffic either, so its not as if its syncing in the background. Please advise.

edit: I briefly saw it say "Syncing 0/30" but then went back to "Not connected"

[noospheer]

It auto-connected for a moment before dropping. Terminal printed this:

W/i | interface.[46.229.238.187:57002] | disconnecting due to GracefulDisconnect(RPCError(-101, 'excessive resource usage'))

[JeremyRand]

Hi, thanks for the bug report! That sounds like it's due to a combination of:

1. The checkpoint is old, so it needs to download a lot of headers.
2. Namecoin headers are much larger than Bitcoin headers.
3. Probably the default rate limits on ElectrumX don't account for the bigger header size.

I'll look into fixing this, but it won't happen in the next month (due to an announcement incoming shortly). You could maybe try using Tor and see if that helps, but it might not.

[noospheer]

Thanks for reply -- re your first point, this implies that it's downloading headers in the background? I don't see network traffic though.

What would be the most recent version that would not have this issue?

[noospheer]

Also, is there an archive where we can download an older version that doesn't have this issue?

edit: same issue with the AppImage 4.0.6

[noospheer]

~ bump ~

[victoirechan]

在 2024-07-05 03:49:34，"noospheer" @.***> 写道：

~ bump ~

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[JeremyRand]

Thanks for reply -- re your first point, this implies that it's downloading headers in the background? I don't see network traffic though.

The error message you pasted indicates that there was network traffic. You wouldn't be getting that error from an ElectrumX server if there weren't a connection to an ElectrumX server.

What would be the most recent version that would not have this issue?

I don't think we've bumped the checkpoint for a while (I'll do this before branching the next release), but for issues caused by an outdated checkpoint, naturally things would be monotonically better with newer versions.

edit: same issue with the AppImage 4.0.6

Yeah there's no reason why the AppImage would behave differently from any other binary produced by the same tag.

[JeremyRand]

Could you check what height you're currently synced to? I'd like to look at whether perhaps any of the nearby block headers are unusually large, which might inform an ElectrumX patch.

[noospheer]

Network: Blockchain: 586655 blocks