TS3 wont open open port 9987

Hello when i do netstat -tulpn | grep LISTEN

i get this output

tcp 0 0 0.0.0.0:10022 0.0.0.0:* LISTEN 4089/./ts3server
tcp 0 0 0.0.0.0:30033 0.0.0.0:* LISTEN 4089/./ts3server
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 27616/sshd
tcp 0 0 0.0.0.0:10011 0.0.0.0:* LISTEN 4089/./ts3server
tcp 0 0 0.0.0.0:10080 0.0.0.0:* LISTEN 4089/./ts3server
tcp6 0 0 :::10022 :::* LISTEN 4089/./ts3server
tcp6 0 0 :::30033 :::* LISTEN 4089/./ts3server
tcp6 0 0 :::22 :::* LISTEN 27616/sshd
tcp6 0 0 :::10011 :::* LISTEN 4089/./ts3server
tcp6 0 0 :::10080 :::* LISTEN 4089/./ts3server

havent changed anything were have 9987 gone?

i can connect with my lan ip 192.168.1.2 from within the network but not with external ip and port via my phone on cellular…

the log says

ts3server_2021-02-05__16_51_06.702076_0.log
2021-02-05 16:51:06.702162|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.13.3 (2020-12-16 14:17:05)
2021-02-05 16:51:06.702828|INFO |ServerLibPriv | |SystemInformation: Linux 3.10.0-957.12.1.el7.x86_64 #1 SMP Mon Apr 29 14:59:59 UTC 2019 x86_64 Binary: 64bit
2021-02-05 16:51:06.703680|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, ©TeamSpeak Systems GmbH
2021-02-05 16:51:06.703702|INFO |DatabaseQuery | |dbPlugin version: 3.11.1
2021-02-05 16:51:06.704725|INFO |DatabaseQuery | |checking database integrity (may take a while)
2021-02-05 16:51:06.764241|WARNING |Accounting | |Unable to open licensekey.dat, falling back to limited functionality
2021-02-05 16:51:06.764691|INFO |Accounting | |Licensing Information
2021-02-05 16:51:06.764710|INFO |Accounting | |licensed to : Anonymous
2021-02-05 16:51:06.764721|INFO |Accounting | |type : No License
2021-02-05 16:51:06.764741|INFO |Accounting | |starting date : Thu Oct 1 00:00:00 2020
2021-02-05 16:51:06.764753|INFO |Accounting | |ending date : Tue Nov 1 00:00:00 2022
2021-02-05 16:51:06.764763|INFO |Accounting | |max virtualservers: 1
2021-02-05 16:51:06.764772|INFO |Accounting | |max slots : 32
2021-02-05 16:51:07.436553|INFO | | |Puzzle precompute time: 636
2021-02-05 16:51:07.438468|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2021-02-05 16:51:07.454856|INFO |Query | |Using a query thread pool size of 2
2021-02-05 16:51:07.522463|INFO |Query | |listening for query on 0.0.0.0:10011, [::]:10011
2021-02-05 16:51:07.522732|INFO |Query | |listening for ssh query on 0.0.0.0:10022, [::]:10022
2021-02-05 16:51:07.522995|INFO |Query | |listening for http query on 0.0.0.0:10080, [::]:10080
2021-02-05 16:51:07.523109|INFO |CIDRManager | |updated query_ip_allowlist ips: 127.0.0.1/32,

ts3server_2021-02-05__16_51_06.702076_1.log
2021-02-05 16:51:07.522160|INFO |VirtualServerBase|1 |listening on 0.0.0.0:9987, [::]:9987
2021-02-05 16:51:08.050388|INFO |VirtualServerBase|1 |client connected ‘Tobias’(id:1515) using a myTeamSpeak ID from 192.168.1.10:51930
2021-02-05 16:51:11.779645|INFO |VirtualServerBase|1 |client connected ‘PartilleBoy!’(id:1658) from 192.168.1.7:38080

EDIT:

After a reboot of the teamspeak vm and updating of teamspeak all is well… Thank you all who reply’d and asked questions :smiley:

UDP listens do not show up with a LISTEN flag, so your grep won’t ever show them.
Besides, your grep is redundant, because the -l parameter already specifies to only show listening sockets.

its open in my firewall…

I got the same problem

Looks fine when the port is listed.

UDP will never appear as listening in that list. That’s intended.

Rest of the issue belongs to firewall and forwarding.

1 Like