You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by SunnyMoo August 10, 2022
Hi,
I've got a problem with lgsm monitor: it tries to query my ts3 server on public IP but query is only allowed on private (vpn) IP and I don't want to let it opened on public IP.
How can I force lgsm monitor to use correct IP to check query ?
Thanks !
Addressed by #4975, merged and assigned to v26.3.0, now linked in Development.
LinuxGSM reads query_ip from ts3server.ini and includes the configured specific IPv4 address in the monitor's query targets. Set that value to the private/VPN address on which ServerQuery listens; the query interface does not need to be exposed publicly for local monitoring.
The PR validated address selection using configuration fixtures, including localhost bindings. It did not test a live TeamSpeak server, and IPv6-only query bindings remain outside its scope.
Closing as completed for the IPv4 query-binding issue. If this persists with a version containing #4975, please report the relevant binding configuration and monitor output.
Activity
dgibbs64 commentedon Oct 17, 2026
Addressed by #4975, merged and assigned to v26.3.0, now linked in Development.
LinuxGSM reads
query_ipfromts3server.iniand includes the configured specific IPv4 address in the monitor's query targets. Set that value to the private/VPN address on which ServerQuery listens; the query interface does not need to be exposed publicly for local monitoring.The PR validated address selection using configuration fixtures, including localhost bindings. It did not test a live TeamSpeak server, and IPv6-only query bindings remain outside its scope.
Closing as completed for the IPv4 query-binding issue. If this persists with a version containing #4975, please report the relevant binding configuration and monitor output.