Session not starting

I’m adding an update because the issue of UEFN being unable to start a session has recurred.

・I previously mentioned that UEFN was able to start a session after I updated my graphics card drivers, but unfortunately, UEFN is now unable to start a session again.
・Following that, I reinstalled both UEFN and Fortnite. This allowed UEFN to start a session once, but the problem has since returned, and UEFN is again unable to start a session.
・It’s worth noting that I’m currently still able to start the game using a private code in my environment.

1 Like

I believe issuing a private code and testing it on Fortnite is a good workaround as well.
However, I’ve encountered that this approach does not always work perfectly.
In the end, crashes or network connection errors may still occur.

For now, it’s still better than starting a game session directly from UEFN. :sweat_smile:

1 Like

@moderators

Can someone from the staff respond, please?
Frustration among creators is building up significantly.
Does voting not make much of a difference?

2 Likes

Hello, if you get an error after the “connecting” loading screen, you must select the “Creative Mode” epic island. Once you’re in the hub, enter the island you have selected. Within your Creative Mode island, without exiting it, click “Login” in UEFN and you’ll be logged in. (This doesn’t always work.)

Here to say I’ve been stuck with this as well for the past few days… My workaround was to just upload private versions but that’s tedious when having to debug Verse code. Hopefully now that the weekend’s over the devs can finally look at this issue

1 Like

i have been dealing with this issue for 3 days
a lot of infinite loading screen and when i do get it there is nothing but issues and devices not working properly or not working at all and bugs ranging from the start button not showing in game to the creative phone showing when the game starting or the phase mod showing in game,

creating a second island don’t help, verifying the game and uefn don’t help
not sure what to do i even got an easy anti cheat error it’s totally broken :melting_face:

1 Like

I’m experiencing the same thing.
I thought it was just me bc there were no bug report posts at the time so I started a support ticket.
In that ticket I’ve given my fortgame.log and dxdiag.txt.
If I get a solution there I’ll update my posts.
I also made a report here:

1 Like


Also can’t launch sessions.. just gets stuck on connecting.

1 Like

@Flak

1 Like

This fixed it for me:

  1. Log into a different Epic account in UEFN (this fixed it)

  2. Logged back into my main account, Went to Epic Account Settings → Password & Security → clicked “Sign Out Everywhere.”,

Sessions now launch every time

1 Like

just tried it sadly did not work for me all tho the account i switched to did not have the infinite loading screen issue we are having, weird :sneezing_face:

I tried that way, but the problem still wasn’t fixed.
The same issue occurred with another account, and my motivation has really dropped a lot… :nauseated_face:

Earlier, there was an update for UEFN and Fortnite, but the situation remains completely unchanged.
It has now been six full days since the issue started.

Can confirm that this hasn’t been fixed after today’s update.

Normally when I launch a session, my lobby music from the game plays while the session loads. But ever since this bug it also just doesn’t play anymore. Just something else I found strange.

1 Like

I hope this resolves the issue.

1 Like

Mine works 100% of the time now (I’m in OCE servers).

I suspect it had something to do with the FortniteStatus twitter account investigation, or the update.

See my report for more info: Cannot connect to UEFN session since 36.10 update. - #8 by hoskijdev

1 Like

this is my second run on uefn today and it seems to be fixed but there is still the issue of the start game button disappearing in game randomly and the devices randomly going back to the channels system [visual bug]

looks like it got fixed

(post deleted by author)

Ok it seems to be fixed now, indeed