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