Hi everyone,
I was told to open a thread about this issue after speaking with support via tickets.
I am getting the following error after a server is launched:
"Could not establish connection to Steam servers."
Nobody can see the server listing due to this, or connect.
Server: Linux Debian VDS, 2x IP's.
1. Launching the server on IP ending .221, does not work (error above).
2. Launching the server on IP ending .221 on a different port, does not work (error above).
3. Launching the exact same server on IP ending .220, works (no error).
I have tried:
- 'rebooting' vds.
- made a ping to the ip ending .221 and .220 (both respond, no timeouts).
- checked IP is correct.
- flushed IP tables
- no firewall rules set via NFO control panel.
The IP ending .221 was DDoS'd last night (UDP flood).
Could not establish connection to Steam servers
- Abdul
- A semi-regular
- Posts: 28
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Thu Apr 04, 2013 3:11 am
- Location: United Kingdom
Re: Could not establish connection to Steam servers
Steam has a longstanding bug that causes it to not bind TCP connections to the correct IP address on the outbound. Try blocking all new TCP connections outbound to port 27017-27019:
iptables -A OUTPUT -p tcp --dport 27017:27019 --syn -j DROP
Doing this will force it to fall back to using UDP, which does work correctly.
This is one of those bugs that would be super-super-easy for Valve to fix, but for some reason they haven't fixed (I've told them many times).
iptables -A OUTPUT -p tcp --dport 27017:27019 --syn -j DROP
Doing this will force it to fall back to using UDP, which does work correctly.
This is one of those bugs that would be super-super-easy for Valve to fix, but for some reason they haven't fixed (I've told them many times).
Re: Could not establish connection to Steam servers
Thanks, that worked like a charm.