-
-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teamspeak 3 monitor command failed to query Server with IPv4 and IPv6 #2658
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
You would be the first person I have come across to have configured your server in such a way. Is there a specific reason why you have configured the server to have two IP addresses? LinuxGSM relys on having a single IP address configured to make it easy to manage various things. Having mulitple IP addresses can currently become problematic and more complicated |
I'm not quite sure anymore, my server has been configured this way for quite a while and hasn't caused any problems so far. As far as I remember I registered a server nickname for my Teamspeak server. There was the possibility to specify both IPv4 and IPv6, which I did. I had to realize that my server was not reachable with the IPv6 address and some of my friends could not connect to the server with the nickname. So I looked for this possibility to specify both IP addresses. From my point of view it would be enough if LGSM would take the first address. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Greetings,
My Teamspeak3 server is constantly restarted by the monitor command.
I am using Ubuntu 18.04.3 with LinuxGSM 19.12.5
It seems that the monitor command has a problem with the fact that my Teamspeak 3 server is configured for IPv4 and IPv6.
My ts3server.ini looks something like this:
voice_ip=34.100.42.88,2001:3f3:828:742e::2
When I execute the Monitor command it looks like this:
Monitor ts3server: Querying port: tcp: 34.100.42.8820013f3828742e2:10011
The text was updated successfully, but these errors were encountered: