Closed Fynf closed 4 years ago
I don't see a rejection message in the server logs, looks like the port might not be open. You need 27015 and 27016 open I believe.
See #6 and tell me if it works.
tl;dr use
sudo docker run -p 27015:27015/udp avivace/ror2server:0.1
👍 Can confirm that port parameter ordering made all the difference for me. I actually have some of the docker output from when the parameters were different. Running docker ps
can show if you're forwarding the ports correctly. The top one shows 27015/udp
while the bottom one (correct) shows 0.0.0.0:27015->27015/udp
This is an EC2 instance running on AWS.
ubuntu@ip-10-0-0-137:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
39513f92f76a avivace/ror2server:0.1 "/bin/sh -c ${STEAMA…" 8 minutes ago Up 7 minutes 27015/tcp, 27015/udp charming_ardinghelli
ubuntu@ip-10-0-0-137:~$ sudo docker kill 39513f92f76a
39513f92f76a
ubuntu@ip-10-0-0-137:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
08b1f7711309 avivace/ror2server:0.1 "/bin/sh -c ${STEAMA…" 2 minutes ago Up About a minute 27015/tcp, 0.0.0.0:27015->27015/udp crazy_ellis
ubuntu@ip-10-0-0-137:~$
I'm 100% sure that the old command in the README was working a couple of months ago. Something must have changed in the way docker is interpreting the syntax of docker run
. Anyway the solution proposed by @dubvulture has fixed the problem for me as well.
For reference: https://stackoverflow.com/a/60896628
On a DigitalOcean Droplet running with Debian 10 no connection can be established.
After installing Docker and running the command in the readME, the server seemingly starts, but a RoR2 client is unable to connect.
Server-Logs:
Client-Log: