Closed thewilltavares closed 4 years ago
Hi @thewilltavares, with that output the server is working correctly. Have you tried connecting to the server while the container is in that state?
Thanks @fnicolini - I get the following error in the game console. 1 other user replicated the same issue trying to connect.
Attempt to send to not connected connection {1}
Failed to send internal buffer channel:6 bytesToSend:1096
Send Error: WrongConnection channel:6 bytesToSend:1096
ChannelBuffer SendBytes no space on unreliable channel 6
GameNetworkManager.desiredHost={ hostType=None }
ClientDisconnected due to error: Timeout
I have the server port open, and even tried DMZ'ing the container and was still unable to connect.
Did this errror occur after the server was running for quite a while? This is an issue with the server, it happens to us all the time when the server has been up for a while. The only workaround we found at the moment is restarting the container.
Hi @fnicolini - this is on a new docker container. I have been unable to connect at all.
1) Are you trying anything custom? E.g. changing port or setting a password? 2) Do you get different results stopping the container and restarting it (both on starting and connecting phases) ?
I can confirm that the initial screenshot is the normal and expected behaviour, so the server starts up correctly but cannot handle connections.
I actually test the docker images on a DigitalOcean droplet with Debian Buster and it definitely works there, the problem is (probably) somewhere else.
I'm getting the same error, here the full log :
Running on :
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
Any idea ?
1. Are you trying anything custom? E.g. changing port or setting a password? 2. Do you get different results stopping the container and restarting it (both on starting and connecting phases) ?
I can confirm that the initial screenshot is the normal and expected behaviour, so the server starts up correctly but cannot handle connections.
I actually test the docker images on a DigitalOcean droplet with Debian Buster and it definitely works there, the problem is (probably) somewhere else.
Hi @avivace I tried with and without custom settings, and stopping/starting and rebuilding a few times as well. If the log file is expected behavior, I must have something else (perhaps network related) to address.
Hi there, decided to chip in as I am experiencing the exact same issue. @thewilltavares , I'm using Ubuntu 16.0.4 so I am wondering if it has something to do with the operating system if Debian Buster works fine? I am currently getting an environment setup to confirm this, but that's the only thing I can think of that could be influencing this at present.
EDIT: I have attempted using this on a fresh installation of Debian buster, but the results seem to be exactly the same. Maybe there's a possibility of something extra being required, or a specific network configuration to allow connections to pass in a certain way? Firewalls don't seem to be causing any issues as I can't find any enabled, but I may be wrong.
Hi all, just chipping in myself too. Having the same issues. Although I have started off with the Steam dedicated server and have noticed the same issues on there... Maybe something caused by the source?
I have tested with the Windows install and (only) connecting to the server on localhost worked. Anything past that was not able to get to the port at all. Not even telnets on the Default port out of the same Network.
Thinking it might be some stupid Win Network or Firewall issue I have switched to my 18.04.4 Ubuntu LTS and tried the docker image on there. Cannot access the port again and there are other gameservers running just fine on there. Checked with https://www.portcheckers.com/ aswell and port is closed to them.
Hi @Leamnji , @Vaela-V , @thewilltavares Sorry for the late reply. Unfortunately, we are not able to consistently reproduce this issue. We test the docker image on blank droplets from DigitalOcean on Debian 10, without any prior configuration to the system. This is probably a network/nat related issue.
One thing you can try is to open the query port too (so 27015 and 27016 needs to be allowed), and append 27016:27016/udp
on the docker command.
On the other hand, it makes little sense to troubleshoot to hell this now, since a the 1.0 release is expected to come in August and they might bring some improvements and fixes (server browser??) to the server, too.
Getting the same thing here on an arch desktop. It runs to the same point as the dedicated server console directly off steam/proton (unloading x unused assets ...), but you can't type or interact with it. I can use the window launched through steam like a normal server console (although with tons of extra text and markdown gibberish) with commands like 'help', 'quit', etc, but the docker console is completely unresponsive, and the only way to stop it was to lookup the PID and kill -9 it, ctrl-c and even ctrl-z wouldn't work. Wasn't able to connect via localhost while it was running.
Getting the same issue here. One thing I noticed is that in the output log there are error messages like
Could not load config /Config/config.cfg: Could not find file "Z:\home\steam\ror2-dedicated\Risk of Rain 2_Data\Config\config.cfg"
Could not load config /Config/config.cfg: Could not find file "Z:\home\steam\ror2-dedicated\Risk of Rain 2_Data\Config\autoexec.cfg"
Could not load config /Config/config.cfg: Could not find file "Z:\home\steam\ror2-dedicated\Risk of Rain 2_Data\Config\server.cfg"
I don't know what the first 2 config files do, but the last one is required when you specify a password right? My command was docker run avivace/ror2server:0.1 -p 27015:27015 -p 27015:27015/udp -e R2_PSW='PASSWORD'
Did you guys retry with the 1.0 release? Any update?
Hello, with 1.0 I'm getting
Could not load config /Config/server_pregame.cfg: Could not find file "Z:\home\steam\ror2-dedicated\Risk of Rain 2_Data\Config\server_pregame.cfg"
on the server-side and
Attempt to send to not connected connection {1}
Failed to send internal buffer channel:6 bytesToSend:1096
Send Error: WrongConnection channel:6 bytesToSend:1096
ChannelBuffer SendBytes no space on unreliable channel 6
GameNetworkManager.desiredHost={ hostType=None }
ClientDisconnected due to error: Timeout
when trying to connect.
I can now confirm that after the 1.0 update and the new commits, everything works fine... Apart from the command input in console. That doesn't really bother me though, as there are mods such as R2DSE that gets past this issue. Thanks a bunch, it works just as normal!
Hello, with 1.0 I'm getting
Could not load config /Config/server_pregame.cfg: Could not find file "Z:\home\steam\ror2-dedicated\Risk of Rain 2_Data\Config\server_pregame.cfg"
on the server-side
That isnt anything to worry about. They added a new config in the 1.0 update,
Servers can now define behavior to run upon entering character select by supplying a "server_pregame.cfg" config file
I can confirm the server is running correctly. As mentioned by @Vam-Jam that file is not strictly required and the error is non-blocking
@DerYeger see #5 and #6
@DerYeger see #5 and #6
This worked for me. Thank you!
@DerYeger see #5 and #6
This worked for me. Thank you!
Great!
@vyrus714 @Leamnji @thewilltavares @qcoumes Can you try refollowing the README now? We pushed some updates and hopefully we fixed the network connection issues.
Everything is working on my side, good job !
Works fine now! I think my previous problems with stopping it were just not being familiar with docker as well - it stopped fine with docker stop.
I am unable to get past this point in running the container. Is there a known workaround to this issue?
OS: Docker running on DigitalOcean droplet.