SteamAuth Fail Message

[Ronyel]

This morning, trying to log into official server, and I keep getting a SteamAuth Failed message. I've verified game files. Any other thoughts? Anyone else get this?

[Ronyel]

anyone?

[Armadaan]

yes me to

[Serious]

Me too after Update

[Willi]

Im hosting my own server on a Linux machine. Running the server manually, it works just fine, no issues at all. But If I run the server as a Linux Service, I get the "SteamAuth Fail" message whenever I try to connect. Exact same config.. bit strange...

[Kaervan]

Originally posted by Willi:

Im hosting my own server on a Linux machine. Running the server manually, it works just fine, no issues at all. But If I run the server as a Linux Service, I get the "SteamAuth Fail" message whenever I try to connect. Exact same config.. bit strange...

You're saying you don't get the message if you just launch the service as a user in the foreground with tmux or screen or whatever instead of a systemd service, authentication works fine? Gonna try it out.

[Kaervan]

That was it. I had thrown all the startup commands into a systemd unit file, and would just keep getting the errors. I wonder if the operating env was dropping some configuration that was needed for steam auth to work, though /proc/pid/environ showed the path to steam client library was present.

Anyway, this makes sense because hosting services like g-portal containerize their servers, and the entrypoint is the server process, which makes it a foreground process. I'd buy you a beer if I could. Thanks for posting!

For anyone who doesn't understand what this means, You need to take you the ExecStart line from the systemd file that you may have got from PiMyLife's guide, and put it in a script on disk, then run that script in tmux or screen so you can close the session.

put this in a file like server.sh

#!/bin/bash

/home/steam/servers/soulmask/StartServer.sh -SteamServerName='' -MaxPlayers=20 -PSW='' -adminpsw='' -pve -Port=8777 -QueryPort=27015 -EchoPort=18888

You can use screen for easy attach/detach

$ screen -S soulmask
$ bash server.sh

to send it to the background, hold control and press A then D. then you can log out of your session. To re-attach, connect to the server with the same user and use screen -x soulmask to attach to the process window. Many people like tmux because it's more robust, but I'm old and screen has never failed me :)

[PapaBearDoes]

Originally posted by Kaervan:

That was it. I had thrown all the startup commands into a systemd unit file, and would just keep getting the errors. I wonder if the operating env was dropping some configuration that was needed for steam auth to work, though /proc/pid/environ showed the path to steam client library was present.

Anyway, this makes sense because hosting services like g-portal containerize their servers, and the entrypoint is the server process, which makes it a foreground process. I'd buy you a beer if I could. Thanks for posting!

For anyone who doesn't understand what this means, You need to take you the ExecStart line from the systemd file that you may have got from PiMyLife's guide, and put it in a script on disk, then run that script in tmux or screen so you can close the session.

put this in a file like server.sh

#!/bin/bash

/home/steam/servers/soulmask/StartServer.sh -SteamServerName='' -MaxPlayers=20 -PSW='' -adminpsw='' -pve -Port=8777 -QueryPort=27015 -EchoPort=18888

You can use screen for easy attach/detach

$ screen -S soulmask
$ bash server.sh

to send it to the background, hold control and press A then D. then you can log out of your session. To re-attach, connect to the server with the same user and use screen -x soulmask to attach to the process window. Many people like tmux because it's more robust, but I'm old and screen has never failed me :)

Confirming this works on bare metal Debian 12.

I am still confused as to why running the same command / setup as user via systemd causes issues though ...

[pppppp]

I just restart my server and it fixed , buying dedicated server from claw.cloud