Didstopia / rust-server

Provides a dedicated linux server for Rust (the game) running inside a Docker container.
MIT License
245 stars 106 forks source link

Login to steam failed #27

Closed Steven-Harris closed 6 years ago

Steven-Harris commented 6 years ago

I was trying to get my own server setup and had some issues. I can access Rcon and I was able to register my server with rust's list but I can't connect to it at all. I have port forward everything on my router and there is no other firewall in between.

I started digging in the log files and noticed this line... [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. I then exec'd into the container and tried logging in manually but nothing worked. For some reason `login anonymous prompted for a password and didn't work. I also tried a steam account that I normally use when steamcmd requires a steam account and it didn't work either.

Here is my docker-compose:

version: '3'
services:
   server:
      image: didstopia/rust-server
      ports:
       - "28015:28015"
       - "28015:28015/udp"
       - "28016:28016"
       - "8085:8080"
      volumes:
       - "./rust:/steamcmd/rust"
      environment:
       - RUST_SERVER_STARTUP_ARGUMENTS=-batchmode -load -logfile /dev/stdout +server.secure 1
       - RUST_SERVER_IDENTITY=RUST_BUCKET
       - RUST_SERVER_SEED=12345
       - RUST_SERVER_NAME=Rust Bucket
       - RUST_SERVER_DESCRIPTION=Rust Server on Tank
       - RUST_RCON_PASSWORD=${bucket_key}
       - RUST_OXIDE_ENABLED=1

Environment (OS/Distro, Docker version etc.)

Server Version: 17.09.1-ce

Dids commented 6 years ago

The SteamAPI lines are safe to ignore, and are happening for everyone using the linux build of the Rust server (as far as I know).

There's quite a few possibilities as to why it's not working, one or more firewall being the most common one, but since you said you've already check any firewalls, it's probably not that.

Do you see the server on something like Battlemetrics, and if so, could you provide a link, so I could check it out?

If it's visible there, have you tried connecting to it manually from the Rust client's console?

If all else fails, one other common issue occurs if your host machine (server) has multiple IP addresses, and you sometimes need to bind the Rust server to a specific IP address, otherwise it won't accept connections from different IP addresses.

Steven-Harris commented 6 years ago

Here is my battlemetrics https://www.battlemetrics.com/servers/rust/1936114

I don't have multiple IP's to the server so I don't know what else to try. I haven't used the rust cli so I will have to check that out

Steven-Harris commented 6 years ago

The console is saying 2018-02-03 05_44_18-clipboard

Steven-Harris commented 6 years ago

I have tried running with all the different branch types... NO BETA, release, and staging

Steven-Harris commented 6 years ago

I even manually set the rust branch on the server to be release and set the client to release so they would be the same.

Steven-Harris commented 6 years ago

Server logs show their protocol is 2052 not 2054

Steven-Harris commented 6 years ago

Tried turning off oxide

Steven-Harris commented 6 years ago

Finally got it, after forcing some updates and crossing some fingers