Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clients older than 3.3.0 can no longer connect/synchronize. Users must upgrade.

See original GitHub issue

using version 3.1.3 in TAILS …upon opening the wallet it states there has been an error…and it won’t let me report it automatically. The manual error is:

Traceback
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/electrum/util.py", line 794, in run_with_except_hook
    run_original(*args2, **kwargs2)
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 985, in run
    self.wait_on_sockets()
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 967, in wait_on_sockets
    self.process_responses(interface)
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 626, in process_responses
    self.process_response(interface, response, callbacks)
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 559, in process_response
    if error is None and result > 0:
TypeError: unorderable types: NoneType() > int()
 
Additional information
Electrum version: 3.1.3
Operating system: Linux-4.19.0-1-amd64-x86_64-with-debian-9.7
Wallet type: standard
Locale: en_US

The wallet simply will not synch or won’t connect at all.

Issue Analytics

State:
Created 5 years ago
Comments:12 (4 by maintainers)

Top GitHub Comments

2reactions

NiExTycommented, Mar 20, 2019

Can’t upgrade because latest Electrum requires newer python version. It is really unfortunate that old versions were intentionally disabled.

2reactions

SomberNightcommented, Jul 5, 2019

Clients older than 3.3 can no longer connect to the network. Users should go to electrum.org and download the latest version of Electrum.

We have found a DOS vulnerability in them where a server can send them certain invalid data that they cannot parse and this kills the client’s network thread (all networking functionality). Old clients are vulnerable to phishing messages from servers via which users kept getting tricked and losing money. To put an end to this, we’ve deliberately started exploiting the DOS vulnerability to make old clients unusable, hence force users to update.

It is unfortunate that this also affects Tails users, where it’s not exactly easy to update. Sorry about this.

I suggest that you download the AppImage and run that. This can also be done on Tails, and is easy.

For Linux in general, see FAQ

Top Results From Across the Web

Electrum wallet - store - snapcraft.io

Clients older than 3.3.0 can no longer connect /synchronize. Users must upgrade. ... using version 3.1.3 in TAILS ...upon opening the wallet it ......

Azure AD Connect: Upgrade from a previous version to the latest

If you only have one Azure AD Connect server, if you are upgrading from AD Sync, or upgrading from an old version, it...

Docker Desktop release notes

Release notes for Docker Desktop for Mac, Linux, Windows.

Avaya Aura® 10.1.x.x Release Notes

under warranty is available to Avaya customers and ... pricing of its licenses and can be, without limitation, an agent, port or user, ......

VMware Workspace ONE Access 22.09.1 - Carl Stalhood

Upgrade Appliance. Version 19.03 and newer no longer include the embedded Connector so you must deploy one or two Windows machines to run...