Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
And some more insights:
The public IP of the server is directly mapped to the nic.
IPv6 IS enabled.
My client is also running linux. There is no "third party software" installed which "optimizes" my network connection - and as stated: connecting to other servers is working.
Hit refresh and wait for it to show up with the right name and etc. As soon as it shows up try hitting stop refresh. Now try to connect.
Idk if it's the steam servers view having issues or the actual server having issues but that's the only way I could get my friends to connect to my server. Only way I can do it from outside my LAN too.
Thank you for taking the time to reply and try to help.
But it seems you haven't fully read my problem / initial post. I have the server listed in the "steam server view" and it is showing as online. I can click connect and it reaches the server (as seen in the log file pasted above). I just then get disconnected by the server and are unable to finish the connect.
Just as an addition: I need to put port 2457 in the "steam server view" as also mentioned in other troubleshooting posts.
On the client, the screen goes black, I hear waves sound, then after a short period the cursor icon shows and I am back to the selection screen with a disconnected notice. This is the same, using favourite servers to connect from steam, or in game with the join IP.
Sorry I can't offer any help OP, but thought at least me putting this may highlight a non-OS constrained view on things.
In the mean time I've tried to debug with unity parameters: setting "-logFile" and even "-stackTraceLogType" on command line. But that gives (at least me), not more insights. Googling for "Steamworks.P2PSessionConnectFail_t" did not really bring something up.
I also validated ulimit settings for the process (linux specific) - all looks good.
Just for completion, the log file running with "stackTraceLogType Full":
And again, opening these ports doesn't do anything
One question @Shroom: do you have IPv6 enabled on the windows machines primary network interface running the server? Kind of the only guess I currently have about this behaviour.
Disabling IPv6 and testing this is a bit hard for me.. as I said there are other services running on the server and I am actually using IPv6 for them.
My server provider (Hetzner) has a "stateless / static firewall" feature. This, however, does not allow communication flow. So it seems to cut off communication for that Steamworks p2p communication.
They describe it like this:
So I added / allowed outgoing UDP packages in the ephemeral port range ("32768-65535") for that feature. Maybe this helps anybody in the future.
Man you basically opened 50% of your UDP ports. I wouldn't recommend doing that.
You should only need to open 2456-2458 TCP&UDP.
Happening to me too, OVH Windows Server + ports 2456-2458 opened TCP/UDP
In my office I can connect to the server, but no one can from home, rare as ♥♥♥♥. Any clue?
Try creating firewall rules for the ports on the Windows Server.