Hi everyone, Epic have put in a potential fix, from our testing we have been able to join 10 random lobbies.
Could you please try and see if you are able to to join a lobby.
If you are still having issues we will let Epic know and they will have to investigate further.
We can't give a time frame as this is with the Epic Online Services, we're sorry for inconvenience but as soon as they have let us know when its been fixed we will respond on here.
The Epic status is currently affecting the P2P Networking, which all our online games run on.
Hello, thank you for the very detailed information.
We're currently seeing from the Epic Online Services that the development portal is down, we believe this could be the reason users are currently having issues.
We are in contact with Epic Games to see what is going on. We apologise for the inconvenience.
You can see the status here - https://status.epicgames.com/
Hi, this isn't regional, the country you live in doesn't matter, we're don't know at this time when this issue with Epic will be fixed, we apologise for this inconvenience.
Hi, what we're looking for is your save which can be located:
C:\Users\[Your Windows Username]\Documents\Sports Interactive\Football Manager 2023\games
Once you find your save you can upload it here - https://oc.sigames.com/owncloud/index.php/s/Kzvhd0MdU3v4Nv4
Hello, have both users got an FMFC account? If a user isn't signed into FMFC even though the host is, they wont see the lobbies. So can you make sure both of you have signed up and signed in.
Hello, thank you for flagging. We will investigate this further.
Can you please attach your editor file.
This can be found - C:\Users\[Your Windows Username]\Documents\Sports Interactive\Football Manager 2023\Editor Data
Hi, we're currently seeing from the Epic Online Services that the development portal is down, which could be the reason users are having issues.
We are in contact with Epic Games to see what is going on.
You can see the status here - https://status.epicgames.com/
Hi, we've tested your save and this appears to be fixed.
If possible, do you have a save from before this issue starts to happen? This will help us run further tests.