Still have the issue even though its off, might be multiple reasons for it happening
Did you found a fix for this?
I’m running 3 minute auto saves with a 10 second inactive time, i think aggressive auto saving is just a best practice as this point. The platforms pretty unstable right now.
Interesting. Is this still holding up for you. Also have you seen a decrease in push times by doing this?
hi @LionUnchained ,
There is no real increase in speed, but the connections are more reliable especially in 20:00 GMT, about 12:00 to 15:00 across the USA. The number of network errors are down. The problem is each region is getting different response times. My Fortnite/UEFN has “Network Debug” in the HUD display for Fortnite top left and hence ping timing on screen and there is a wireless icon which appears red when network errors occur now.
I am seeing the same errors. I have to constantly launch and exit a session until it eventually works.
Same issue
Upvoting this, it is still a problem.
Does there happen to be an update on this @Flak?
hi All @Flak ,
This is for the engineers whilst looking into Live Edit error, this appeared in the log in the build up to the failure.
LogHttp: Warning: 000005450D78C400: libcurl info message cache 0 ( Trying 10.99.34.28:443...)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 1 (ipv4 connect timeout after 14879ms, move on!)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 2 ( Trying 10.99.35.112:443...)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 3 (ipv4 connect timeout after 7438ms, move on!)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 4 ( Trying 10.99.34.154:443...)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 5 (ipv4 connect timeout after 7436ms, move on!)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 6 (Failed to connect to horde.devtools-dev.epicgames.com port 443 after 30000 ms: Timeout was reached)
LogHttp: Warning: 000005450D78C400: libcurl info message cache 7 (Closing connection)
LogHttp: Warning: 000005450D781500: request failed, libcurl error: 28 (Timeout was reached)
LogHttp: Warning: 000005450D781500: libcurl info message cache 0 ( Trying 10.99.50.52:443...)
LogHttp: Warning: 000005450D781500: libcurl info message cache 1 (ipv4 connect timeout after 14829ms, move on!)
LogHttp: Warning: 000005450D781500: libcurl info message cache 2 ( Trying 10.99.51.25:443...)
LogHttp: Warning: 000005450D781500: libcurl info message cache 3 (ipv4 connect timeout after 7414ms, move on!)
LogHttp: Warning: 000005450D781500: libcurl info message cache 4 ( Trying 10.99.50.208:443...)
LogHttp: Warning: 000005450D781500: libcurl info message cache 5 (ipv4 connect timeout after 7412ms, move on!)
LogHttp: Warning: 000005450D781500: libcurl info message cache 6 (Failed to connect to horde.devtools.epicgames.com port 443 after 30000 ms: Timeout was reached)
LogHttp: Warning: 000005450D781500: libcurl info message cache 7 (Closing connection)
From my point of view, the code on UEFN is going through a list of available servers. The response time is checked and if too high the comment is “move on”.
For example the name " horde.devtools-dev.epicgames.com" is now assigned to 10.99.34.154:443 the next Cache Server eventually reaching Cache Server 7 and still the latency is not good enough so after Cache server 7 cannot “move on” to the connection is closed.
This results in “horde.devtools-dev.epicgames.com” will NEVER have an IP address assigned to forever, because there are NOT any Amazon servers in EMEA (LONDON, IRELAND, MILAN) which are capable of supporting Fortnite.
In Europe, we developers have to put up with high latency and deal with this in our code and our Cloud servers
any solution??
hi all,
The problem is fixed in the 30.30 update arrived 16:03 GMT 08:00 PST 24th July 24
Thank you for voting this thread up
Community Bugfixes section 30.30 Fortnite Ecosystem Updates and Release Notes
Community Bug Fixes
The following list of fixes are from issues that you submitted to us on the forums. Thank you for your patience and for reporting these issues!
- Improved Launch Session reliability when connecting to server.
- Forum Issue Report
Testing on UEFN 30.30 Logs does not have any errors “horde.” not found
“https://content-service.bfda.live.use1a.on.epicgames.com” now works quickly
Update
Similar problems were encountered in 30.40 and this was to do with browser caching of login details someone asked how to clear browser cache on MS Edge
Restart the PC after clearing cache
This is a similar problem for the other browsers. Find out how to manually clear the browser cache.
In the case of the error, another IP address was now being used
1 Like
Thank you 
hi all,
While this is a little off topic, another Indie Dev has sent me a Fortnite T-shirt.
Forgot his name so posting thanks here.
Dev thought it was this problem, The fix was NOT about this problem but about the need to “Verify” the installation
Exported from US and others have challenged me to wear the t-shirt. They make them for Dads as well La Grande. XXL
So it is me in a UK English Public House holding a pint (452ml 
) of Green King IPA Beer wearing a Fortnite T-shirt
2 Likes