Open tehelsper opened 4 years ago
You could try to delete the certificate in your .electrum
folder: 20200825T165229.997467Z | WARNING | interface.[192.168.1.175:50002] | Cannot connect to main server due to SSL error (maybe cert changed compared to "/Users/xxx/.electrum/certs/192.168.1.175"). Exc: ConnectError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1076)'))
. It could be that via some process you have updated the ssl cert on your server.
Are all affected users on macOS?
Also, is the cert self-signed or CA-signed? I expect self-signed from the domain, but can you confirm? Is that the case for all affected users?
Could you get someone who can reproduce to share the contents of the cert file on disk?
So e.g. this file /Users/xxx/.electrum/certs/192.168.1.175
The cert is self-signed.
All users are not affected. It appears to be a small minority and may be related to the device being used to access the server. AFAIK, it may have only affected one user on MacOS, but they claimed they reset all certs on both ends and repeatedly ran into the same issue.
Having the same issue, latest version with deleted certs folder. No change.
20201114T225216.500548Z | INFO | interface.[electrumx.erbium.eu:50002] | connection established. version: ['ElectrumX 1.15.0', '1.4']
20201114T225216.560675Z | INFO | network | fee_histogram [[69, 100873], [38, 126078], [28, 106198], [20, 142205], [12, 149310], [9, 243471], [5, 209123], [4, 139971], [3, 989630], [2, 269088], [1, 529860]]
20201114T225216.561111Z | INFO | lnwatcher.WatchTower.[local_tower] | set_up_to_date: True
20201114T225216.561322Z | INFO | lnwatcher.LNWalletWatcher.[wallet_2-LNW] | set_up_to_date: True
20201114T225216.562882Z | INFO | interface.[xtrum.com:50002] | connection established. version: ['ElectrumX 1.15.0', '1.4']
20201114T225216.657310Z | WARNING | interface.[167.172.226.175:50002] | disconnecting due to RPCError(2, "daemon error: DaemonError({'code': -5, 'message': 'No such mempool or blockchain transaction. Use gettransaction for wallet transactions.'})")
20201114T225216.657598Z | DEBUG | interface.[167.172.226.175:50002] | (disconnect) trace for RPCError(2, "daemon error: DaemonError({'code': -5, 'message': 'No such mempool or blockchain transaction. Use gettransaction for wallet transactions.'})")
Traceback (most recent call last):
File "electrum/interface.py", line 474, in wrapper_func
File "electrum/interface.py", line 498, in run
File "electrum/interface.py", line 638, in open_session
File "aiorpcx/curio.py", line 242, in __aexit__
File "aiorpcx/curio.py", line 211, in join
File "electrum/synchronizer.py", line 82, in _start_tasks
File "aiorpcx/curio.py", line 242, in __aexit__
File "aiorpcx/curio.py", line 211, in join
File "electrum/synchronizer.py", line 241, in main
File "electrum/synchronizer.py", line 209, in _request_missing_txs
File "aiorpcx/curio.py", line 242, in __aexit__
File "aiorpcx/curio.py", line 211, in join
File "electrum/synchronizer.py", line 214, in _get_transaction
File "electrum/interface.py", line 906, in get_transaction
File "electrum/interface.py", line 166, in send_request
File "asyncio/tasks.py", line 414, in wait_for
File "aiorpcx/session.py", line 529, in send_request
File "aiorpcx/session.py", line 499, in _send_concurrent
aiorpcx.jsonrpc.RPCError: (2, "daemon error: DaemonError({'code': -5, 'message': 'No such mempool or blockchain transaction. Use gettransaction for wallet transactions.'})")
20201114T225216.669991Z | INFO | network | switching to blackie.c3-soft.com:57002:s
20201114T225216.689547Z | INFO | lnwatcher.WatchTower.[local_tower] | set_up_to_date: False
20201114T225216.690318Z | INFO | lnwatcher.LNWalletWatcher.[wallet_2-LNW] | set_up_to_date: False
20201114T225216.691647Z | INFO | interface.[endthefed.onthewifi.com:50002] | set blockchain with height 656952
20201114T225216.691934Z | INFO | interface.[endthefed.onthewifi.com:50002] | skipping header 656952
20201114T225216.692676Z | INFO | interface.[orannis.com:50002] | disconnecting due to: ErrorGettingSSLCertFromServer(ConnectError(ConnectionRefusedError(61, "Connect call failed ('50.35.73.78', 50002)")))
@scramblr that's unrelated. probably duplicate of https://github.com/spesmilo/electrum/issues/6686 see https://github.com/spesmilo/electrum/issues/6686#issuecomment-716548084 in particular
note: similar error message in https://github.com/spesmilo/electrum/commit/02a9ab80be819468352f773bd7120421868d38f0 (but related to CA-signed certs there)
Some myNode users are having an issue connecting to the electrs electrum server via nginx on myNode. It seems to work in the vast majority of cases, but some users do seem to have issues. Electrs does appear to be running properly and can be accessed via port 50001. The failure only occurs on port 50002.
Here is one of the logs:
More info is on the mynode issue tracking this. https://github.com/mynodebtc/mynode/issues/360
Any ideas?