CM2Walki / CSGO

Dockerfile for automated build of a CS:GO gameserver: https://hub.docker.com/r/cm2network/csgo/
https://CM2.Network
MIT License
249 stars 74 forks source link

Still getting `Failed to connect to game server. The game server restricts clients` on DigitalOcean #75

Closed wildneuro closed 1 year ago

wildneuro commented 2 years ago

image

image
wildneuro commented 2 years ago

Help guys :)

korotky commented 2 years ago

It looks like you need to create login token for game server on https://steamcommunity.com/dev/managegameservers and put it into sv_setsteamaccount in server.cfg https://www.youtube.com/watch?v=mcKKfuEBNw8

CM2Walki commented 2 years ago

You can also set it using SRCDS_TOKEN= in docker run

wildneuro commented 2 years ago

I did that guys before opening a ticket.

What else?

CM2Walki commented 2 years ago

Can you post your docker run command or docker-compose stack?

Why is the server.cfg empty? Did you empty it?

wildneuro commented 2 years ago

Can you post your docker run command or docker-compose stack?

docker run -it --net=host --env-file /root/csgo-data/csgo.env -v /root/csgo-data/:/home/steam/csgo-dedicated/ -v /root/csgo-data/server.cfg:/home/steam/csgo-dedicated/csgo/cfg/server.cfg cm2network/csgo /bin/bash

File: /root/csgo-data/csgo.env:

SRCDS_TOKEN="AB...2C"
SRCDS_RCONPW="xxxxxxx"
SRCDS_PW="xxxxxxx"
SRCDS_PORT=27015
SRCDS_TV_PORT=27020
SRCDS_NET_PUBLIC_ADDRESS="0"
SRCDS_IP="0"
SRCDS_LAN="1"
SRCDS_FPSMAX=300
SRCDS_TICKRATE=128
SRCDS_MAXPLAYERS=14
SRCDS_STARTMAP="de_dust2"
SRCDS_REGION=3
SRCDS_MAPGROUP="mg_active"
SRCDS_GAMETYPE=0
SRCDS_GAMEMODE=1
SRCDS_HOSTNAME="CSGO Server"
SRCDS_WORKSHOP_START_MAP=0
SRCDS_HOST_WORKSHOP_COLLECTION=0
SRCDS_WORKSHOP_AUTHKEY="AB15C5.......8E"
ADDITIONAL_ARGS=""

Why is the server.cfg empty? Did you empty it?

I started from scratch, so it's empty. And per entry.sh script if it's missing it will download a new one. Could be a problem here, as file is empty but exists.

CM2Walki commented 2 years ago

SRCDS_LAN=1 try putting that to 0 ;)

vbrunko-voc commented 2 years ago

I did. No results man.

dallemugzz commented 2 years ago

I did. No results man.

i had the same issue and was about to give up. but i found out that the token needs to be made for 730 and NOT 740 even though that is the token that you would go with intuitively. so create a new token for appID 730 and i'm sure it will solve your problem.

CM2Walki commented 2 years ago

I just noticed it also says 730 during the token generation: image

wildneuro commented 2 years ago

image image Nope, still the same:

image

wildneuro commented 2 years ago

All firewalls are open in/out TCP/UDP, tried on 3 different clouds: AWS/Azure/DO