Open JustinBenedick opened 2 years ago
Ran a quick test by extracting the entire contents of the tf2-freeplay container/image and running it on bare metal. Item server was working had full customization. I am thinking running the docker image on a different system would help narrow things down. I am starting to think some port or some networking issue is happening within docker.
@JustinBenedick - the docker container gets the same network settings as the host. You only need to "open" or "map" ports that need incoming traffic.
Does Valve's item servers need a connection back to the TF2 server other than 27015?
Also, it could just be a fluke. Maybe their item servers were just having issues last night. Did you try it in Docker again?
Now it gets weirder. Within docker, if its run like a local lan game. item server works fine.
docker run -d --name TF2Freeplay_Sa16h25m58s -p=27015:27015/tcp -p=27020:27020/tcp -p=27015:27015/udp -p=27020:27020/udp lacledeslan/gamesvr-tf2-freeplay ./srcds_run -game tf -port 27015 +sv_pure 0 +maxplayers 24 -console -usercon -replay +mapcyclefile mapcycle_quickplay_payload.txt +randommap +hostname "Laclede's_LAN_TF2_Freeplay" +rcon_password ""
If I add in the stuff for online play, the item server is disconnected docker run -d -p=27015:27015/tcp -p=27020:27020/tcp -p=27015:27015/udp -p=27020:27020/udp lacledeslan/gamesvr-tf2-freeplay ./srcds_run -game tf -port 27015 +sv_pure 0 +maxplayers 24 -console -usercon -replay +mapcyclefile mapcycle_quickplay_koth.txt +randommap +sv_setsteamaccount [REDACTED] +tf_server_identity_account_id [REDACTED] +tf_server_identity_token "[REDACTED]" +hostname "Laclede's_LAN_TF2_Freeplay" +rcon_password ""
The docker port theory is out the window.
https://forums.alliedmods.net/showthread.php?p=2786543#post2786543 << calling in some help
8/12 the server could not get to the valve item server not sure if this was a network issue or image issue.
Ran on as a docker image on ll-harvey while using dmz on my home router