Can't connect electrum to my own electrumx server

[jtkirk]

Hi,

I've been attempting for the better part of two weeks now to switch from Armory to Electrum as my main BTC client.

(I've been running my own bitcoind and lnd instances on my public linux server for over a year now - eventually I'd like to be able to use my own trusted server for BTC transactions even while on the road, without running a full node on my laptop).

I went through the process of building electrumx from source, getting it running, and then babysitting the 6+ day sync to my local blockchain instance. If it matters, the server is running Fedora Core 31.

Finally as of this morning, my server is up and running, and a TON of connections are being made via. SSL, according to the logs ('INFO:ElectrumX:[number] SSL: IP:PORT 50 total').

However, when I run the client from either my laptop, or even directly on the same server machine, and use my server hostname and port, it seems to just sit there with the red circle in the lower left. I'm able to connect to other servers no problem. But not mine.

Here's my (edited) electrumx.conf:

DAEMON_URL=http://[my_rpc_user]:[my_rpc_password]@127.0.0.1:8332/
DB_ENGINE=leveldb
USERNAME=bitcoin
ELECTRUMX=/usr/local/bin/electrumx_server
SSL_CERTFILE=[certs_folder]/caleb.vegas.crt
SSL_KEYFILE=[private_keys_folder]/caleb.vegas.key
SERVICES = ssl://:50002,rpc://
REPORT_SERVICES=ssl://caleb.vegas:50002
BANNER_FILE=/home/bitcoin/.electrumx/banner.txt
;SSL_PORT=50002
;TCP_PORT=50001
COIN=BitcoinSegwit
;NET=mainnet
MAX_SESSIONS_PER_IP=50

I opened up ports 50001 and 50002 on my firewall.

Any suggestions? Are there any simple tests I should try first with my server to verify it's actually working properly?

Thanks,
-Caleb

[1714187403]

1714187403

[1714187403]

1714187403

[1714187403]

1714187403

[jtkirk]

Ah, so I discovered the '-v' and '--oneserver' flags... Inspecting that output led me to realize the cause of the error: the electrum client wasn't verifying my server's SSL certificate (which is odd, because I was using a valid PositiveSSL certificate that I purchased from namecheap.com, which happens to be the same .crt and .key that my webserver uses, and clients like chrome and firefox accept that certificate). When I switched the electrumx server over to a simple self-signed cert instead of my fancy dancy cert, the client connected without a hitch.

Not a big deal, but it seems odd that I can only get self-signed server certs to validate from the client. Is this possibly a failure on the python side to discover the client system's trusted root certificate chains (the way SSL web browsers do)?

-Caleb

[HCP]

It seems that Electrum has some "cert caching" issues... judging by a number of closed issues on the ElectrumX GitHub Issues register

Try shutting down Electrum, then deleting the certs in the .electrum/certs directory and then restarting Electrum and see if it works with the "fancy dancy" cert loaded in ElectrumX

Failing that, try logging an issue on that ElectrumX github and see if the dev has any ideas.