over 3 years ago - Ubi-Milky - Direct link
No problem LordOfChickenz, we want to see a fix for this issue or at least discover what is causing it as much as our Siege players do and these reports from players should help as always, so thank you for contributing!
over 3 years ago - Ubi-Milky - Direct link
Hello everyone sorry for the delay getting back to you, I have not worked the Siege forums for a little while.

Thank you very much for the player reports, please when you can remember to stick to the bullet point format as it makes it easier to report.
Please also make sure to give us the exact time when this last affected you and your time zone please as this bit of information is very useful to our QA testers.

FamilaMontemor, cemilxelilov, Gronus2005PL, Sixx_String

I have added your info to the report, thanks again.
over 3 years ago - Ubi-Milky - Direct link
Hey Crazy_Juergsi and JayGeL44,

Thanks for submitting your report too, the team are still investigating and thanked me for the reports th eother day so keep them coming. Thank JayGeL44 for the extra detail shared at the end, this may be helpful to us the more information we can gather when it happens.
over 3 years ago - Ubi-Milky - Direct link
Originally Posted by Crazy_Juergsi
Why are there no updated to the progress??????????
Hey Crazy_Juergsi, I last spoke to the QA team about this 5 days ago, they thanked us for the recent reports, but no updates as of yet, apologies.

MrVoid3233
, I've added your report to the investigation, thanks for the help.
over 3 years ago - Ubi-Milky - Direct link
Hey LordOfChickenz, thanks for letting us know.

Can you remember anything in particular happening, did you uninstall any files or change any settings on your computer / console / router?

Or did the error just stop appearing naturally?
over 3 years ago - Ubi-Milky - Direct link
Thank you for the reports everyone, I have added all of the recent messages we have received on this thread that answers the QA teams questions, to our 4-0 error investigation to help find the cause as it is currently unknown what causes this. Any updates when we have some to share will be posted in this channel.

Special thanks to Mytre. Mitachax and Usir. for the reports as having the exact date and time is crucial to the team investigating.
over 3 years ago - Ubi-Raziel - Direct link
Thank you all for continuing to provide information about your experience. I will forward everything to our dev team!
over 3 years ago - Ubi-Milky - Direct link
Thank you to everyone who has submitted reports over the last 3 weeks, we really appreciate it - I have passed this onto the QA team to compile.

Also, special mention to White_Wolf_3141 thank you for letting us know your mobile data connection ran the game without issue, I will make sure to pass your post onto our QA team as well, thank you.
over 3 years ago - Ubi-Raziel - Direct link
Originally Posted by Limeade_
-Platform Name: Limeade_

- What 4-0 error code do you receive specifically? [4-0xFFF0BE20]

- What platform you are playing on? PC

- What is the last exact date and time when this affected you? At the start of a new season and got to the point where i bourght a completely new copy of siege and still is happening now. date is now (17/01/21)

- What region do you live in? uk

- Who is your internet service provider? TalkTalk

- Are you using wired ethernet or WIFI? Wifi

- What exactly were you doing in the game when this message popped up? i was just trying to get into an online game of siege quickplay

- Does this error appear 100% of the time, or only sometimes? it happens 100% of the time whenever i try go into any game mode
Thank you, and I'm sorry to read you're also affected by this.

I have forwarded everything to our Siege team to add to the data that we have.

All the best!
about 3 years ago - Ubi-Raziel - Direct link
Hello everyone!

Originally Posted by MARKSMANdawd
you have been saying this since 2017. How can you can you not solve a problem from 2017 if your are really working on it?
The error itself may have shown itself in 2017, however this specific issue has been occurring since 2020. At first it seemed to be resolved however we continued to receive reports, so we're gathering as much information as we can and sending it to our devs to help with their investigation.


Originally Posted by Maid.Noelle
nearly 3 weeks since the last update from a UBI staff member. Is this even being looked into?
Yes it absolutely is. We have not yet received more information regarding a fix yet, however we will let players know when we do. Support agents will continue to check back here, so we can forward the information given to us by players.

Originally Posted by LilPeanut00
- Ubisoft username. LilPeanut00
- What 4-0 error code do you receive specifically? 4-0xFFF0BDC0
- What platform you are playing on? PC
- What is the last exact date and time when this affected you? Everyday
- What region do you live in? Southeast Asia
- Who is your internet service provider? PLDT
- Are you using wired ethernet or WIFI? Ethernet
- What exactly were you doing in the game when this message popped up? In-game or at the start of the game.
- Does this error appear 100% of the time, or only sometimes? 100% happen all the time
Originally Posted by FamilaMontemor
- What 4-0 error code do you receive specifically? 4-0xFFF0BE29
- What platform you are playing on? PC
- What is the last exact date and time when this affected you? Today
- What region do you live in? Portugal
- Who is your internet service provider? MEO
- Are you using wired ethernet or WIFI? Wired
- What exactly were you doing in the game when this message popped up? Matchmaking
- Does this error appear 100% of the time, or only sometimes? Sometimes
Originally Posted by DavidCastlehof
Ubisoft username DavidCastlehof
- What 4-0 error code do you receive specifically? 4-0xFFF0BE2A
- What platform you are playing on? PC
- What is the last exact date and time when this affected you? 02/02/21
- What region do you live in? EU
- Who is your internet service provider? Virgin
- Are you using wired ethernet or WIFI? Ethernet
- What exactly were you doing in the game when this message popped up? Solo Queueing, doesnt work for ranked, unranked or casual.
Thank you all! I'll make sure this is added to the investigation.
about 3 years ago - Ubi-Milky - Direct link
Thank you to everyone who has contributed to this thread in the past 4 weeks, I have forwarded all of your reports to our QA team to investigate, we may be back in touch if our QA team need further information from certain players.

When it comes to investigating this issue, often the most recent date and time this has occurred is very valuable to us. I have been able to add 9 of your reports to our investigation for the players who were able to answer all questions in the past month.

Thank you again for all the information you keep providing us with and I am sorry we have no other updates at this moment in time as we continue to pass this information on to the team, with your help.
about 3 years ago - Ubi-Milky - Direct link
Thank you for continuing to add your report to this thread in the last week everyone, I have now added 10 recent reports from you to our investigation.

I am sorry we have no updates to share on our investigation yet, but thank you for contributing to our investigation of what is causing these 4-0 error codes and disconnects.
about 3 years ago - Ubi-Milky - Direct link
Thank you to everyone who has continued to give us your reports for what happened and when you encountered this error code and disconnect.

Thank you to AS3N233 for posting your workaround to change IP address, when accessing the game on console.

We have had an update from our Siege QA team and they have now implemented a fix for this issue in the background. This means the error code may still appear in the future, but this should not happen very often anymore for most players.

Should you receive any kind of 4-0 error code please continue to follow our connectivity troubleshooting per platform -

PS4 - https://ubi.li/12soI
PS5 - https://ubi.li/JE6K7
Xbox One - https://ubi.li/6L9Js
XBSX/S - https://ubi.li/55G8e
PC - https://ubi.li/YPwnl

We will continue to monitor these forums for any influx of new reports, in the Player Support section, thank you.
almost 3 years ago - Ubi-Milky - Direct link
Thank you to nanof, Playerfjudofig, DrSupply and ChefZimba for your player reports of the same error code you have all experienced in the past week, 4-0xFFF0BE25

I have passed your information onto our QA team, to track the frequency of this error code disconnection/crash in case this begins to affect more players, thank you for being the first players to report this after the recent update
almost 3 years ago - Ubi-Milky - Direct link
Thank you to everyone who has contributed to this thread with reports over the past few weeks.

As we have had more reports of this recently since the start of S1 and S2 Year 6, we have opened a separate investigation to track how often players are being disconnected with these particular error codes this season.

Please stay tuned for any further information we may need to ask you and please make sure to perform the following troubleshooting and port forwarding steps, to help prevent these particular disconnections -

PC - https://ubi.li/YPwnl
PS4 - https://ubi.li/12soI
PS5 - https://ubi.li/JE6K7
Xbox One - https://ubi.li/6L9Js
XBSX/S - https://ubi.li/55G8e
almost 3 years ago - Ubi-Milky - Direct link
Thank you for the last 2 weeks of reports everyone.

It seems as though after the updates made by the Siege team in the background, the other 4-0 error codes that players were affected by in this thread have quietened down.

Most players effected now after the introduction of Y6, seem to mainly see the 4-0xFFF0BE25 error code now only for the majority of players, thank you for your reports and answering the questions needed, we will continue to pass this onto our Siege QA team to investigate and reproduce.
almost 3 years ago - Ubi-Thrupney - Direct link
Hi Tedha_Ant and M00tarde, thanks very much for these two reports - I have passed them on.

We are continuing to investigate this, and we unfortunately have nothing to report quite yet, but we're looking to get it resolved as soon as possible. Sorry for the inconvenience in the meantime.
over 2 years ago - Ubi-Karl - Direct link
Hey everyone!

When sending requested details, it would be great if you could also let us know if you had a chance to go through troubleshooting steps that were suggested. Once we know it has been done, let us know and we will pass details over accordingly.

Originally Posted by squishward77
I discovered a two or three ago that when the game crashes, if I relaunch siege normally I will get the 4-0 error code, but I will not if I launch it in Vulkan instead. It also seems that the game crashes less while using Vulkan. Im not sure if this is just coincidence but I have not gotten the error code since then.
Hey squishward77, thanks for sharing this with everyone and I do hope others will find this useful!

Should you have any other suggestions or if you ever require any assistance, feel free to reach out at any time!
over 2 years ago - Ubi-Karl - Direct link
Originally Posted by Moorsie.
Ubisoft nickname:
Moorsie.
- What 4-0 error code do you receive specifically?
4-0xfff0be20
- What platform you are playing on?
PC
- What is the last exact date and time when this affected you?
08/2/21
- What region do you live in?
West US
- Who is your internet service provider?
Comcast
- Are you using wired ethernet or WIFI?
WIFI
- What exactly were you doing in the game when this message popped up?
I que for any game mode, I wait for as long as 5 minutes and then I'm hit with error 4-0, then 3-0, and then 0-0.
- Does this error appear 100% of the time, or only sometimes?
This has appeared every time I have tried to que for over 4 days now.
Hey Moorsie., welcome to forums and sorry to hear that you've been dealing with this issue for a few days now.

Just to double-check, did you have a chance to go through steps outlined in the following article yet? It will help you to establish the best possible connection to game servers as well as remove any limitations preventing you from doing so, therefore give it a go and keep us updated!
over 2 years ago - Ubi-Orion - Direct link
Originally Posted by KnowingNothing
Ubisoft nickname:
KnowingNothing
- What 4-0 error code do you receive specifically?
4-0xfff0be20
- What platform you are playing on?
PC
- What is the last exact date and time when this affected you?
3rd August 2021
- What region do you live in?
Sweden
- Who is your internet service provider?
Security Firewall Ltd
- Are you using wired ethernet or WIFI?
WIFI
- What exactly were you doing in the game when this message popped up?
I que for any game mode, after a minute the Error message pops up.
- Does this error appear 100% of the time, or only sometimes?
This has appeared every time I have tried to que for the past week, 100% of the time. Only training ground works.

Last week it worked fine. Nothing since the last time it worked have changed, no game updates, no software updates or internet problems.
No new updates seems to help this either.
I have tried all the possible solutions: Reinstall, forward ports, verify files, check Modem and Router, reset Hosts file, flush DNS.
I hope this error code gets solved. I dont hate siege or Ubisoft, but if this continues, i just might have to throw Ubi and siege in the bin.
Hey there.

I'm sorry to hear you're continuing to experience issues with connectivity.

As a result as you've exhausted all standard troubleshooting we'd like to investigate further to try and resolve this for you. Can you open a support case with us and once the case is open submit images of your forwarded ports

Originally Posted by Moorsie.
I tried everything on the troubleshooting page and nothing worked so after trying everything I could, I found that disabling and fully quitting out of my vpn solved my problem. I then went into the uninstaller and clicked on the repair button and once the files were verified and repaired, I reopened the VPN and everything worked perfectly. Have not had any issues thus far.
Thanks for keeping us updated on this and really glad to hear you've managed to resolve this!