starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-24 21:56:01 +03:00

[GH-ISSUE #1932] Linux GSM cant query port on Rust Server #1521

New issue

Closed

opened 2026-02-27 02:57:34 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 02:57:34 +03:00

Owner

Originally created by @Karrigallu on GitHub (Jul 6, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1932

I have the issue, that since yesterday, when i want to start my gameserver, the script works flawlessly, but i cant connect to my server. It worked before on the same settings. so i did ./gameserver monitor and found out that when the server is querying ports it fails.

[ FAIL ] Monitor rust-server: Querying port: gsquery: 62.75.163.10:28015 : 60/5: FAIL

so i went into root user, checked iptables and added some rules allowing port 28015 and 28016.
Still no success.
i then did ./gameserver query-raw and got errors aswell:

Failure! gamedig not installed Failure! jq not installed gamedig --type "" --host "0.0.0.0" --port "28015"|jq
/home/rustservermain/lgsm/functions/command_dev_query_raw.sh: line 30: jq: command not found
gsquery Raw Output
./query_gsquery.py -a "0.0.0.0" -p "28015" -e "unity3d"
ERROR: Unable to receive

I lready restarted my server, i also tried reinstalling rust server on a new user, same problem.
Please help me

Originally created by @Karrigallu on GitHub (Jul 6, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1932 I have the issue, that since yesterday, when i want to start my gameserver, the script works flawlessly, but i cant connect to my server. It worked before on the same settings. so i did ./gameserver monitor and found out that when the server is querying ports it fails. `[ FAIL ] Monitor rust-server: Querying port: gsquery: 62.75.163.10:28015 : 60/5: FAIL` so i went into root user, checked iptables and added some rules allowing port 28015 and 28016. Still no success. i then did ./gameserver query-raw and got errors aswell: `Failure! gamedig not installed Failure! jq not installed gamedig --type "" --host "0.0.0.0" --port "28015"|jq` `/home/rustservermain/lgsm/functions/command_dev_query_raw.sh: line 30: jq: command not found` `gsquery Raw Output` `./query_gsquery.py -a "0.0.0.0" -p "28015" -e "unity3d"` `ERROR: Unable to receive` I lready restarted my server, i also tried reinstalling rust server on a new user, same problem. Please help me

kerem

2026-02-27 02:57:34 +03:00

closed this issue
added the
outcome: wrong forum
label

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jul 6, 2018):

https://github.com/GameServerManagers/LinuxGSM/wiki/Support

GitHub
GameServerManagers/LinuxGSM
LinuxGSM - Linux Game Server Managers_

@UltimateByte commented on GitHub (Jul 6, 2018): https://github.com/GameServerManagers/LinuxGSM/wiki/Support <blockquote><img src="https://avatars2.githubusercontent.com/u/20358373?s=400&v=4" width="48" align="right"><div><img src="https://assets-cdn.github.com/favicon.ico" height="14"> GitHub</div><div><strong><a href="https://github.com/GameServerManagers/LinuxGSM">GameServerManagers/LinuxGSM</a></strong></div><div>LinuxGSM - Linux Game Server Managers_</div></blockquote>

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@Karrigallu commented on GitHub (Jul 6, 2018):

i dont understand why you closed this issue.
Im not sure if this issue is GSM related or not.
i take it as quite rude to just give me a wiki link, since i read it well enough.
I would much more appreceate you telling me, that it is as example not GSM related, instead
of just closing it. Thank you

@Karrigallu commented on GitHub (Jul 6, 2018): i dont understand why you closed this issue. Im not sure if this issue is GSM related or not. i take it as quite rude to just give me a wiki link, since i read it well enough. I would much more appreceate you telling me, that it is as example not GSM related, instead of just closing it. Thank you

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jul 6, 2018):

Three main reasons:

Didn't follow support guidelines regarding provided information
This isn't a LinuxGSM issue
You are not even reading the given output of your console which would allow you to most likely resolve at least half of the issue in 15 seconds, so why should anyone read your post?

Now please, be nice and read the provided link before commenting back on GitHub.

PS: I'm also more nice when the post starts with "hello" and ends with something like "thank you for your time and effort", thought it depends on mood at the moment... Dealing with unhelpful posts made at the wrong place takes effort.

@UltimateByte commented on GitHub (Jul 6, 2018): Three main reasons: 1) Didn't follow support guidelines regarding provided information 2) This isn't a LinuxGSM issue 3) You are not even reading the given output of your console which would allow you to most likely resolve at least half of the issue in 15 seconds, so why should anyone read your post? Now please, be nice and read the provided link before commenting back on GitHub. PS: I'm also more nice when the post starts with "hello" and ends with something like "thank you for your time and effort", thought it depends on mood at the moment... Dealing with unhelpful posts made at the wrong place takes effort.

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@Karrigallu commented on GitHub (Jul 6, 2018):

You are right, and i am sorry for taking your effort, but also thankful for giving it.
Even thought this isn't a GSM issue, and you said that i could most likley resolve 50% of it in 15 seconds, i cant fix it. But you seem like you can, and i would be really happy if you would help me.
Thanks again for your effort, and sorry for not being nice in my Issue at the first place...
Im working on this for 6 hours now and im really "depressed" in not fixing this damn issue

@Karrigallu commented on GitHub (Jul 6, 2018): You are right, and i am sorry for taking your effort, but also thankful for giving it. Even thought this isn't a GSM issue, and you said that i could most likley resolve 50% of it in 15 seconds, i cant fix it. But you seem like you can, and i would be really happy if you would help me. Thanks again for your effort, and sorry for not being nice in my Issue at the first place... Im working on this for 6 hours now and im really "depressed" in not fixing this damn issue

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@Karrigallu commented on GitHub (Jul 6, 2018):

please help me..

@Karrigallu commented on GitHub (Jul 6, 2018): please help me..

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jul 6, 2018):

Non development related issues have no place on github. Go on the Steam group or Discord and there will be people to help with this kind of issues.

@UltimateByte commented on GitHub (Jul 6, 2018): Non development related issues have no place on github. Go on the Steam group or Discord and there will be people to help with this kind of issues.

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@ghost commented on GitHub (Mar 13, 2019):

@Karrigallu Hey, did you resolve the issue? This is a mindblowing problem... I just can't wrap my head around. Especially with no SSH / coding experience really. There's nothing on the web about it and help is hard to find apparantly.
I've checked my logs. Made sure the ports were open and also done these: 1. systemctl disable firewalld
2. systemctl stop firewalld. I'm hosting at OVH and using CentOS7.

@ghost commented on GitHub (Mar 13, 2019): @Karrigallu Hey, did you resolve the issue? This is a mindblowing problem... I just can't wrap my head around. Especially with no SSH / coding experience really. There's nothing on the web about it and help is hard to find apparantly. I've checked my logs. Made sure the ports were open and also done these: 1. systemctl disable firewalld 2. systemctl stop firewalld. I'm hosting at OVH and using CentOS7.

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 24, 2020):

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.

@github-actions[bot] commented on GitHub (Dec 24, 2020): 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.