What is this :s protocol? Strange, my man page for elecctrum says there are only :t and :h options.
The online docs tell about more; a server can announce even a non-standard tcp port easily.
supported protocols (“t” = tcp@50001, “h” = http@8081, “s” = tcp/tls@50002, “g” = https@8082; non-standard port would be announced this way: “t3300” for tcp on port 3300)
I didn't need to know all those details, but it's all in server.peers.subscribe docu; it may worth a read.
How bizarre, having two dfiferent protocol flags for ports 50001 and 50002.
Thanks for sharing, I'll give those docs a look.
@helloelec can you also try to post the Electrum log? and what version does your Electrs running?
Code:
./electrum -v -1 --oneserver --server electrs_server_ip:50002:s
This command works! What is this :s protocol? Strange, my man page for elecctrum says there are only :t and :h options.

I think I have read it somewhere. The :t suffix should tell the client not to use SSL, and just connect plainly over TCP. While the :s suffix would make the client connext over SSL over TCP which make the command you are using now is working. This also the reason in your previous try whereas you are connecting to the server in an unencrypted manner.
Well I'm a bit confused. According to the post above the :t flag is just for tls over 50001, and my electrs server listens on 50001 but is not (to my knowledge) tls. I'll have to do some digging. Anyway thanks a bunch, what a relief to have this finally working!