Teamspeak Server not reachable from outside after reboot of server
reddit / selfhosted

----------------------------------------------------------------------
aspirat2110 · 2023-10-30 20:03

Hello,

I rebooted my server a few hours ago, and now my teamspeak server is
not reachable from the outside anymore. The direct IP from inside the
network still works.

The last time I know it was working, was on the 28th October at around
1am, I haven't changed anything since then (except for the server
reboot) and the Teamspeak Server Version should be the same as back
then.

I have forwarded the following ports in my router: 9987 UDP, 30033
TCP, 10011 TCP and 41144 TCP.
The Firewall in Proxmox is disabled. If I enable it, add rules to
allow connections on the ports and enable logging, I can see that the
packets arrive at the Proxmox Firewall and get accepted.

The Teamspeak Server is running inside a docker container and I have
passed through the same ports I forwarded in the router.

I have already tried the following:
\- Restart Teamspeak Docker Container
\- Restart Docker Service
\- Restart VM in which Docker is running
\- Restart entire Server
\- Move Teamspeak Server to a different VM and change the port
forwards in the router


The basic setup is like this:
Router -> Proxmox Server -> VM -> Docker -> Teamspeak Server

I'm running the following versions:
Proxmox 8.0.4 on the host
Debian 12 (with all updates installed as of this post) on the VMs
Docker 24.0.7
Teamspeak 3.13.7


If anyone knows what else I can try I would appreciate it. I don't
know what else I can try.

----------------------------------------------------------------------
Whyd0Iboth3r · 2023-10-30 20:08

Make sure the OS firewall has the allowed ports/protocols allowed.

----------------------------------------------------------------------
aspirat2110 · 2023-10-30 20:12

Shouldn't the OS firewall also block requests from the local network
if the port is not allowed?

If I connect via the local IP, everything works as expected.

----------------------------------------------------------------------
taxigrandpa · 2023-10-30 21:14

your IP changed when you rebooted

----------------------------------------------------------------------
aspirat2110 · 2023-10-30 21:31

Sorry, I should have mentioned that the IPs are static

----------------------------------------------------------------------
RedditSlayer2020 · 2023-10-30 21:46

Did you try running kubernetes?

----------------------------------------------------------------------
aspirat2110 · 2023-10-30 22:21

I recreated the portforward in the router, and now it works. I have no
idea what broke there

----------------------------------------------------------------------
taxigrandpa · 2023-10-30 22:22

no worries.

You got a new external ip?   have you restarted the router?

----------------------------------------------------------------------
aspirat2110 · 2023-10-30 22:53

Yeah, I already solved it. Had to recreate the port forward in the
router, after that everything works as it should. Thank you

----------------------------------------------------------------------
thekrautboy · 2023-10-31 07:49

> EDIT2: the IP of the server is static, and I used the new external
IP after the router restart

Why bother with connecting through the IP at all? Do yourself a favor
and set up a simple free DDNS for your external IP. Most likely your
router can keep it automatically updated, if not plenty of small tools
exist for it such as `ddclient`.

And even better, if you also use SRV records for Teamspeak in your
DNS, then you dont even need to specify the port number anymore.

You can turn this `142.16.420.69:56610` into just
`myteamspeak.dedyn.io` and done. Much nicer and easier to tell people
to use when they want to join your server.

----------------------------------------------------------------------
aspirat2110 · 2023-10-31 10:34

Normally I have set up a domain of which the records get updated
through cloudflare from my router, however I wanted to exclude the
delay the router has before updating the domain and the caching of DNS
as potential sources for this issue :)

----------------------------------------------------------------------
Whyd0Iboth3r · 2023-10-31 15:58

Yeah, that is true... Hmm