Unable to tell what the relevance of this is, I’ve unfiltered all of my logs and I have been trying to trace if this is related to something going on in my game or if this is just on your (epic server/code) side? It’s been a few patches now so I figure i’d mention it as this isn’t filtered by default.
I tried unblocking the port, and turning off the reporting that it may have been associated with per a search on the forums to no avail.
I have heard multiple others confirm they’re having the same thing go on, but not enough for me to presume its everyone.
Felt like I may as well throw up a report.
Seeing as you probably know all of this i’ll leave it here and if you have any further questions just add additional context then.
( Trying 10.99.34.114:443...)
(ipv4 connect timeout after 7484ms, move on!)
LogHttp: Warning: 00000AA9BBEF2300: libcurl info message cache 6 (Failed to connect to horde.devtools-dev.epicgames.com port 443 after 30003 ms: Timeout was reached)
LogHttp: Warning: 00000AA9BBEF2300: libcurl info message cache 7 (Closing connection)
Steps to Reproduce
Open any session.
Expected Result
Unsure of what service is failing here, not sure what to expect.
It’s probably something we don’t yet have access to, and I have to imagine they added access control server side but didn’t add any client side handling to ensure that profiles that aren’t set to beta don’t send the request. Probably just need to add that handler w/ the flag check.
If you want to use Horde there is only one C++ class in API and its in 5.4 and its not Verse there isnt any 5.5 information
Effectively this comes from Epic.Hord.Tests file BufferTest.cpp which periodically test for the server and is part of UE5main the UE5 Developers repository.
There are references from UEFN to this code, but its not part of the standard UE 5.5 build
Take out maybe 100 for other initialization prints but getting this message 1,000 times probably isn’t right. The images it shows this for will complain about power of 2 or not having mipgensettings correct but they’ll be equivalent to other textures with the exact same settings.
Really unsure what this is indicative of or related to, but i’d like to fix it.
When moving files to different folders in the project, and then update revision control, I just get constant crashing.
Hi @LionUnchained all,
This is MY workaround to the problem does NOT fix it just reduces problem Warning if you use this you do at your risk.
Only do this only personal machines. If your on corporate domain ask your IT support.
This in effect slows the requests a burst of requests of about
8 every 3 minutes when using the Blank project
Go to Windows find Notepad right click “Run As Administrator”
open go to directory “C:\Windows\System32\drivers\etc”
open (drop down all files) called hosts add the line sown below
localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
::1 localhost
# slow rate of request by looping back to your PC add the line below
127.0.0.1 horde.devtools-dev.epicgames.com
save the file
Restart UEFN open Blank project you should see “Trying 127.0.0.1” port 443 rejected several times about every three minutes.
Checked and UEFN connection are not affected by this workaround still connect properly during netstat dump of activity
used netstat -b -n 3 seconds interval for 5 minutes
The workaround allows connection to 104.98.2.218:443 over 250 times before the error occurs
Looking at UE 5.5 source code Horde section looks like a request is being made
without the right authentication codes, using epic internal network there is a bypass this
For us indie devs on external network we see it all the time.
TCP 192.168.1.210:63471 3.228.40.2:443 SYN_SENT AMAZon
TCP 192.168.1.210:63437 104.98.2.218:443 ESTABLISHED AMAZON AWS
TCP 127.0.0.1:63483 127.0.0.1:1989 SYN_SENT
TCP 127.0.0.1:63505 127.0.0.1:443 SYN_SENT
TCP 127.0.0.1:63514 127.0.0.1:443 SYN_SENT
TCP 127.0.0.1:63453 127.0.0.1:63452 ESTABLISHED
TCP 127.0.0.1:63452 127.0.0.1:63453 ESTABLISHED
TCP 192.168.1.210:63497 146.75.74.217:443 ESTABLISHED
Had the same problem and kind of found the issue, turning off streaming in the world partition settings allowed me to enter a session. This is a streaming issue I suppose
