Submit Feedback

SE dedicated server fails to start server on EOS

Lowie Kestens shared this bug ago

Solved

Hi,

I am having an issue where a server is not able to start with the error "Server connect failure (User connect failed.)"

the server is set to EOS (because I want to play with some friends that are on console) and if I change nothing but set it to steam, the server starts up just fine. And if I try the same thing on my local pc it also works fine (even on EOS).

I will include a screenshot of the console.

My current setup:

ESXi running a windows server 2025 VM

the VM/server has internet access, UDP port of server is port forwarded and allowed through firewall

Nothing else is running on this machine

Files:

I have the same bug

Replies (2)

QA KeenSWH ●

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

Reply URL

Keen SWH QA Agent 1 ●

Hello,

Thank you for your detailed report and for sharing your setup information.

Please make sure your system has the latest Windows updates installed, as these updates include the root certificates required by Epic Online Services. Missing certificates may cause errors such as "Server connect failure (User connect failed)."

If needed, you can also install the certificate manually:

Install the latest Windows Updates, which will add the necessary root certificate.
Or manually install the certificate via Windows by running this command in a terminal (Command Prompt or PowerShell):
```
curl https://account-public-service-prod03.ol.epicgames.com/account/
```

If the problem continues after checking these steps, please come back to us with details so we can assist further.

Kind Regards,

Ludmila Danilchenko

Head of Space Engineers QA Department

Reply URL

Lowie Kestens ●

Hi,

The certificate was not installed by windows update, so I tried the command and that did the trick.

I am now able to start the server via EOS and connect to it.

Thanks for the quick feedback.

URL

Ondrej Borz ●

Hello Lowie,

thank you for your reply.

Happy to hear that you are no longer experiencing this problem after applying the steps from above.

Since there is no more assistance needed from our side, I will close this thread now.

Happy Engineering!

Kind Regards

Keen Software House: QA Department

URL