TrueOsiris / docker-vrising

Container for V-Rising dedicated server
244 stars 63 forks source link

Can't see game in Server list on VRising #66

Closed pzohner closed 6 months ago

pzohner commented 6 months ago

image Does 'Failed to Initialize SteamNetworking' have anything to do with that?

I have opened up more ports as someone mentioned you need more ports opened in order for steam to see the game. heres my compose file: image

Am I missing anything else? All those ports are also forwarded on my router to my server.

Thanks so much for giving us a way to host V Rising on something other than windows :D

Killerherts commented 6 months ago

You only need to do

 27015:27015
 27016:27016

Also you can't bind multiple ports to the same one or multiple times. This is why I think your getting failure to initiate steam networking.

You need to add the queryport and gameport to your env section. Inorder to get the game to use the correct ports to appear on the server list.

environment:
  -GAMEPORT=27015
  -QUERYPORT=27016

This will update them in the host setting json file.

You can verify these are open by running netstat or running nmap on your public IP address to verify it's filtered and not closed

Make sure "ListOnSteam": true, and "ListOnEOS": true are set in the ServerHostSettings.json in \persistentdata, so the server is visible in the serverlist as well.

TrueOsiris commented 6 months ago

A normal docker installation shouldn't even be able to start your container with that config. if you change the ports to 27015, 27016, you should spin up the container, wait 10 minutes, and stop it. Then you can alter ServerHostSettings.json (in your /data folder on your host) and also change the ports there. And then start it. Then, on your firewall, you need to forward your incoming traffic on those ports to your dockerhost's internal ip (also on those ports)

The explanation is in the readme.md