finitio

Kill me ... freaking port 15636 just not listening - yeah. So try 15637 instead. Works - I hate my life. Had a problem with Password in the end. Fixed it with this. I hate unfinished software so much! I am trying to run the Enshrouded_Proton Container which starts up and the logs look clean. Though I can not connect to it - not even locally. It seems like the server is not listening on any port. If I try to ping the server - everything is good. I am 99.99% sure that this aint a network problem. Being on the server I can't even find the port being listened to: nc: connectx to Local-IP port 15636 (tcp) failed: Connection refused Being ON the server (in the container) I can not even successfully nc the 127.0.0.0 15636 ... Just aint working and I do NOT want to have this server on the public steam list but only locally available. Also ON the server (in the container): nmap -sT -p- 127.0.0.1 Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-18 10:23 PST Nmap scan report for localhost (127.0.0.1) Host is up (0.00019s latency). Not shown: 65534 closed tcp ports (conn-refused) PORT STATE SERVICE 36633/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 3.16 seconds Can somebody please try and help? The container is set up to use the local IP address and still, in the logs it shows my public IP. I did read that this might be normal "While debugging it actually turned out that the Enshrouded Server is always talking to the Steams STUN Servers." source --- After 5 very frustrating hours I am giving up on this project. I have no clue what might be causing my problem. I checked IP tables on unraid - all good it's simply that this damn container aint having it, not listening to the ports at all. What caught my eye was this on the server (in the container) netstat -tuln Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:41893 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:44124 0.0.0.0:* udp 0 0 0.0.0.0:15637 0.0.0.0:* seems like there is only one port listed and god knows why two other ports are listening. I recon this must be a problem on my end but I simply can not get my head around it - no way. Oh and if you think it must be my network - no. I get an nginx working and calling from 0.0.0.0 which runs on the same docker stack. So it must be something else but network! docker-server-logs.rtf