Original Post — Direct link

I've been trying to fix it for a while now, I've looked at somewhat all issues it could be. Now I'm banned because of this problem because I can't reconnect.

about 2 years ago - Ubi-Mercury - Direct link

Hey there @god-peak-ezekil, I'm sorry to hear you received this error code when trying to reconnect to your match. Would you please confirm if you have received this specific error code more than this one instance, and if you have seen other error codes appear as well?

about 2 years ago - Ubi-Milky - Direct link

Hello @kasuu2005 thank you for providing this screenshot.

We know some players have been affected by disconnection and certain 4-0 error codes recently, we are monitoring the frequency of each code that appears, and what platforms are affected.

Could you please get back to us and let us know what platform you play on, so we can pass this information on to the Siege team?

In the meantime, please follow all of the steps in our guide for whichever platform you experience this error code on, as these guides contain the most common fixes for connection issues and can help rule out certain things that may cause disconnections >

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
STADIA - https://support.google.com/stadia/answer/9595943?hl=en-GB#zippy=



about 2 years ago - ubi-smash - Direct link

@bigboyappetite I am very sorry this issue persists after exhausting all steps previously share by my colleague. To help share some further information with our team to further investigate this, anyone that is still having the same error  4-0xFFF0BE20 appear for them, could you please answer the following:

  • Do you receive any other codes besides 4-0xFFF0BE20?
  • What is the last exact date / time you were blocked by this code?
  • What region do you live in?
  • Who is your current ISP?
  • Are you playing via Wi-Fi or Ethernet?
  • Does this error appear 100% of the time or sometimes? 


about 2 years ago - Ubi-Karl - Direct link

Hey @BigBoyAppetite, thanks for your input there and sorry to hear you have been affected by this too.

I've had a closer look at our server status during the time of your contact and can see that we have experienced a temporary degradation, however servers are all working as intended now, therefore if you'll have a chance, see if issue persists and we will take it from there.

Keep us updated!

about 2 years ago - Ubi-Nacho - Direct link

@knockaroundguy7 Hi there.

Sorry to hear you're seeing this connectivity error code. Could you confirm for us if you've been able to follow any of the connectivity troubleshooting steps provided by Ubi-Milky?

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
STADIA - https://support.google.com/stadia/answer/9595943?hl=en-GB#zippy=


If you require further assistance with this error code after following these steps, please be in touch, and we'd be happy to help.

almost 2 years ago - Ubi-LadyBlue - Direct link

@bigboyappetite I'm sorry you're still running into the error. I've gone ahead and passed the information you provided over to our teams to better help them check into what's happening. I know this is a super frustrating experience so thank you for being so understanding.

almost 2 years ago - Ubi-Oxavo - Direct link

Hello @DeadRec0rt ,

Thank you for reaching out and sorry to hear you're receiving the error 4-0xFFF0BE2B.

Please let us know which steps you have already taken to remedy this issue? Have you tried to perform all the steps suggested by my colleague @Ubi-Milky? . The more information you can give regarding your experience, the better equipped I am to assist you.

We look forward to hear back from you and provide a further guidance.

almost 2 years ago - Ubi-Ciel - Direct link

Hey there @Dazthetaz69-0 and welcome to the Ubisoft Discussions!

I understand you have been able to connect to the online services of R6S due to an error code. To attempt to fix the situation, I'd recommend changing the "UseProxyAutoDiscovery" value from 0 to 1 in GameSettings.ini file, as this seems to have worked for other players!






Recent Rainbow Six Siege Posts

about 18 hours ago - Ubi_Zurik