Unable to join Fortnite servers... but all systems operational?

enealefons · June 14, 2024, 11:27pm

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Matchmaking

Summary

Dearest UEFN team, today I’m experiencing degraded connectivity to the Fortnite Servers.
I checked https://status.epicgames.com/ and seems like everything is OK… but still doesn’t let me join Fortnite servers.
Since it really takes long… it feels like timeout.
My internet connectivity is fine… Am I the only one with this problem today?

I’m working on a complex Verse project and I’m keeping relaunching in a bid to connect… should I chill instead?

Steps to Reproduce

Launch session from UEFN, connection takes very long and eventually fails.

Expected Result

When launching a session from UEFN, it should connect

Observed Result

connection takes very long and eventually fails.

Platform(s)

UEFN + Windows

enealefons · June 15, 2024, 12:50am

after 3 hours trying to connect to a game session to test and iterate verse work… I have to give up.

I hope in a few hours we will be able to login!

enealefons · June 15, 2024, 5:47am

S T I L L
N O T
C O N N E C T I N G

The struggle is un R E A L

enealefons · June 16, 2024, 6:52pm

The above “spotty joining experience” still persists…

…Also, if I click “Relaunch” immediately… I am rewarded with LS-0018 .

If this user experience is designed to teach devs about the virtues of PATIENCE… well done.

Otherwise, would be nice to know if I can do anything to improve the situation.

AlreadyRunning

Mineblo · June 16, 2024, 9:16pm

Possible Fixes:

Task manager Fortnite,Unreal Editor and urc.exe
If you already have UEFN opened you can try to launch a session with the Launch PC option selected which can sometimes ovveride the Fortnite is Already Running.

enealefons · June 16, 2024, 9:32pm

Thank you Mineblo!

Issue still persists, with super slow launch and connection times… (3 to 5 minutes!)
followed 70% of the times by

“unable to join fortnite servers, please try again later”

And yes, the situation already brought me to experience clicking all buttons available to launch a session, experimented with all sorts of combinations

So far only trying again and again and again and again and again… sometimes allows me to get through.

#frustrating

Bug-Reporter · June 18, 2024, 1:18am

The status of FORT-759159 incident has been moved from ‘In Testing’ to ‘Closed’. Resolution Reason: ‘Cannot Reproduce’

latundaPC · June 18, 2024, 1:21am

I cant launch uefn, I am logged in, but it says I need a valid login. I tested with 2 accounts. Both fail.

in logs I get:

[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: request failed, libcurl error: 60 (SSL peer certificate or SSH remote key was not OK)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 0 (Hostname account-public-service-prod.ol.epicgames.com was found in DNS cache)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 1 (  Trying 54.224.96.151:443...)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 2 (Connected to account-public-service-prod.ol.epicgames.com (54.224.96.151) port 443)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 3 (ALPN: curl offers http/1.1)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 4 (TLSv1.3 (OUT), TLS handshake, Client hello (1):)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 5 (TLSv1.3 (IN), TLS handshake, Server hello (2):)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 6 (TLSv1.2 (IN), TLS handshake, Certificate (11):)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 7 (TLSv1.2 (OUT), TLS alert, unknown CA (560):)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 8 (SSL certificate problem: unable to get local issuer certificate)
[2024.06.18-01.04.58:353][416]LogHttp: Warning: 000005CA6DF50700: libcurl info message cache 9 (Closing connection)
[2024.06.18-01.04.58:353][416]LogOnline: Warning: OSS: Http Unexpected Result: HttpResult: 0 Code: 0 Error: Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
[2024.06.18-01.04.58:353][416]LogOnline: Warning: MCP: Invalid response. CorrId=FN-qpp8jtBmSEOmf7x5ja59vw code=0 error=Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
[2024.06.18-01.04.58:353][416]LogOnlineIdentity: Warning: MCP: Client auth request failed. Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
[2024.06.18-01.04.58:388][428]LogOnline: Warning: OSS: Http Unexpected Result: HttpResult: 0 Code: 0 Error: Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
[2024.06.18-01.04.58:388][428]LogOnline: Warning: MCP: Invalid response. CorrId=FN-mSutZzPn-0CS1cm6F-NTAQ code=0 error=Failure ErrorCode=errors.com.epicgames.online.generic.connection_failure, Message=Connection to the server failed., Raw=connection_failure
[2024.06.18-01.04.58:388][428]LogOnline: Warning: MCP: Triggering failed connection status change for service [fortnite] to status [ConnectionDropped], due to http status [0]
[2024.06.18-01.04.58:388][428]LogOnline: MCP: Service status updated [Normal] -> [ConnectionDropped]

Flak · June 18, 2024, 1:01pm

@enealefons and @latundaPC could we get your full logs?

enealefons · June 18, 2024, 4:25pm

Sure! @Flak ! Can you give me your mail, so that I can send the full logs over?
Thank you for checking this out!

here’s an excerpt:

time="2024-06-17T19:38:24+02:00" level=warning msg="error running fortnite: exit status 0x40010004\n"
time="2024-06-17T19:38:24+02:00" level=fatal msg="error running fortnite: 1073807364"
time="2024-06-18T19:46:41+02:00" level=info msg="started FortniteLauncher"
time="2024-06-18T19:46:41+02:00" level=info msg="loaded caldera-service public key"
time="2024-06-18T19:46:41+02:00" level=info msg="launched with command line args:"
time="2024-06-18T19:46:41+02:00" level=info msg="[C:/Program Files/Epic Games/Fortnite/FortniteGame/Binaries/Win64/FortniteLauncher.exe -obfuscationid=rnJQg-XoHR5F1iHfBUya15nic8MimA -epicenv=Prod -epicapp=Fortnite -epicusername=**********-epicuserid=*******************-epiclocale=en -epicsandboxid=fn -EOSArtifactNameOverride=Prod -Res=1920x1080w -VK.JoinEditOnLaunch -epicportal -skippatchcheck -AUTH_LOGIN=unused -AUTH_TYPE=exchangecode -AUTH_PASSWORD=23215930f5364f1ab56a3eae65e972e6]"
time="2024-06-18T19:46:41+02:00" level=info msg="requesting anticheat provider"
time="2024-06-18T19:46:41+02:00" level=info msg="checking anticheat configuration for battleye"
time="2024-06-18T19:46:41+02:00" level=info msg="checking anticheat configuration for eac eos"
time="2024-06-18T19:46:41+02:00" level=info msg="preparing to run fortnite"
time="2024-06-18T19:46:41+02:00" level=info msg="running fortnite: FortniteClient-Win64-Shipping_EAC_EOS.exe -obfuscationid=rnJQg-XoHR5F1iHfBUya15nic8MimA -epicenv=Prod -epicapp=Fortnite -epicusername=*************-epicuserid=***************-epiclocale=en -epicsandboxid=fn -EOSArtifactNameOverride=Prod -Res=1920x1080w -VK.JoinEditOnLaunch -epicportal -skippatchcheck -AUTH_LOGIN=unused -AUTH_TYPE=exchangecode -AUTH_PASSWORD=*********************-nobe -noeac -fromfl=eaceos -caldera=eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJhY2NvdW50X2lkIjoiNzY2NzYyYzM2ZmMwNGNlY2FkZDgzNTQyNmE4OGZlMzQiLCJnZW5lcmF0ZWQiOjE3MTg3MzI4MDIsImNhbGRlcmFHdWlkIjoiYWYxNTI5ODgtMzljOS00MzRkLTkzN2YtZWZiZmRjYTBjNjBiIiwiYWNQcm92aWRlciI6IkVhc3lBbnRpQ2hlYXRFT1MiLCJub3RlcyI6IiIsInByZSI6dHJ1ZSwiZmFsbGJhY2siOmZhbHNlfQ.c5a3mJnKG6DfpHfGwsVpYsFyowRpT6ZzSjWEWaq8FqCYNHNzz2qDuiPzRGSa1qkdIvVpYxXEN5h3Lw6Diww9RA\n"```

latundaPC · June 18, 2024, 8:20pm

I already deleted them.

If anyone has the same problem (both uefn and fortnite fail to launch), try this:

ipconfig /flushdns

if it does not help, in the Epic Game Launcher, sign out, then sign in. Then:

ipconfig /flushdns

You should be able to launch without errors now.

latundaPC · June 18, 2024, 10:12pm

(post deleted by author)

enealefons · June 19, 2024, 1:24am

Thank you for the suggestion @latundaPC !
I tried it but… doesn’t work in my case, still same situation.

enealefons · June 19, 2024, 1:48am

more waiting and relaunching… more logs

[2024.06.19-01.46.21:908][815]LogDLSSNGXRHI: NGXRHI::ReleaseAllocatedFeatures Leave
[2024.06.19-01.46.21:908][815]LogDLSSNGXD3D12RHI: NVSDK_NGX_D3D12_DestroyParameters -> (1 NVSDK_NGX_Result_Success)
[2024.06.19-01.46.22:027][815]LogDLSSNGXD3D12RHI: NVSDK_NGX_D3D12_Shutdown -> (1 NVSDK_NGX_Result_Success)
[2024.06.19-01.46.22:027][815]LogDLSSNGXD3D12RHI: FNGXD3D12RHI::~FNGXD3D12RHI Leave
[2024.06.19-01.46.22:027][815]LogDLSSNGXRHI: NGXRHI::~NGXRHI Enter
[2024.06.19-01.46.22:027][815]LogDLSSNGXRHI: NGXRHI::~NGXRHI Leave
[2024.06.19-01.46.22:027][815]LogDLSS: FDLSSModule::ShutdownModule Leave
[2024.06.19-01.46.22:027][815]LogDLSSNGXRHI: FNGXRHIModule::ShutdownModule Enter
[2024.06.19-01.46.22:027][815]LogDLSSNGXRHI: FNGXRHIModule::ShutdownModule Leave
[2024.06.19-01.46.22:029][815]LogVerseSaveService: VOS: FVerseSaveService::Uninitialize called.
[2024.06.19-01.46.22:036][815]LogElastiquePitchShifterModule: Module Shutdown
[2024.06.19-01.46.22:039][815]LogWebAuth: Display: FWebAuthModule::ShutdownModule:
[2024.06.19-01.46.22:042][815]LogFort: Display: AC console objects: cleanup
[2024.06.19-01.46.22:043][815]LogAudioModulation: Audio Modulation Shutdown
[2024.06.19-01.46.22:045][815]LogGauntlet: Gauntlet Shutdown
[2024.06.19-01.46.22:051][815]BuildPatchServicesModule: Shutting Down
[2024.06.19-01.46.22:051][815]VeryVerbose: BuildPatchServicesModule: Removing Ticker
[2024.06.19-01.46.22:051][815]VeryVerbose: BuildPatchServicesModule: Finished shutting down
[2024.06.19-01.46.22:053][815]LogGfeSDK: 2024-06-19T03:46:22.054[I] GAME        Controller.cpp:121  Posted Request Destroy[12237f7d]

[2024.06.19-01.46.22:053][815]LogGfeSDK: 2024-06-19T03:46:22.054[I] GAME        Controller.cpp:257  LEAVE IPC

[2024.06.19-01.46.22:053][815]LogGfeSDK: 2024-06-19T03:46:22.054[I] TASK        TaskRunner.cpp:167  Shutting down TaskRunner thread

[2024.06.19-01.46.22:053][815]LogGfeSDK: 2024-06-19T03:46:22.054[I] TASK        TaskRunner.cpp:52   Stopping TaskRunner thread. Flushing notifications

[2024.06.19-01.46.22:053][815]LogGfeSDK: 2024-06-19T03:46:22.054[I] TASK        TaskRunner.cpp:63   Stopped TaskRunner thread

[2024.06.19-01.46.22:054][815]LogGfeSDK: 2024-06-19T03:46:22.055[D] GAME       FactoryImpl.cpp:77   Release shared messagebus interface directly

[2024.06.19-01.46.22:064][815]LogGfeSDK: 2024-06-19T03:46:22.065[I] GAME         HandleMap.cpp:56   Releasing handle 1 from handle map, pointed to 00000141F836FF30

[2024.06.19-01.46.22:064][815]LogGfeSDK: 2024-06-19T03:46:22.065[I] GAME              Core.cpp:35   Destroyed GfeSDK

[2024.06.19-01.46.22:065][815]LogSVGF: FSVGFModule::ShutdownModule
[2024.06.19-01.46.22:065][815]LogDLSSNGXVulkanRHIPreInit: FNGXVulkanRHIPreInitModule::ShutdownModule Enter
[2024.06.19-01.46.22:065][815]LogDLSSNGXVulkanRHIPreInit: FNGXVulkanRHIPreInitModule::ShutdownModule Leave
[2024.06.19-01.46.22:075][815]LogOnline: MCP: Mcp Shutdown!
[2024.06.19-01.46.22:084][815]LogHttp: Warning: [FHttpManager::Shutdown] Unbinding delegates for 3 outstanding Http Requests:
[2024.06.19-01.46.22:084][815]LogHttp: Warning: 	verb=[POST] url=[https://datarouter.ol.epicgames.com/datarouter/api/v1/public/data?SessionID=%7BD8805E5C-4CF5-84BF-DC8A-5786DF62A4ED%7D&AppID=Fortnite.Fortnite&AppVersion=30.10.0%20-%20%2B%2BFortnite%2BRelease-30.10-CL-34399867&UserID=a94c05d24db7b79f7974acbb2e5a0a2a%7C%7C2b5c3be3-5142-448e-addf-db2d72b72d54%7C%7C&AppEnvironment=Prod&UploadType=eteventstream] refs=[3] status=Processing
[2024.06.19-01.46.22:084][815]LogHttp: Warning: 	verb=[POST] url=[https://datarouter.ol.epicgames.com/datarouter/api/v1/public/data?SessionID=%7BD8805E5C-4CF5-84BF-DC8A-5786DF62A4ED%7D&AppID=Fortnite.Fortnite&AppVersion=30.10.0%20-%20%2B%2BFortnite%2BRelease-30.10-CL-34399867&UserID=a94c05d24db7b79f7974acbb2e5a0a2a%7C%7C2b5c3be3-5142-448e-addf-db2d72b72d54%7C%7C&AppEnvironment=Prod&UploadType=eteventstream] refs=[3] status=Processing
[2024.06.19-01.46.22:084][815]LogHttp: Warning: 	verb=[DELETE] url=[https://account-public-service-prod.ol.epicgames.com/account/api/oauth/sessions/kill/eg1~eyJraWQiOiJnX19WS2pTU21xSjB4WmoxUllrTEdLUTdkbkhpTTlNTGhGVndLUHlTREI0IiwiYWxnIjoiUFMyNTYifQ.eyJwIjoiZU5xdGs4bE9BekVNaHQrblFraGxPMWlhQTB0Qm5FQkM0am95aVdkcU5lTlVpVlBvMitOaEdTaExCeENuYkY3Ky8wdlN4S1RDU3VCQ0xENXJUTmdTNUhWVzZ1Q2NVRXNpZjVrRGlqL1k1YWV4bWg3dE5EOVAyeDlOSzVrU3VDZ050OVhlOXRLM2k1bG5QU1BQRHBYOERhVVZwUXZzYUplRlI0WGRMcTREcnJka1k5TndZRHVEWmJrTDdHRFlHQkUycHZ0ZkZjK2taUm55QXhaeGN5UG80NzJFaUI0Q3J3Z21KaWxIeHhoQUNic01rcUdSNm1qSENtR0lMZVE1MmgxQmJCcEsyWUkvMTVuQStZdTIweWhLb2llRmcrOWowYmxZUkFkS3o4dHEraXNJbXpaZVMwWXNPZ2Q2MFBwcGNrK3RzWUtFSE9wTU9YT1VXdGt0U0t2RDdkMTZBRlFDYWtLM1lCa00ydzVseFRZUmRlYnBzNXUyWVBLTWtzM1AxMFo3ZVpRRXc3Rkp2Skt3dHNnUFdDZnY2cjZNMllCMnBPZ3RFdWJMdW4vMk5mdDZtYUwvMDd2ZkJQaUxMemw5OXlWTnhJb2RzUmdUY2ZRTnRBSFgzZG9hOTdjd3BuaXo0OTVieDBkVUVMSzUiLCJjbHN2YyI6InByb2QtZm4iLCJ0IjoicyIsIm12ZXIiOmZhbHNlLCJjbGlkIjoiZWM2ODRiOGM2ODdmNDc5ZmFkZWEzY2IyYWQ4M2Y1YzYiLCJpYyI6dHJ1ZSwiZXhwIjoxNzE4Nzc1NzExLCJhbSI6ImNsaWVudF9jcmVkZW50aWFscyIsImlhdCI6MTcxODc2MTMxMSwianRpIjoiNWU4Nzc1MDZiZmEzNGQ2M2JmY2Y3NWMzNzM3NjMzNDIiLCJwZnBpZCI6InByb2QtZm4ifQ.tVGfX-sUJHjG3yZtyVPtwnLcatTCSvF7XdGVj7s47mKzqcHoCr7xz7I34WXft3dT8kMGrSxfLArz4OSs-x-oUQZ8fgy1730HTeCBfyinS97jEb_J4nyEpIQuAIySnmJcthc8xn8_cOuM9Nrtp20aoVvddYHUf5vfA5ldoDJJxvAMY8tw-bhvOsYKpMQ8PYnAo2uGfivzf0ix2LQtnX-gFE1_FA3zbwAMxVsasoN1MNuWmpSXCqppAqBM10rAcah5mYMzO1mYVn9y3AZw-6rxdAUfvx5t1AIKqIlPmmaBSCEA11_AE1_R-CsuuEIlLuziH9pudhYcDew7MRyM4xTE1-_zGNaoTYwvQadtvYpQVtdpT_C3mq2BOH9Gw5Sfv-tXkFdUnTlDqyDb_qZw7TBL2vYjnQJidgenGG9AeMQ_dRPcA4eDsvX8h1kdg0FSbfnouuKRuyn1orNStpG1fyKUbe8GFH16M3fpT7lF7BQNQ06USmuVGZL1JV9MJO2UNamD9p9-aIlqsxtGe1l9__SN9WVdM1X6wy9P9QZJygwKTavDgT2gVGEdRxA6lYDWAg3AF-LylWsuqIK9oPmmiTVsslauMpMr6SNo5JzZLszb4Z-Wk4lxyoTJCwvz9aduuD2vhRShkZTXt2jzk0zbHxwsgU6bfGWlqeYyCWX6Z3qyArQ] refs=[2] status=Processing
[2024.06.19-01.46.22:085][815]LogHttp: Warning: 	Sleeping 0.500s to wait for 1 outstanding Http Requests.
[2024.06.19-01.46.22:615][815]LogEOSSDK: LogEOSRTC: [Core] Shutting down LibRTC...
[2024.06.19-01.46.23:186][815]LogEOSSDK: FEOSSDKManager::Shutdown EOS_Shutdown Result=[EOS_Success]
[2024.06.19-01.46.23:194][815]LogPakFile: Destroying PakPlatformFile
[2024.06.19-01.46.23:986][815]LogD3D12RHI: ~FD3D12DynamicRHI
[2024.06.19-01.46.24:000][815]LogExit: Exiting.
[2024.06.19-01.46.24:146][815]Log file closed, 06/19/24 03:46:24

enealefons · June 19, 2024, 2:03am

Another way to get my timeout error

another sleepless night trying to test my Verse work…

E M O T I O N A L
D A M A G E

enealefons · June 19, 2024, 4:55am

FYI, I really tried everything

no proxy
no vpn
router reset
cabled
cabled + wi fi
private wi-fi

connection still times out. In 5 hours I managed to run my project only once.

enealefons · June 19, 2024, 9:20am

FYI, out of slighly masochistic determination to make it work
(In theory I should be teaching Verse to some clients by showing them working examples, so I’m not giving up)

I performed “Verify Files” on UEFN and Fortnite files via launcher
checked Ping to relevant epic servers (35 eu, 125 us)
following https://www.epicgames.com/help/en-US/c-Category_EpicGamesStore/c-EpicGamesStore_LauncherSupport/how-to-unblock-ports-to-connect-to-the-epic-games-launcher-and-fortnite-a000084740 I opened 80, 433, 443, 3478, 3479, 5060, 5062, 5222, 6250, and 12000-65000
tried adding these arguments as “launch options” -limitclientticks -nomoviestartup -lanplay

Still same results: super long connection times, followed by “unable to join Fortnite servers” 8 times out of 10.

On a positive note, 8 out of 10 is statistically better than most slot machines…

Jokes apart, is there anything else I can try in the rational field… or should I start with Palo Santo smudging?

davidpkami · June 19, 2024, 10:05am

My project can not launch due errors with the connection

LogHttp: Warning: 00000AD8FBF35400: request failed, libcurl error: 28 (Timeout was reached)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 0 (  Trying 10.99.35.94:443...)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 1 (ipv4 connect timeout after 14959ms, move on!)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 2 (  Trying 10.99.34.44:443...)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 3 (ipv4 connect timeout after 7479ms, move on!)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 4 (  Trying 10.99.34.166:443...)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 5 (ipv4 connect timeout after 7479ms, move on!)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 6 (Failed to connect to horde.devtools-dev.epicgames.com port 443 after 30000 ms: Timeout was reached)
LogHttp: Warning: 00000AD8FBF35400: libcurl info message cache 7 (Closing connection)
LogHttp: Warning: 00000AD8FBF36900: request failed, libcurl error: 28 (Timeout was reached)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 0 (  Trying 10.99.51.118:443...)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 1 (ipv4 connect timeout after 14970ms, move on!)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 2 (  Trying 10.99.51.79:443...)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 3 (ipv4 connect timeout after 7484ms, move on!)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 4 (  Trying 10.99.50.87:443...)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 5 (ipv4 connect timeout after 3742ms, move on!)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 6 (  Trying 10.99.50.73:443...)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 7 (ipv4 connect timeout after 1869ms, move on!)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 8 (  Trying 10.99.50.195:443...)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 9 (ipv4 connect timeout after 934ms, move on!)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 10 (  Trying 10.99.50.144:443...)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 11 (ipv4 connect timeout after 934ms, move on!)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 12 (Failed to connect to horde.devtools.epicgames.com port 443 after 30000 ms: Timeout was reached)
LogHttp: Warning: 00000AD8FBF36900: libcurl info message cache 13 (Closing connection)
LogHttp: Warning: 00000AD8FBF31C00: request failed, libcurl error: 28 (Timeout was reached)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 0 (  Trying 10.99.34.166:443...)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 1 (ipv4 connect timeout after 14991ms, move on!)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 2 (  Trying 10.99.34.44:443...)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 3 (ipv4 connect timeout after 7495ms, move on!)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 4 (  Trying 10.99.35.94:443...)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 5 (ipv4 connect timeout after 7495ms, move on!)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 6 (Failed to connect to horde.devtools-dev.epicgames.com port 443 after 30003 ms: Timeout was reached)
LogHttp: Warning: 00000AD8FBF31C00: libcurl info message cache 7 (Closing connection)
LogHttp: Warning: 00000AD8FBF35B00: request failed, libcurl error: 28 (Timeout was reached)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 0 (  Trying 10.99.50.87:443...)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 1 (ipv4 connect timeout after 14962ms, move on!)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 2 (  Trying 10.99.50.73:443...)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 3 (ipv4 connect timeout after 7479ms, move on!)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 4 (  Trying 10.99.50.195:443...)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 5 (ipv4 connect timeout after 3738ms, move on!)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 6 (  Trying 10.99.51.79:443...)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 7 (ipv4 connect timeout after 1868ms, move on!)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 8 (  Trying 10.99.51.118:443...)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 9 (ipv4 connect timeout after 933ms, move on!)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 10 (  Trying 10.99.50.144:443...)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 11 (ipv4 connect timeout after 933ms, move on!)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 12 (Failed to connect to horde.devtools.epicgames.com port 443 after 30003 ms: Timeout was reached)
LogHttp: Warning: 00000AD8FBF35B00: libcurl info message cache 13 (Closing connection)

Logs.zip (15.7 MB)

enealefons · June 19, 2024, 10:14am

you are not alone…
…welcome to the club

EDIT:

from https://status.epicgames.com/

latunda · June 19, 2024, 7:25pm

For me it worked both times before and after the extra update. I had to wait a little longer the second time but was able to launch test and publish my game yesterday. Both times I logged out/in before running the command.

Ii might be epic also worked on the problem at the same time, so I am not sure if it was luck