[GH-ISSUE #2133] Monitoring function not work correctly with NAT #1642

New issue

Closed

opened 2026-02-27 02:58:17 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:58:17 +03:00

Owner

Originally created by @fearrr on GitHub (Dec 20, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2133

Server is behind NAT, there is an internal and external IP address. If specify 0.0.0.0 IP in the LGSM config file, server normally starts and players connect without problems, but the monitoring function checks the availability by the internal IP address (192.168...) and the LGSM is always rebooting normally running server
(P.S. If you specify an external IP address, the server does not start correctly)

dt command conclusion
https://gist.github.com/fearrr/42d6bcef5bbf82558e72802987e2ddcf

Originally created by @fearrr on GitHub (Dec 20, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2133 Server is behind NAT, there is an internal and external IP address. If specify 0.0.0.0 IP in the LGSM config file, server normally starts and players connect without problems, but the monitoring function checks the availability by the internal IP address (192.168...) and the LGSM is always rebooting normally running server (P.S. If you specify an external IP address, the server does not start correctly) dt command conclusion `https://gist.github.com/fearrr/42d6bcef5bbf82558e72802987e2ddcf`

kerem closed this issue

2026-02-27 02:58:17 +03:00

kerem commented

2026-02-27 02:58:17 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 20, 2018):

How odd, not an obvious issue. Can you provide the output of:

./rustserver monitor

also ./rustserver query-raw

query-raw is accessed by enabling ./rustserver dev

Thanks

@dgibbs64 commented on GitHub (Dec 20, 2018): How odd, not an obvious issue. Can you provide the output of: `./rustserver monitor ` also `./rustserver query-raw` query-raw is accessed by enabling `./rustserver dev` Thanks

kerem commented

2026-02-27 02:58:17 +03:00

Author

Owner

@fearrr commented on GitHub (Dec 22, 2018):

Thank you for your answer,
but now the behavior has changed,
the command is ok, I did not do anything to solve.
Maybe I was mistaken or not tested somewhere.

Just in case my outputs:
Output 'monitor' command:

[ INFO ] Monitor rustserver: Check IP: 192.168.1.10
[  OK  ] Monitor rustserver: Checking session: OK
[  OK  ] Monitor rustserver: Querying port: gsquery: 192.168.1.10:28015 : 0/1: OK

Output 'qr' command :
https://gist.github.com/fearrr/2f43babc86c723ca15057104f9406185

I'll open this issue again if the problem repeat.

@fearrr commented on GitHub (Dec 22, 2018): Thank you for your answer, but now the behavior has changed, the command is ok, I did not do anything to solve. Maybe I was mistaken or not tested somewhere. _Just in case my outputs:_ Output 'monitor' command: ``` [ INFO ] Monitor rustserver: Check IP: 192.168.1.10 [ OK ] Monitor rustserver: Checking session: OK [ OK ] Monitor rustserver: Querying port: gsquery: 192.168.1.10:28015 : 0/1: OK ``` Output 'qr' command : `https://gist.github.com/fearrr/2f43babc86c723ca15057104f9406185` I'll open this issue again if the problem repeat.

kerem commented

2026-02-27 02:58:17 +03:00

Author

Owner

@lock[bot] commented on GitHub (Dec 22, 2019):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Dec 22, 2019): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.