Can connect to ElectrumX Server with desktop, but not phone

[hashslinger]

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.

[jackg]

Yeah I can't connect to it either. Have you tried the version on your phone without the one on your computer running? Maybe it's load issue.

[hashslinger]

Code:

changing task concurrency from 10 to 1
disconnected whilst throttled

Sounds like a bug injected when the devs updated ElectrumX to defend agains DDoS attacks, but the fact the my desktop client works makes me think there is something wrong with the Android version of Electron Cash.

[Pmalek]

I am not experienced with this type of troubleshooting but isn't the default ssl port 50002? Maybe try changing it.
There are some suggestions here, maybe they help: https://www.reddit.com/r/Electrum/comments/d8j09w/on_what_port_can_i_connect_to_my_electrumx/

[jackg]

It looks to be connecting though. 50002 is a personal port ssl is somewhere like 253 I think (probably for backwards compatibility with 8 bit systems).

[hashslinger]

The port choice explained*: In my previous post I went about figuring out how to run Bitcoin Core and Cash servers on the same box. My solution was to run one server with the default configs and for Bitcoin Core I added a second private IP address to my box. I tried using the default external ports, but I could only connect to one server at a time this way. Since it would cost money and other resources to get a second public IP address, it was much easier to use a non-standard port for one of the servers. If I were trying to run my servers for the public, it would warrant the cost of another IP address because most people are not going to try to connect to a server with a non-standard port. However, for the purpose of learning ops, it made much more sense to use a non-standard port. 
   *In short, it's possible to identify a service uniquely with a unique IP:PORT. I could add a second IP or port to run both Core and Cash servers; it's easier to add a port.

I had assumed the Electron Cash automatically updated through Google Play, but I had been running version 3 when 4 is available. It appears the default config for ElectrumX drops old clients which is reasonable. I switched Bitcoin Cash to the default port 50002 just in case the Electron Cash Android app is not smart enough to connect to a non-standard port. The app gives the option to pick any port, but it also gives the option to not select a server automatically which does not work. So the app obviously has bugs.

I will report how the Electrum Android app behaves in a day after my server has reindexed.

[jackg]

So it's electron cash with the issue? Don't report it to electrum, report it to electron cash.

Old clients are dropped by default after a vulnerability was discovered, I have auto update on my phone so didn't know it extended to android too so that's interesting.

If you're running Linux, try running

Code:

ss -tupan | grep 50002

if you want to check that port is just used once (so there aren't any conflicts - if it doesn't find anything your electrum server isn't running or it's on a different port.

[hashslinger]

At the time I initially posted, I didn't know if the problem was with the server or the client.