Summary
Cannot enter UEFN sessions to test dev, I was getting region: NONE since the last update. It briefly returned to region: OCE. Now it has gone back to error region: NONE. Fortnite region auto has returned to 9,999 m/s
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Matchmaking
Steps to Reproduce
Fortnite times out with #5 error. UEFN with region: NONE error.
Expected Result
the usual server joining
Observed Result
I have tried a range of official fixes and community suggestions. Server joining is not working.
Platform(s)
windows
Additional Notes
Just re uploading this bug issue through the UEFN help/report issue feature, as it was suggested online this is the best way to do it. Apparently it sends logs? I’ve tried every trick, deleting appdata files/folders, net resets, restarts, router settings and got our isp to look in to it. Think I’ve exhausted ideas. Any tips please?
sorry, thought I could delete my previous post on the same bug (that can be closed), and keep this one which I assume is done properly through the Editor’s Report Issue feature.
there’s an Exclamation Mark over my top right player icon in the Fortnite menu. It appeared after trying to join servers, and not being able to, after the last update. Is that possibly related to all this? This is a bit frustrating
could it be a ‘sanction’ for a mistakenly uploaded texture that somehow triggered something else during the last update? I haven’t been able to join anything. The appeal function isn’t working either???!
I’ve gone over every possible network, file, official and developer tip I can find. I’ve spent days testing and restarting and getting my ISP to review things and paying for more services. There has been no email message of any issue, no comms. What on earth is going on?
Drat. The update seemed promising but it’s gone back to 9,999m/s Region connection. Think I’ve gone through every obvious fix and reinstall. Any qualified fixes would be wonderful. Bit of a bother
Output log in UEFN is showing this now (I have disabled Ipv6, seems to cause connection fails straight away):
Failed to connect to beacon
Your backend is: Fortnite
Your Build is: ++Fortnite+Release-41.00-CL-54872343
Region: OCE
BuildIdOverride is: 53972989
LogValkyrieRequestManagerEditor: Executing Step DestroyValkyrieBeacon
LogValkyrieRequestManagerEditor: Destroying valkyrie beacon
LogValkyrieSummary: Destroying Valkyrie Beacon
LogBeacon: Verbose: Destroying beacon ValkyrieBeaconClient_3, netdriver NULL
LogValkyrieRequestManagerEditor: Executing Step ClearFoundConnectInfo
LogHttp: Warning: 000002464204C400: request failed, libcurl error: 7 (Could not connect to server)
LogHttp: Warning: 000002464204C400: libcurl info message cache 0 (Hostname in DNS cache was stale, zapped)
LogHttp: Warning: 000002464204C400: libcurl info message cache 1 (Host datarouter.ol.epicgames.com:443 was resolved.)
LogHttp: Warning: 000002464204C400: libcurl info message cache 2 (IPv6: (none))
LogHttp: Warning: 000002464204C400: libcurl info message cache 3 (IPv4: 100.51.244.76, 98.85.20.139, 34.231.120.200, 3.94.17.116, 32.192.143.176, 3.232.183.245, 3.94.74.21, 54.237.140.172)
LogHttp: Warning: 000002464204C400: libcurl info message cache 4 ( Trying 100.51.244.76:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 5 (connect to 100.51.244.76 port 443 from 0.0.0.0 port 63671 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 6 ( Trying 98.85.20.139:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 7 (connect to 98.85.20.139 port 443 from 0.0.0.0 port 63672 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 8 ( Trying 34.231.120.200:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 9 (connect to 34.231.120.200 port 443 from 0.0.0.0 port 63673 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 10 ( Trying 3.94.17.116:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 11 (connect to 3.94.17.116 port 443 from 0.0.0.0 port 63674 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 12 ( Trying 32.192.143.176:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 13 (connect to 32.192.143.176 port 443 from 0.0.0.0 port 63675 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 14 ( Trying 3.232.183.245:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 15 (connect to 3.232.183.245 port 443 from 0.0.0.0 port 63679 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 16 ( Trying 3.94.74.21:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 17 (connect to 3.94.74.21 port 443 from 0.0.0.0 port 63683 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 18 ( Trying 54.237.140.172:443…)
LogHttp: Warning: 000002464204C400: libcurl info message cache 19 (connect to 54.237.140.172 port 443 from 0.0.0.0 port 63684 failed: Connection refused)
LogHttp: Warning: 000002464204C400: libcurl info message cache 20 (Failed to connect to datarouter.ol.epicgames.com port 443 after 16206 ms: Could not connect to server)
LogHttp: Warning: 000002464204C400: libcurl info message cache 21 (closing connection #196)
in command prompt I get this:
for %i in (98.89.180.114 98.82.222.243 44.205.229.155 3.221.106.132 100.51.44.115 34.194.78.187 54.164.235.152 98.87.46.51) do @powershell -NoProfile -Command “Write-Host ‘Testing %i’; if ((Test-NetConnection -ComputerName ‘%i’ -Port 443 -InformationLevel Quiet)) { Write-Host ‘%i : TCP 443 OK’ } else { Write-Host ‘%i : TCP 443 FAILED’ }”
Testing 98.89.180.114
WARNING: TCP connect to (98.89.180.114 : 443) failed
98.89.180.114 : TCP 443 FAILED
Testing 98.82.222.243
98.82.222.243 : TCP 443 OK
Testing 44.205.229.155
44.205.229.155 : TCP 443 OK
Testing 3.221.106.132
3.221.106.132 : TCP 443 OK
Testing 100.51.44.115
100.51.44.115 : TCP 443 OK
Testing 34.194.78.187
34.194.78.187 : TCP 443 OK
Testing 54.164.235.152
54.164.235.152 : TCP 443 OK
Testing 98.87.46.51
98.87.46.51 : TCP 443 OK
only one edge node is unreachable. I’m not sure how to proceed. If this helps anyone understand the connection issues I would appreciate any help thanks
@Flak Excuse me Flak for tagging you in this way, I’m not sure of the complete bug report process but have seen others tag you in with their bugs. I’ve had huge issues with being able to connect to beacon through our OCE Region. I think I’ve tried all the regular fixes. I think the logs point to a handshake issue with aws ports, perhaps just one? Is it possible for any engineers to take a look at this please, or is there another uncommon fix I might try? e.g. I tried adding the connecting tcp ports to my host file (hasn’t worked yet). Cheers
OK, it’s looking like it’s a local ISP issue despite their claims it is from Epic’s end. I’ll post anything I think might help others if I get a resolution.
Ok Dear Player, we’ve reached the end of this exciting self-humiliation quest. It wasn’t the ISP or Epic, it’s my ignorance again. Running through a fix checklist again got it, I must have missed it first time through. If you have this issue with not being able to connect to Epic Servers please try this if none of the other fixes help. For me it was a Service that was blocking connections to Epic Games servers. Specifically Portmaster Core Service, which is a networking 3rd party thing, though you may have something similar.
By testing connection to epic games through Command Prompt:
curl -v --connect-timeout 10 https://datarouter.ol.epicgames.com
you will get failed: Connection refused errors if a service or something is blocking it from your PC. If you try to connect to that address through the same router on a phone or other device and it gets through it is something on your PC causing the issue.
Run through the Clean Boot process thoroughly and methodically. Disable Startup apps. Open msconfig and hide all microsoft services. Disable all remaining services and restart. Try that Command Prompt, if it connects/gives a different msg than failed: Connection refused it is a Service that is blocking, check Fortnite and UEFN connect to confirm. Turn on half the services and restart and test methodically until you hit the Service causing the fail in Command Prompt. Keep adding half the remaining services, working down to the bad Service. test connection to epic games in Command Prompt until you get different replies than Connection refused.
Hope that helps someone. This has been a fortnight of Major Bother. Sorry for bothering any tech support for my issue. Kia ora, big up all past and present Epic team support.
You have complete this quest. Go to the forest and talk to the wizard in the hat. Create something cool.