Port, +1 or not?

[kieron]

Hi there, I notice the instructions that says to add +1 to your port, to get what you should input to steam etc, but Im a bit stuck.

I am running 2 servers, this one,

ports:
      - 2459:2459/udp
      - 2460:2460/udp
      - 2461:2461/udp
    environment:
      - PORT=2459

and this one

ports:
      - 2456:2456/udp
      - 2457:2457/udp
      - 2458:2458/udp
    environment:
      - PORT=2456

Those ports are reflected in portainer too, so I'm sure its all mapped correctly- but what I'm finding is that take that top one, I have 2459 in the docker compose, so +1, I should be adding 2460 right? But if I click Find games in steam using ip:2460 it finds the server, correct name, then I click save this, and I view the server info, now it says ip:2459 so I'm not sure which I am supposed to tell people to use?

Also, are there any other issues with running 2 at once? Anything else I should change to avoid a crossover, except ports & directories obviously.

Thanks!

[mbround18]

if you are looking to access the server Via in game by clicking join by ip make sure to use the :2456 port. However, if you are using the favorites method you will have to use port :2457. (unless you changed the env var, then its what ever you put in the env var is the game connection port and the +1 port is the steam favorites port.)

The whole +1 schema is accurate, I run ~10-15 servers right now on my cluster with escalating port numbers. (ex 30010-30013, 30014-30016, etc) The steam connection port for steam related is based off the query port which is +1 of what you set in the env variable but the connection port for in game is the env variable port.

[CosmicHorrorDev]

I think one of their more recent updates did make it so that public actually had an effect. I'll have to test it out. So do you have it figured out now?

[slayer1551]

I’ve got it working on the other docker by lloeche but not this one yet

[CosmicHorrorDev]

Hmm, there really shouldn't be any major differences. If you're still willing to try troubleshooting, can you set PUBLIC=1 for a container using this image? And if that doesn't work also try removing the server install and let it redownload. From what I remember the public flag used to have seemingly no effect, but I think one of the recent updates talked about changing that behavior.

[deepusudhakar]

Hmm, there really shouldn't be any major differences. If you're still willing to try troubleshooting, can you set PUBLIC=1 for a container using this image? And if that doesn't work also try removing the server install and let it redownload. From what I remember the public flag used to have seemingly no effect, but I think one of the recent updates talked about changing that behavior.

Ran into the same problem on my end; server wouldn't show up in favourites unless the container had PUBLIC=1.

[slayer1551]

That did the job thank you! 😀