Windows Dedicated Server not connecting to EOS

Khisanthax

Refugee
Hi Everyone,

So, I have the dedicated server newly installed on a windows 10 pro machine.  At first steamnetwork was listed not to  use that protocol but I removed that and it seemed to get better but still I couldn't connect to the server from a different PC.  Then I disabled anticheat since I had some warning but still can't connect to the dedicated server.

Here's the log:

https://pastebin.com/Bf9bpqYs

It seems it can't connect to the EOS or the backend or get auth somehow?  Any help would be appreciated.

 
You need to create an exclusion in your antivirus software for the game folder and saves folder. If you don’t have a third party antivirus then you have Windows Defender. Turning off the antivirus is not enough, you still need to create the exclusions. This is the most common cause of that error. If creating the exclusions doesn’t help, let us know and someone will help with other possibilities.

 
I have a version of win10 pro that doesn't have windows defender or firewall installed (tiny10) and I don't have an antivirus.  It would have to be something on the machine locally?

 
Last edited by a moderator:
I looked again at the error, a bit closer, and it might be a certificate issue. There was another thread where several people chimed in on getting good certificate but I don't remember the details. I'll try to find the post but in the meantime maybe someone else will chime in. Part of it was using a browser to try and connect to the website in the error message but let me see if I can find that post.

EDIT: Take a look  at this post and see if it helps.




 
Last edited by a moderator:
Thank you!  That link worked.  Apparently the version of windows that I had, (tiny10) does NOT have windows root CA installed.  Figuring out how to install the CA was beyond me, but one of the mods said that installing MS Edge probably installed the certs with it.  I installed Edge and it works.  I hate how bloated edge is ... but I'll figure that out later.  Thanks!

 
Ensuring the world is set correctly fixed my bogus cert issues!  The default world doesn't work for us but select 10k and it does, then just load whatever custom world up and thats fine also now.

 
Back
Top