Dedicated Server connection issues
I am running a dedicated server on a windows 2016 server. I have set the server config to use the default port(27016), the server is an actual hosted server on my own hardware/rackspace, has a fixed IP address, all local firewalls disabled, and the hardware firewall I run has port 27016 opened both ways for both TCP/UDP(Just in case). The server shows on the steam server list, but when I try to connect it times out. I can connect to other dedicated servers. I've had friends try to connect to my server and they all get the same issue.
The logs in the dedicated server management shows:
2025-01-23 12:11:14.296: Peer2Peer_SessionRequest [007...802]
2025-01-23 12:11:29.319: Peer2Peer_ConnectionFailed [007...802], Timeout
2025-01-23 12:11:29.328: User left [007...802]
Config file is attached(I masked out the password)
I have the same bug
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards
Keen Software House
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards
Keen Software House
Small update - I removed all the firewall restrictions on that server to test, and the connection works. I've confirmed a dozen times that my config is correct, but I can see the dedicated server trying to open other ports?
52294
56644
49875
These aren't listed anywhere I can find - Are they also needed?
Small update - I removed all the firewall restrictions on that server to test, and the connection works. I've confirmed a dozen times that my config is correct, but I can see the dedicated server trying to open other ports?
52294
56644
49875
These aren't listed anywhere I can find - Are they also needed?
Looks like although the main port is the one used to form the initial connection, the server then attempts to open other ports to service the client. My firewall is set to not allow all outbound connections because it's in a secure hosting environment. How do I go about fixing this?
Looks like although the main port is the one used to form the initial connection, the server then attempts to open other ports to service the client. My firewall is set to not allow all outbound connections because it's in a secure hosting environment. How do I go about fixing this?
Hello Tony,
Thank you for reaching out to us on the forum. We’re sorry to hear about the issue you’re experiencing.
Based on the behavior you’ve described, it seems your Windows Server 2016 environment is blocking the ephemeral ports dynamically assigned by the operating system for client-server communication.
To resolve this issue, please ensure the ephemeral port range is allowed for both inbound and outbound traffic in your firewall. On Windows Server 2016, the default ephemeral port range is 49152–65535, which is critical for gameplay connections after the initial handshake.
Recommended Actions:
Firewall Configuration:
Update your firewall rules to allow TCP/UDP traffic on ports 49152–65535, specifically for the Space Engineers server executable.
Optional: Custom Port Range:
If you’d like to limit the range of ports used:
a. Open Command Prompt as Administrator.
b. Run the following command to set a smaller range (e.g., 52200–52499):
netsh int ipv4 set dynamicport tcp start=52200 num=300
c. Restart the server to apply the changes.
Update the firewall rules to allow traffic on the specified range.
If the issue persists after making these changes, please provide the latest server log files for further investigation. On Microsoft Windows Server, logs can typically be found in, C:\ProgramData\SpaceEngineersDedicated\Instance\Logs\ folder.
Kind Regards,
Keen Software House: QA Department
Hello Tony,
Thank you for reaching out to us on the forum. We’re sorry to hear about the issue you’re experiencing.
Based on the behavior you’ve described, it seems your Windows Server 2016 environment is blocking the ephemeral ports dynamically assigned by the operating system for client-server communication.
To resolve this issue, please ensure the ephemeral port range is allowed for both inbound and outbound traffic in your firewall. On Windows Server 2016, the default ephemeral port range is 49152–65535, which is critical for gameplay connections after the initial handshake.
Recommended Actions:
Firewall Configuration:
Update your firewall rules to allow TCP/UDP traffic on ports 49152–65535, specifically for the Space Engineers server executable.
Optional: Custom Port Range:
If you’d like to limit the range of ports used:
a. Open Command Prompt as Administrator.
b. Run the following command to set a smaller range (e.g., 52200–52499):
netsh int ipv4 set dynamicport tcp start=52200 num=300
c. Restart the server to apply the changes.
Update the firewall rules to allow traffic on the specified range.
If the issue persists after making these changes, please provide the latest server log files for further investigation. On Microsoft Windows Server, logs can typically be found in, C:\ProgramData\SpaceEngineersDedicated\Instance\Logs\ folder.
Kind Regards,
Keen Software House: QA Department
Thank you for the update. I was hoping that was not the case as I can't allow outbound traffic like that. I'll move it to another less secure environment. I'll close the case.
Thank you for the update. I was hoping that was not the case as I can't allow outbound traffic like that. I'll move it to another less secure environment. I'll close the case.
Hello,
thank you for your reply.
Since there is no more assistance needed from our side, I will close this thread now.
Thank you for your understanding.
Kind Regards
Keen Software House
Hello,
thank you for your reply.
Since there is no more assistance needed from our side, I will close this thread now.
Thank you for your understanding.
Kind Regards
Keen Software House
Replies have been locked on this page!