Jump to content

EOS issues running a shiny new dedicated server


risingfish

Recommended Posts

I haven't run a server since A19 and a friend and I are going to start playing again. I've been trying to setup a new dedicated server, but I can't connect to it, and it's throwing a bunch of EOS errors at startup. Even using the local I.P. I can't connect. I've made sure to add folder exceptions to Windows defender so that isn't in the mix.

Anyone know what these are, and if they would stop me from being able to connect? Well, looks like I can't attack photos so here's some of the log lines:

 

2023-10-04T15:46:17 15.800 WRN [EOS] [LogHttp - Warning] Retry 2 on https://api.epicgames.dev/sdk/v1/default?platformId=WIN
2023-10-04T15:46:17 16.094 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: invalid HTTP response code received. URL: https://api.epicgames.dev/sdk/v1/default?platformId=WIN, HTTP code: 0, content length: 0, actual payload size: 0
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: request failed, libcurl error: 60 (Peer certificate cannot be authenticated with given CA certificates)
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 23 (Hostname api.epicgames.dev was found in DNS cache)
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 24 (  Trying 18.214.72.93...)
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 25 (TCP_NODELAY set)
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 26 (Connected to api.epicgames.dev (18.214.72.93) port 443 (#2))
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 27 (ALPN, offering http/1.1)
2023-10-04T15:46:17 16.095 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 28 (Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 29 (TLSv1.3 (OUT), TLS handshake, Client hello (1):)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 30 (TLSv1.3 (IN), TLS handshake, Server hello (2):)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 31 (TLSv1.2 (IN), TLS handshake, Certificate (11):)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 32 (TLSv1.2 (OUT), TLS alert, Server hello (2):)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 33 (SSL certificate problem: unable to get local issuer certificate)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] 000001FE7BFEDB90: libcurl info message cache 34 (Closing connection 2)
2023-10-04T15:46:17 16.096 WRN [EOS] [LogHttp - Warning] Lockout of 15.823481s on https://api.epicgames.dev/sdk/v1/default?platformId=WIN
2023-10-04T15:46:33 31.962 WRN [EOS] [LogHttp - Warning] Retry 3 on https://api.epicgames.dev/sdk/v1/default?platformId=WIN

 

Here's more log lines:
 

2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: invalid HTTP response code received. URL: https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7B9FE55EE0-429F-6C6E-7329-5F98C1F39BCC%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.16.0-23677751%20-%20%2B%2BEOSSDK%2BRelease-1.16-CL-23677751&UserID=&AppEnvironment=Production&UploadType=sdkevents, HTTP code: 0, content length: 0, actual payload size: 0
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: request failed, libcurl error: 60 (Peer certificate cannot be authenticated with given CA certificates)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 0 (Hostname in DNS cache was stale, zapped)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 1 (  Trying 35.173.33.138...)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 2 (TCP_NODELAY set)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 3 (Connected to api.epicgames.dev (35.173.33.138) port 443 (#45))
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 4 (ALPN, offering http/1.1)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 5 (Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 6 (TLSv1.3 (OUT), TLS handshake, Client hello (1):)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 7 (TLSv1.3 (IN), TLS handshake, Server hello (2):)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 8 (TLSv1.2 (IN), TLS handshake, Certificate (11):)
2023-10-04T15:57:03 661.368 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 9 (TLSv1.2 (OUT), TLS alert, Server hello (2):)
2023-10-04T15:57:03 661.369 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 10 (SSL certificate problem: unable to get local issuer certificate)
2023-10-04T15:57:03 661.369 WRN [EOS] [LogHttp - Warning] 000001FED331CAE0: libcurl info message cache 11 (Closing connection 45)
2023-10-04T15:57:03 661.517 WRN [EOS] [LogHttp - Warning] Retry exhausted on https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7B9FE55EE0-429F-6C6E-7329-5F98C1F39BCC%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.16.0-23677751%20-%20%2B%2BEOSSDK%2BRelease-1.16-CL-23677751&UserID=&AppEnvironment=Production&UploadType=sdkevents

 

Link to comment
Share on other sites

Thanks for the response, I just verified it was current but repaired any way. Still no dice. It looks like there is something wrong with an SSL cert in there. Anyone know if there's a way to turn off support for Epic so it just doesn't run that code?

Link to comment
Share on other sites

Yeah, could be. I didn't know Amazon was CA now, and that must be a new development, so I could see only Windows 11 having it by default. I bought a little HP EliteDesk G2 that I use for windows game servers, but it doesn't have TPM 2.0 so can't be upgraded to Win 11. Might good to put the fix in a KB article somewhere for folks using old computers for servers.

Link to comment
Share on other sites

Ah yeah that makes sense. Indeed, they became a CA I think 2 or 3 years ago, some dynamic intermediate certificate deal they have going on, honestly cert-tech isn't something I have really been keeping an eye on. I'll add that to the common solutions; it certainly should be somewhere in a KB article. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...