ssl ports randomly close about electrumx HOT 5 OPEN

ok so the ssl port was open on startup, and i saw the all seeing eye monitor connected to 50002 via netstat, but once the server went live, there were no more connections to the ssl port and it appears closed to the monitoring client again. im puzzled. electrumx is using >90% cpu most of the time as well.

from electrumx.

What version of python are you using? Maybe try updating it to a newer version, ideally 3.11+.
Also, if it is only the SSL ports you are having trouble with, try putting an nginx reverse-proxy in front of electrumx and let that terminate SSL. From experience, the SSL code in nginx seems to be much more robust than python's.

from electrumx.

@SomberNight python 3.8, ill update it.. yes only the ssl ports, they were working fine for the last 3 months and then suddenly both servers closed the ssl ports within a day of each other, but tcp and wss remain open. nmap also shows that ssl port is open on the machine, however electrumx is not responsive on it.

from electrumx.

updated to 3.12, seems to still have the issue.. after i start it up, i can see incoming connections on ssl port with netstat, but once the server goes live, they disappear. bizarre behavior. wss and tcp ports are open n have connections.

from electrumx.

update:
was watching the console for a bit, while the tcp and wss ports were open, but the ssl hadn't been.. and this came up after about an hour after the server went live:

INFO:ElectrumX:[14] SSL 68.183.133.141:41520, 1 total
INFO:PeerManager:[electrum-verge.cloud:50002 SSL] verified in 0.0s

that is the servers ip address., however the monitoring service is still showing the ssl port as closed.

from electrumx.