Linux WRN [EOS] [LogHttp - Warning]

B

Big_Willy

Refugee
Periodically (sometimes several times a day) an error occurs immediately after the server restart (automatic restarts are configured through the hosting control panel), due to which players cannot log in to the server. In particular, they receive a message that the server is still rebooting. And this can continue until the next restart.

Error text:
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: HTTP request timed out after 30.00 seconds URL=https://api.epicgames.dev/matchmaking/v1/c9ccbd00333f4dd6995beb7c75000942/sessions
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: request failed, libcurl error: 0 (No error)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 0 (Found bundle for host: 0x7fa674012060 [serially])
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 1 (Hostname api.epicgames.dev was found in DNS cache)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 2 ( Trying 98.80.27.190:443...)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 3 (Connected to api.epicgames.dev (98.80.27.190) port 443)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 4 (ALPN: curl offers http/1.1)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 5 (SSL reusing session ID)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 6 (TLSv1.3 (OUT), TLS handshake, Client hello (1):)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] 0x5584a5d95cb0: libcurl info message cache 7 (Closing connection)
2025-07-17T05:01:11 61.706 WRN [EOS] [LogHttp - Warning] Retry exhausted on https://api.epicgames.dev/matchmaking/v1/c9ccbd00333f4dd6995beb7c75000942/sessions
2025-07-17T05:01:11 61.706 WRN [EOS] [LogEOS - Warning] Failed to connect to the backend. ServiceName=[Sessions], OperationName=[CreateSession], Url=[<Redacted>]

The problem is solved by a manual restart. But it is not convenient, because I can not serve the server 24/7. Hosting support assured that from their side they opened all the necessary ports and all firewall permissions. And this is understandable, because otherwise this error would have repeated after a manual restart, but this is not the case.

At the time of the error, I go to the EpicOnlineServices website and I don't see any information that they have any problems with their services.
Has anyone found the root of the problem and fixed it? Is this really a problem solely on the EOS side?
 
Willy, if you could provide the server logs, that would be helpful so the experts can take a look :)

SylenThunder

Thread 'HOW TO REPORT AN ISSUE ~~ Please Read Before Creating New Threads! ~~'

NOTE: This thread is resurrected from a very old version. I need to update it and make some changes, but it should be mostly correct.

Howdy folks,
If you're reading this, you're probably thinking about starting a thread for help with an issue. This post is intended for you to understand what we need in order to assist you properly, and how you can give it to us.
Threads created without the information outlined in this post are not likely to get you a good resolution. (Most likely you will simply be re-directed to this thread to get instruction on posting the information...
 
This error occurs when there is a communications issue with the Epic online server. I am finding if I ever see those messages in the output log file the server needs to be restarted.

EOS comes out of any number of data centers. I think Epic is having intermittant and sporadic datacenter issues causing the error to pop up from time to time and it has to do with DDOS and server loading issues on the Epic's end.

I have more concerns longer term when this game gets to be 20-30 years old and Epic drops support. Are we going to have to do a punkbuster esque workaround as the fans of Wolfenstein Enemy Territory did to work around the PunkBuster support removal?
 
You must log in or register to reply here.
Back
Top