dedicated Server: WRN [EOS] - NoConnection and server is still initializing [Solved]

[Neflitix]

Hey folks

I had some problems until I got my self-hosted dedicated server running on a Windows Server 2022 VM.

I would like to share my findings with you here.


On the terminal window for log output on my server, I had various warnings regarding the Epic Online Services (EOS). A connection with the game to the ded. server could not be established, in the game I got the message: "Server is still initializing please try again in a minute"

And this for hours...


I had the following entries in the log (and terminal windows of course) of the dedicated server like:

WRN [EOS] [LogHttp - Warning] 0000022A90DA6030: libcurl info message cache 8 (SSL certificate problem: unable to get local issuer certificate)
WRN [EOS] [LogHttp - Warning] 0000022A90DA6030: libcurl info message cache 9 (Closing connection)

WRN [EOS] [LogEOS - Warning] Failed to connect to the backend. ServiceName=[SDKConfig], OperationName=[GetPlatformConfigRoute], Url=[<Redacted>]
WRN [EOS] [LogEOS - Warning] SDK Config Platform Update Request Failed, Result Code: EOS_NoConnection, Retrying after 3.230567 seconds
ERR [EOS] Failed registering session on backend: NoConnection

After I was disconnected from the game (you remember, "Server is still initializing please try again in a minute") I had the following messages in the server log:
(xxxxxx is for the corresponding IDs)

INF [Auth] PlayerName authorization successful: EntityID=-1, PltfmId='Steam_xxxxxx', CrossId='EOS_xxxxxx', OwnerID='<unknown/none>', PlayerName='xxxxxx', ClientNumber='1'
INF [Auth] ServerState authorization failed: EntityID=-1, PltfmId='Steam_xxxxxx', CrossId='EOS_xxxxxx', OwnerID='<unknown/none>', PlayerName='xxxxxx', ClientNumber='1'
INF Kicking player (Server is still initializing): EntityID=-1, PltfmId='Steam_xxxxxx', CrossId='EOS_xxxxxx', OwnerID='<unknown/none>', PlayerName='xxxxxx', ClientNumber='1'

ERR [EOS] [LogEOSAntiCheat - Error] [AntiCheatServer] [UnregisterClient-001] ClientHandle 0000000000000001 not found.
ERR [EOS-ACS] Failed unregistering user: InvalidParameters
ERR [EOS] Failed unregistering player in session: NotFound
WRN DisconnectClient: Player EOS_xxxxxx not found

The relevant message is this one, which gave me the right thought:

(SSL certificate problem: Local issuer certificate cannot be retrieved)

Solution:
(I use firefox and therefore, I describe the procedure with Firefox.
However, the procedure is similar in other browsers.)

1. Go to the website (on your gaming-rig or the server machine)
   https://api.epicgames.dev/sdk/v1/default?platformId=WIN
   
2. Left-click on the padlock to the left of the address bar
   
3. Left-click on connection is secure
   
4. Left-click on more information
   
5. In the window that opens, left-click on the padlock-icon at the top and then on Show certificate
   
6. Three certificates are displayed in the following window.
   Click on the one at the top right (in my case "Amazon Root CA")
   
7. Scroll down to Misc and save the two certificates.
   PEM (certificate) and PEM (certificate chain)
   
8. Rename the two downloaded files from *.pem to *.crt
   
   From here, the steps must be executed on the server machine:
   
   
9. Stop the dedicated server app if still running
   
10. Double-click the *.crt-files and click on "Install certificate" in the following window
    
11. Import the two certificates into the "local computer" certificate store
    
12. repeat the process and import into the "current user" certificate store

Start the 7dtd dedicated server and the EOS error messages should have disappeared. Playing on the server also worked for me afterwards.

Hope it helps - feedback welcome.


Drop some beers - cheers!

[Elprez]

How in the world did you figure that out? I ran into the same errors. I am glad I found your post. Hats off to you!

[Neflitix]

Hi Elprez

Thanks for your feedback.
As already described above, the issue with the certificate error has given me the right idea.

"Why can't the 7 day server communicate with the EOS service if the browser can do so without an error?"

Based on my experience (I have been working in IT for more than 20 years), it had to be an error in the certificate chain and it is usually a lack of trust.

So the certificate für "Amazon Root Certificate Authority" was made known to the computer and thus to all applications by importing it and the connection was trustworthy (it was before but this was not recognized) and the connection works.

[GeneralG]

Neflitix,

You absolute f-ing giga chad. Your post here is a god send. I have a very similar setup (Hyper-V with Server 2022 as a VM) and was able to get a search result when looking earlier today. I spent so long trying to figure out why I couldn't get it working and never thought of it being a cert issue, and had not delved into the logs that deeply yet to see the cert failures.

Most games we play have never required a cert and if anything need whitelisting in windows firewall for the exe that's running the application (and of course port forwards in the firewall).

Now I can go back to closing all of the opened ports I made while troubleshooting so it's back to being more secure of a server again. You're a legend.

[Solofoid]

Originally posted by GeneralG:

Neflitix,

You absolute f-ing giga chad. Your post here is a god send. I have a very similar setup (Hyper-V with Server 2022 as a VM) and was able to get a search result when looking earlier today. I spent so long trying to figure out why I couldn't get it working and never thought of it being a cert issue, and had not delved into the logs that deeply yet to see the cert failures.

Most games we play have never required a cert and if anything need whitelisting in windows firewall for the exe that's running the application (and of course port forwards in the firewall).

Now I can go back to closing all of the opened ports I made while troubleshooting so it's back to being more secure of a server again. You're a legend.

I'm using a HyperV VM as well, but this certificate installation did not help me at all.

I believe my issue might be with my ports. I've opened 26900-26905 on the router's firewall, I've port forwarded them to my VM, I created exceptions on the HOST Windows Firewall AND the VM's.

But still I cant get to join the dedicated server. EOS keeps failing to register session on backend saying there's no connection.

[JP]

Thank you for this, saved me some precious time on weekend!

[Neflitix]

Originally posted by Fazoelly:

I'm using a HyperV VM as well, but this certificate installation did not help me at all.

I believe my issue might be with my ports. I've opened 26900-26905 on the router's firewall, I've port forwarded them to my VM, I created exceptions on the HOST Windows Firewall AND the VM's.

But still I cant get to join the dedicated server. EOS keeps failing to register session on backend saying there's no connection.

Hi Fazoelly,

please make sure that your 7dtd VM has its own, static IP address and does not share it with the host machine.
(VMware offers this possibility, unfortunately I don't know HyperV very well).
If the VM has its own IP address, you do not need to open any ports on the host machine. For test purposes, you can also TEMPORARILY deactivate the firewall on the VM.

Assuming that the parameters in serverconfig.xml have not been changed

<property name="ServerPort" value="26900"/>

the ports you need to permit (incoming) are:

Router + virtual machine:
TCP/UDP: 26900
UDP: 26901-26903

virtual machine:
(if you want to use the web panel of the dedicated server)
TCP: 8080-8082

I assume that everything outgoing is unrestricted.
Otherwise you would have to open TCP 80 and 443 to the direction of Epic Online Services.
Unfortunately, I can't give you any IP addresses for this.

Maybe GeneralG can post his port configuration here.

Hope it helps.

[Devestater]

Neflitix,

I f-ing love you!

The cert thing was just the fix i needed to get my dedicated server going.

Just to share my specs in case anyone else is having the same issue: I'm running TrueNAS Scale v24.04.02, with a Win10Pro VM.

I was hoping to get the 7DTD server going on a Debian 12 or Ubuntu 24 VM, but i'm just happy I can play with some friends.

Not all heroes wear capes.

[Gregeri]

Спасибо за помощь! Столкнулся с такой проблемой, когда устанавливал сервер на виртуальную машину. Удалил виртуальную машину и решил просто запустить сервер на пк, но и там появилась такая же проблема)))) Сейчас все работает!

[Mr.G]

dude thank you very much for this article. U R savior

[Azrael316]

♥♥♥♥♥♥♥♥♥! How do I send actual beer?? Saved me what remains of my hair... :) Thanks dude.

[Phoenix.GT]

Thanks, man. They should make EOS ♥♥♥♥ be optional in config. Screw Epic, hail Steam!

[cyBerShy[RUS]]

If someone has an old version of the server OS, like me (WinServer 2012, for example), and manipulations with the certificate do not help, then what helped me was adding the site
"https://api.epicgames.dev"
to the trusted sites in the IE settings. After that, the 7D2D server was able to connect to EOS and stopped kicking everyone as unrecognized players!

[DeadlyToast]

Originally posted by Neflitix:

Hey folks

I had some problems until I got my self-hosted dedicated server running on a Windows Server 2022 VM.

I would like to share my findings with you here.


On the terminal window for log output on my server, I had various warnings regarding the Epic Online Services (EOS). A connection with the game to the ded. server could not be established, in the game I got the message: "Server is still initializing please try again in a minute"

And this for hours...


I had the following entries in the log (and terminal windows of course) of the dedicated server like:

WRN [EOS] [LogHttp - Warning] 0000022A90DA6030: libcurl info message cache 8 (SSL certificate problem: unable to get local issuer certificate)
WRN [EOS] [LogHttp - Warning] 0000022A90DA6030: libcurl info message cache 9 (Closing connection)

WRN [EOS] [LogEOS - Warning] Failed to connect to the backend. ServiceName=[SDKConfig], OperationName=[GetPlatformConfigRoute], Url=[<Redacted>]
WRN [EOS] [LogEOS - Warning] SDK Config Platform Update Request Failed, Result Code: EOS_NoConnection, Retrying after 3.230567 seconds
ERR [EOS] Failed registering session on backend: NoConnection

After I was disconnected from the game (you remember, "Server is still initializing please try again in a minute") I had the following messages in the server log:
(xxxxxx is for the corresponding IDs)

INF [Auth] PlayerName authorization successful: EntityID=-1, PltfmId='Steam_xxxxxx', CrossId='EOS_xxxxxx', OwnerID='<unknown/none>', PlayerName='xxxxxx', ClientNumber='1'
INF [Auth] ServerState authorization failed: EntityID=-1, PltfmId='Steam_xxxxxx', CrossId='EOS_xxxxxx', OwnerID='<unknown/none>', PlayerName='xxxxxx', ClientNumber='1'
INF Kicking player (Server is still initializing): EntityID=-1, PltfmId='Steam_xxxxxx', CrossId='EOS_xxxxxx', OwnerID='<unknown/none>', PlayerName='xxxxxx', ClientNumber='1'

ERR [EOS] [LogEOSAntiCheat - Error] [AntiCheatServer] [UnregisterClient-001] ClientHandle 0000000000000001 not found.
ERR [EOS-ACS] Failed unregistering user: InvalidParameters
ERR [EOS] Failed unregistering player in session: NotFound
WRN DisconnectClient: Player EOS_xxxxxx not found

The relevant message is this one, which gave me the right thought:

(SSL certificate problem: Local issuer certificate cannot be retrieved)

Solution:
(I use firefox and therefore, I describe the procedure with Firefox.
However, the procedure is similar in other browsers.)

1. Go to the website (on your gaming-rig or the server machine)
   https://api.epicgames.dev/sdk/v1/default?platformId=WIN
   
2. Left-click on the padlock to the left of the address bar
   
3. Left-click on connection is secure
   
4. Left-click on more information
   
5. In the window that opens, left-click on the padlock-icon at the top and then on Show certificate
   
6. Three certificates are displayed in the following window.
   Click on the one at the top right (in my case "Amazon Root CA")
   
7. Scroll down to Misc and save the two certificates.
   PEM (certificate) and PEM (certificate chain)
   
8. Rename the two downloaded files from *.pem to *.crt
   
   From here, the steps must be executed on the server machine:
   
   
9. Stop the dedicated server app if still running
   
10. Double-click the *.crt-files and click on "Install certificate" in the following window
    
11. Import the two certificates into the "local computer" certificate store
    
12. repeat the process and import into the "current user" certificate store

Start the 7dtd dedicated server and the EOS error messages should have disappeared. Playing on the server also worked for me afterwards.

Hope it helps - feedback welcome.


Drop some beers - cheers!

Nice

[Ruyoka]

You are gold man thanks!!!!

[smiley52601]

Good god man! You have no idea what this means to me! Thank you so much!