Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.0.6 "Not connected" #375

Open
noospheer opened this issue May 13, 2024 · 4 comments
Open

4.0.6 "Not connected" #375

noospheer opened this issue May 13, 2024 · 4 comments

Comments

@noospheer
Copy link

noospheer commented May 13, 2024

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
Copy link
Author

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
Copy link
Member

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
Copy link
Author

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
Copy link
Author

noospheer commented May 16, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants