ElectrumX: running Bitcoin Core and BitcoinABC simultaneously

[hashslinger]

My goal is to run both the bitcoin and bitcoin cash ElectrumX servers. I have assumed that this would be easiest with the Bitcoin Core and BitcoinABC implementations. I do not know of a daemon which will run both networks simultaneously.

My attempted configuration follows. I configured BitcoinCash.conf with bind=192.168.1.2 and BitcoinCore.conf with bind=192.168.1.3.  Similarly, electrumcash.conf has SERVICES = ssl://192.168.1.2:50002 and electrumcore.conf SERVICES = ssl://192.168.1.3:50002.  With this config, I can connect to both ElectrumX servers with the Electrum and Electron Cash client but only for several minutes. Then the Bitcoin Core daemon gives the error, "socket recv error connect reset by peer (104) bitcoind", and crashes.

This may or may not be relevant. Before that Core's bitcoind gives the warning, "46 of  the last 100 blocks have unexpected version". When I configure BitcoinCore.conf without bind and electrumcore.conf with ssl://:50002,i.e. with both daemons binding to all available IP's, I still get this warning, but the Bitcoin Core daemon continues to run for hours.

For my router's firewall, I have configured two rules for each port. Port 8333, has a rule forwarding that port to 192.168.1.2 and 192.168.1.3, and the same applies to port 50002. I added the second IP address to my network interface with 'sudo ip address add 192.168.1.3/24 dev enp1s0'. I am running  Ubuntu 18 LTS.  I built Bitcoin Core v0.18.0 from source. Thanks for reading, and for your help.

[1715179552]

1715179552

[1715179552]

1715179552

[hashslinger]

Solved! On my last attempt, bitcoin cash was disconnecting instead of bitcoin. Also, the bitcoind daemon was stable, but the Electrum client connection kept dropping I reconsidered whether or not I could run both networks on port 50002. I created a rule to forward port 50002 to 50001 for bitcoin cash (I wasn't using 50001). I will try to document this. I've seen good docs for running an Electrum server, but not for running both networks simultaneously.