"Failed to connect to beacon" upon launching session

General Issues and Bug Reporting
, , ,
1

Summary

Been getting this nonstop since the update. It goes away for a few hours, then comes back and leaves me unable to launch a session for hours. The entire message reads:
“Failed to connect to beacon Your backend is: Fortnite Your Build is: ++Fortnite+Release-41.00-CL-54618515 Region: BR BuildIdOverride is: 53972989”

This had never happened to me in past versions and my internet connection is 100% stable and well. I’ve restarted UEFN, my PC, and tried restarting the sesion dozens of times to no avail.

Our latest priv island code is 6066-8406-6239

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Stability

Steps to Reproduce

Intermittent issue.

  1. Start up UEFN
  2. Try to start a session
  3. Get stuck on “loading” until the client accuses ‘matchmaking failure’ and the editor accuses a failed connection with the aforementioned log.

Expected Result

Expected not to have issues starting a session.

Observed Result

Had issues starting a session.

Platform(s)

PC

Island Code

6066-8406-6239

3

I’m getting this too for the EU region
When launching session i’m unable to move at all and then get a matchmaking error

4

Had the same issue today, sometimes it worked, sometime not.

‘‘Failed to connect to beacon
Your backend is: Fortnite
Your Build is: ++Fortnite+Release-41.00-CL-54872343
Region: EU
BuildIdOverride is: 53972989’’

I also tried to launch a session multiple times on a blank new project and it worked all the time.
It could be random, but it seems like this issue does more often occure on older/bigger projects.

5

This is happening to me as well.

6

yh same thing

7

Same issue over here

8

hi all,

Please try the known problem first

v41.00 Known Issues & Pre-Release Updates - General / Issues and Bug Reporting - Epic Developer Community Forums

if that fails

  • please clear the following directory and try again.

%LOCALAPPDATA%/UnrealEditorFortnite/Intermediate/ValkyrieLocalizationTemp

  • please clear the following directory and try again.

%LOCALAPPDATA%/UnrealEditorFortnite/Intermediate/ValkyrieValidationTemp

In past clearing the above directories as these are related to the Valkyrie Beacon problems

10

If this is still occurring could you attach your logs after reproducing it? How to get your Fortnite logs

11

FORT-1114640 has been ‘Backlogged’. This is an issue that is in a queue to be addressed.

12

I tried to upload them, but my file is too large

13

I’m getting this again.
Weirdly, it only happens if I add any changes to my project.

If I revert to how it was before getting these errors it launches just fine and can start a game, but If I change anything my game freezes after pressing Start Game and then I just get kicked to lobby and get the beacons error.

14

I’ve seen other developers use google drive to get around the file size limit on the forums if you’re able to do that.

15
16

Hi started to having this problem today. Do you know how to fix it

17

I have this issue too, did you find a way to fix it?

18

I’m experiencing what appears to be the same issue on UEFN 43.00 (November 10, 2026).

Every attempt to launch an edit session fails after approximately 31 seconds. Matchmaking/session creation succeeds, but the connection to the Valkyrie beacon times out, and Fortnite reports a lost network connection.

Troubleshooting completed:

  • Reproduced across multiple UEFN projects.

  • Reproduced against at least three different Epic session-server IP addresses.

  • Reproduced on both home internet and a cellular hotspot.

  • Restarted Fortnite, UEFN, and Epic Games Launcher.

  • Cleared Valkyrie temporary directories.

  • Verified DNS resolution and HTTPS connectivity to Epic services.

  • Found no explicit outbound firewall block rules for Fortnite or UEFN.

  • Asset validation and Verse compilation succeed.

The failure is consistently around 31 seconds regardless of network or project. I also observed an InstallBundleManager RootDownloadError in a Fortnite client log, though I haven’t established whether it’s related.

Is FORT-1114640 still being investigated, and are there additional diagnostics that would help isolate this failure?

19

hi @RumboMutumbo

Please check Windows Defender or anti virus not blocking.

Remove VPN software will be blocked by Fortnite

Exception Registration and then Verify UEFN/Fortnite

20

I’m still unable to launch any UEFN edit session as of November 11, 2026, using UEFN/Fortnite 43.00.

Problem:

Every launch attempt consistently fails during the Downloading stage after approximately 31 seconds. Fortnite remains on “Loading into your Edit Session” before reporting a lost network connection.

UEFN successfully completes preparation, validation, upload, and cooking. The failure occurs when establishing the connection to the edit-session server.

This has persisted since November 8.

Troubleshooting performed without success:

  1. Restarted Fortnite, UEFN, Epic Games Launcher, and terminated lingering Fortnite/UEFN processes using PowerShell.

  2. Reproduced the failure across multiple UEFN projects, including an unrelated project.

  3. Reproduced the failure against three different Epic session-server IP addresses: 3.148.47.196, 3.144.63.66, and 18.88.26.134.

  4. Tested both my home internet connection and a cellular phone hotspot. Both fail identically at approximately 31 seconds.

  5. Cleared ValkyrieValidationTemp and ValkyrieLocalizationTemp from UEFN’s Intermediate directory.

  6. Checked Windows WinHTTP proxy configuration: direct connection, no proxy.

  7. Tested DNS resolution using default DNS, Cloudflare (1.1.1.1), and Google (8.8.8.8). All successfully resolved Epic’s launcher download hostname.

  8. Tested TCP port 443 and HTTPS connectivity to launcher-public-service-prod06.ol.epicgames.com and mcp-gc.live.fngw.ol.epicgames.com. Both connected successfully and returned HTTP responses.

  9. Checked Windows Firewall profiles and explicit outbound blocking rules. No Fortnite, UEFN, or Epic Games outbound block rules were found.

  10. Checked Microsoft Defender Protection History. No relevant quarantines or blocks were shown.

  11. Checked for common VPN software and virtual network adapters. None were detected.

Additional observations:

  • The Fortnite client logged UE::InstallBundleManager errors, including RootDownloadError and a libcurl error 6 hostname-resolution failure during one startup. Later DNS and HTTPS tests passed, so it’s unclear whether that error is related to the session failure.

  • UEFN logs show static-mesh LOD warnings, but validation succeeds.

  • The failure is independent of the project’s Verse code and occurs in an unrelated UEFN project as well.

I have not yet completed a Wireshark packet capture.

Can Epic confirm whether FORT-1114640 is still active and identify what causes the Valkyrie beacon handshake to time out consistently after 31 seconds?