Closed xt9 closed 1 year ago
If you can access the container internally but not externally that you have a router/firewall configuration problem, not a problem with the container.
Your external port check looks like a TCP check, but the CS2 game protocol runs over UDP.
I recommend you double check your Router/Firewall configuration to ensure that you are forwarding UDP traffic to your container.
Some devices will let you create a single tcp_udp rule, others will require two separate rules.
I think the port forward is set up correctly but my guess is that it's wsl2 network shenanigans making it so the traffic is not ending up in the right place. Stumbled into this gigantic wsl thread https://github.com/microsoft/WSL/issues/4150 which seems to explain why connecting locally works, but external traffic not being router correctly.
Got it working on ubuntu, but my method from the start was connecting to the external ip for my network from a client running cs2 on the same network, and that for some reason does not work. But when I asked a friend to connect to my external ip it worked.
I've set up the server with docker compose, and can access it locally.
Some sanity checks I've done:
Relevant log excerpt
In the CS2 client I get the following with connecting with
connect 81.234.152.164:27015; password xxxxxx;
I've tried googling the UDP invalid error but not found much. Right now I left
- CS2_IP=
empty in docker-compose because I seemingly get other errors when i set it to 0.0.0.0Advice would be much appreciated