TuRz4m / Ark-docker

Docker for ARK: Survival Evolved
168 stars 184 forks source link

Server is not listening #48

Open problemss opened 4 years ago

problemss commented 4 years ago

My server appears to be starting correctly, but when I run status I receive the following message:

Running command 'status' for instance 'main'
 Server running:   Yes 
 Server listening:   No 
 Server version:   5349305 

Not sure where to check, I have the ports open on the docker call and on my router.

docker run -it -p 7778:7778 -p 7778:7778/udp -p 27015:27015 -p 27015:27015/udp -p 32330:32330 -e SESSIONNAME='####' -e ADMINPASSWORD='####' -e SERVERPASSWORD='####' -e AUTOUPDATE=120 -e AUTOBACKUP=60 -e WARNMINUTE=30 -e TZ='America/Los_Angeles' -v /opt/docker/ark:/ark --restart unless-stopped --name ark turzam/ark

Any help or direction will be much appreciated.

problemss commented 4 years ago

Here is my arkserver.log entry

16:25:14: start
16:25:14: Running /ark/server/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland\?MaxPlayers=70\?Port=7777\?QueryPort=27015\?RCONEnabled=True\?RCONPort=32330\?ServerAdminPassword=####\?ServerPassword=####\?SessionName=####\?listen -crossplay -log
16:25:14: Server PID: 646
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Setting breakpad minidump AppID = 346110
cutec-chris commented 4 years ago

I have exact the same issue, is there anyone who solved this ?

Y0ngg4n commented 3 years ago

Same issue here

CosmicHorrorDev commented 3 years ago

I know I'm a bit late to the party but,

I believe from my when I was searching around that this was just a bug in the program used to monitor the server status that's been fixed in later versions (that this container hasn't been updated for I guess).

If you're not able to connect to your server with a connection timeout then it's likely because port 7777 needs to be passed through as well. I only know because I was struggling to get things working for a large part of the day and was finally saved by finding this docker image that has it documented. The linked image also works fine with status:

Running command 'status' for instance 'main'
 Server running:   Yes
 Server PID:   128
 Server listening:   Yes
Server Name: [REDACTED] - (v320.18)
Steam Players: 0 / 70
Active Steam Players: 0
 Server online:   Yes
 ARKServers link:   http://arkservers.net/server/[REDACTED]
 Steam connect link:   steam://connect/[REDACTED]
 Server build ID:   5983737
 Server version:   320.18
Y0ngg4n commented 3 years ago

@LovecraftianHorror i am currently passing this port threw but the problem exists neverless