I have been running both Bitcoin Core and Bitcoin Cash. Currently, I am only troubleshooting the Bitcoin Cash server. I am reindexing the Core server. ElextrumX reports,

Code:

changing task concurrency from 10 to 1
disconnected whilst throttled

I would just Google that ad infinitum, but I can connect with the Electron Cash desktop app version 4.9 and 4.10. This seems like a less Googleable problem. Once Bitcoin Core is done reindexing I will compare the behavior between the two servers. My public IP address is 199.59.105.235:50001 if anyone wants to try to reproduce the behavior. I recall connecting to my server with my phone when I first set up both servers, but it has been a few months and I could be misremembering. I am using the non-standard port of 50001 with SSL. Thanks for reading.

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.

I have run an ElextrumX server in the past. I stopped running the server around the beginning of the new year. I started attempting to run one shortly after v 0.18 Bitcoin Core released. I synced both bitcoin's and electrum's database fresh. Initially I ran into a couple issues where the configs had changed for bitcoin/electrum and my old config files were causing problem. After updating my bitcoin config to reflect the new RPC syntax, and updating my electrum config for the new Services syntax, I run into a problem which includes throttling:

INFO:ElectrumX:[81392] disconnected whilst throttled.

Nmap shows port 50001 as open. However, I cannot find my server's IP or hostname in the list of servers and when I connect to the server manually I instantly see the above message when I tail -f the server log. When I close the Electrum wallet the above message stops recurring.

I accidentally sent some BTC to a BCH address. It is an insignificant amount, but it made me realize that Electrum (legacy) wallets do not generate addresses in the same order as Electron or perhaps they use a different depths. If I recall correctly there are a few numbers which can be changed when generating a wallet 'x/y/z' where x is the BIP implementation and z is the depth.  Presumably, I should be able to see the BTC in Electrum if the client searches the blockchain for transactions.

Electrum: 3.3.6
Electron:   3.3.1
Operating System: Linux

I didn't provide the other specs, because I am more interested in understanding the problem than recovering an insignificant amount of BTC. In Electrum I loaded the transaction from the blockchain via Tools -> Load transaction which did not prompt Electrum to search if it could generate the address which received UTXO in that transaction.

I also require that this implementation can communicate with ElectrumX.  I tried Parity, so that I could run bitcoin and bitcoin cash while only having to upgrade one codebase.  However, ElectrumX will not speak to Parity. As I understand it, Parity and bitcoin core use a different database formats.  Hence why ElectrumX rejects Parity's RPC responses with:

Code:

 
Jan 30 05:55:12  electrumx_server[4937]: ERROR:root:task crashed: <Task finished coro=<Controller.serve() done, defined at /usr/local/lib/python3.7/dist-packages/electrumX-1.8.12-py3.7.egg/electrumx
Jan 30 05:55:12  electrumx_server[4937]: Traceback (most recent call last):
Jan 30 05:55:12  electrumx_server[4937]:   File "/home/electrum/.local/lib/python3.7/site-packages/aiorpcx/util.py", line 118, in
.
.

Jan 30 05:55:12  electrumx_server[4937]: ERROR:Daemon:Supplied content type is not allowed. Content-Type: application/json is required

*I use lower case to denote that I am referring to the bitcoin/bitcoin cash networks and not the units of account.