vinanrra / Docker-7DaysToDie

7 days to die server using LinuxGSM in Docker with backups, monitor, auto-installable mods and more
GNU General Public License v3.0
209 stars 42 forks source link

External IP changed after a power outage. Have restarted the server and restarted the container, but can't be seen on Steam. Internally everything is the same. #217

Closed tagelthebagel closed 7 months ago

tagelthebagel commented 7 months ago

Describe the bug My router restarted and I gained a new external IP.

To Reproduce Steps to reproduce the behavior: I have restarted my server my friends can connect directly to my IP. We all can still connect but Publicly it is not showing on the 7DaysToDie server list. Not even in my local list.

Expected behavior Expect to see my server upon a server restart. Even if my IP changes? Maybe though.

Versions: Docker Engine 24.0.7 Client Docker Engine Server: 24.0.7

Docker/Docker-compose version: '2' services: 7dtdserver: image: vinanrra/7dtd-server container_name: 7dtdserver environment:

JonnySiHI commented 7 months ago

Check port forwarding on your router , and see if your server internal IP (192.x.x.x) is there with ports 26900, 26901 and 26902 being forwarded

tagelthebagel commented 7 months ago

Check port forwarding on your router , and see if your server internal IP (192.x.x.x) is there with ports 26900, 26901 and 26902 being forwarded

Yeah my Server PC's IP has not changed and my router has forwarded 26900-26903 my other instances of services Jellyfin and Plex have forwarded okay with no problems.

tagelthebagel commented 7 months ago

I did not mean to close. And

tagelthebagel commented 7 months ago

And the thing is my internal IP has not changed. But my external has. We can connect via Internal IP so my Port is still forwarded.

tagelthebagel commented 7 months ago

Whats weird is the game can still be connected to just fine and everything still works, nothing was lost. Just my External IP changing. The port forwarding is clearly working if me and my friends can connect on that port. I have attempted to restart router and restart the docker container but to no avail. I do not think the external IP would matter but I feel like Steam or the server hosting list is just bugged somehow.

vinanrra commented 7 months ago

I'm going to transfer this issue to conversation, because it isn't an issue with the container but can help other users.