Dedicated Server Ports not working

[Sn!ck[CH]]

I have the problem that my dedicated server will not use the ports I specify on the startup.

When I run ./InsurgencyServer-Linux-Shipping -password=1234 the server starts and "works" when I let every Port (TCP/UDP all) open.

When I run ./InsurgencyServer-Linux-Shipping -Port=27102 -QueryPort=27131 -password=1234
and specify the Ports 27102 27131 (and to be sure 27015) for TCP/UDP I can't connect.
And then I try it will all ports open again: doesn't work. I checked the open ports on my server where the application is listening. No, this ports are not on the list.

I don't know what the standard Ports are nor what the problem is

1) is there a Standard Port the server will run when no Port is provided?
2) Does anybody know why the heck the server will not start on the port 27102 if the parameter -Port=27102 is set?


EDIT
The server is running on the port, but on the connection I have to specify the port (IP:PORT). But then the server doesn't start with my game config. No idea have to check it tomorrow
- in case a dev read this post. I have never see such a bad documentation with so many problems and bugs as here.

What is still open: Which Port does the Game chose if no port is specified?

[Compad]

Look at this side => https://portforward.com/insurgency-sandstorm/
you can read this:
Insurgency: Sandstorm - Playstation 4
TCP: 1935,3478-3480
UDP: 3074,3478-3479
Insurgency: Sandstorm - Steam
TCP: 27015-27030,27036-27037
UDP: 4380,27000-27031,27036
Insurgency: Sandstorm - Xbox One
TCP: 3074
UDP: 88,500,3074,3544,4500

open your server firewall also!

[Sn!ck[CH]]

Thank you very much. Now I now which ports are used. It is a shame, that the community has a better documentation then NWI

What is still open: Which is the Standard Port the Game uses, if no Port is specified?

My Problem: When I specify 27015, the Game doesn't allow the connection.
- For troubleshooting I opened on the firewall all ports for my IP (TCP and UDP).

When I specify no Port on startup I can connect (because all Ports are open). This can't really be the solution.

In the documentation the show as an example: -Port=27102
- This is not on the List you provided

So the devs did really a bad job about the documentation.....

[=BB= Pudfark]

"So the devs did really a bad job about the documentation....."

Yes, they shy away from the real modding community.

[Leaper]

27015 is the standard port.

Quick question though, when you connect do you type the port also? On my server even if i set it to 27015 and don't type the port it wont connect.
You have to type in the connect box: ip:port
eg: 192.168.0.123:27015

Also you mention you turn off your firewall, that part is confusing and no one on the internet seems to have a clue how firewalls work..
Are you hosting on your own computer or another computer on your network or a paid host on the internet?
Firewalls only block incoming connections to your computer and applications. If you connect to a service/game(aka outgoing) your firewall gives zero F****'s about that connection.
The only place you need to take care of the firewall to allow connections is on the computer where the server is running.

[=TAC= Stuermer]

Doesn't count which port you're using as long as it isn't a standard-port like 80 etc.
Usually you have to port-forward those ports you're using for all protocols (TCP with checks for packetloss and UDP for fast connections without check for packetloss). That's it. No matter what portnumber you use, but the "official" range is 27000-27999.

The first port is the game-port, where your player connect to, the second one the query-port for the browser-list ingame (or within Steam). So you only need the first one, you should be able to connect to it manually. As mentioned above you need the full line with port, not just the IP.

So for example you need to put in "233.155.93.54:27015" into the directconnect field. If you forwarded the port 27015 for TCP and UDP on your server, it should work.

What I'm not really sure about is the travelcommand thing within the documentation, because I still use travel commands, not commandline parameters for the ports. So my startfile still looks like this:

InsurgencyServer.exe Powerplant?Scenario=Scenario_Powerplant_Checkpoint_Security?Game=CheckpointHardcore?maxPlayers=4?port=27015?queryport=27016?password= -log -hostname="=[TAC]= SweatySWAT 3 | Ammo+ | NoZones | SecCPHC |" -MapCycle=MapCycle  -AdminList=Admins -Rcon -RconPassword=rconpass -RconListenPort=27017 -GSLTToken=62GOO36004DFC9CC2026788690D31DE3 -GameStats -Mods -ModList=Mods -mutators=MoreAmmo,NoRestrictedArea -ModDownloadTravelTo=Powerplant?Scenario=Scenario_Powerplant_Checkpoint_Security?Game=CheckpointHardcore

You can try with it, just change the servername and the token.

[Sn!ck[CH]]

Hi guys. Thank you for your help. It's very appreciated.

@Lipe123: 192.168.0.123:27015 ->yes I used this to connect.

@Stuermer: Thank you very much! I personally would delete the GLS token out of your command you've posted. Just to be sure, nobody can use it.


I should maybe specify some things that makes it easier for you to help me: I have the background knowhow about port forwarding etc., I work in IT :) So Im 99.99% sure that it is not a firewall problem. But I have never hosted any dedicated steam server with steamcmd. And that the devs do not document anything and all guides in the internet have different infors makes it not eaiser...

I'm doing an automated container image for docker, so everybody can run a dedicated server in this community in less then 2min just with one command (startup the container, path to the config etc.). I saw that there are so many ways to run the servers, updates that breaks things etc. so I thought this would maybe help the community. I was asked by a friend if I could do this, so challenge accepted.

Before I started this, I just setup everything on a VM to test it. There it works in generally . But there it is easy: I just created a firewall rule (on the VM) that allows all incomming UDP and TCP traffic from my gamePC to the VM. There it works. So that's why I guessed that it must use more then just 2 ports (Port=x and QueryPort=y). But Maybe I'm wrong. The Problem is, that the devs officially do not really document it...

On a container it is a bit more tricky because you have to speficy the exact port and protocol that is allowed into the container. And there are much more dependencies during the creating on the container. This is just my problem to create the container image till it works. As soon as I have figured out the problem and fix it, it will just work out of the box for everybody that would use the container.

The last days I did all the automation scripts from scratch to get all potential bugs out of it. And there I found some points that may lead to this. I have now to test if it works now with the ports I specify on the server startup. Now I have to run some tests. I'll keep you posted.

Thank you all for your help and patience. And sorry, that I did not specify the situation clear enough what I'm doing behind the scene :)

[Sn!ck[CH]]

Ok guys I found the problem. It was docker related. For some reason inside the container it forwarded from outside the wrong port (example: 5000) to the Port 27015 etc.

Oh dear... It was just one line of code missing a ":" (double point) in my script.

Now I have a fully automated container image on docker for insurgency sandstorm. Vanilla server that can be fully customizable. I'll write now in the next 1-2 weeks a documentation for it and then publish it here on steam as a Guide for all that like to have such thing

Thanks again for all your patience and your inputs.

[=BB= Pudfark]

Hopefully, you are on to something good. Thank You ^^^^^^^^^^^^^^^^^^^^

[=TAC= Stuermer]

Glad it's working ... often it's the damn small things haunting users in config files ;) I usually forget to include "scenario=" into the startbatch or have a fubar in essential names ;) Makes me very nervous, when things work from the start ;D

[Sn!ck[CH]]

Stuermer: Yes, it would be somehow suspicious if it works from the beginning xD

[=TAC= Stuermer]

;)

[Sn!ck[CH]]

Stuermer and Pudfark: the first part of the project is released on GitHub. The Guide on Steam is in work

https://github.com/SnickCH/InsurgencySandstormDedicatedServer

If you like, you can check it. If you already have container knowhow you can start using it.

The "Howto Guide" (how to get started with a container for a dedicated insurgency sandstorm server) is in work and needs some other days. So if you are not familiar with container but are interested, maybe add me on the friend list and I can show you the first part of the guide. The more feedback I get from admins, the better the guide will help the community:)

[=TAC= Stuermer]

Our linux servers are managed by another member, I'm only on windows, so probably not much of help here. But I'm interested nonetheless, maybe I'm starting another linux-server at the weekend and try a docker installation. Never did this before, so might be I need some help. I can play the total noob part quite well ;)

[Sn!ck[CH]]

FYI: the container works on linux and should also work on windows. There I don't know the exact parameters.

The cool thing about containers: OS independent :) The only difference is how to run the container (Commands, path slach vs. backslash and such small details)

[=TAC= Stuermer]

Ok, then I will be your windows-noob ;)