[2023] Error code 4-0xFFF0BE20

Hey @Loketheboiii! Sorry to hear you've encountered this issue.

You should be able to circumvent this error by changing the "UseProxyAutoDiscovery" value from 0 to 1 in the GameSettings.ini file.

You should be able to find this file under the following path:

C:\Users\%username%\Documents\My Games\Rainbow Six - Siege\\GameSettings.ini​​

Please note that instead of User ID, you will find a string of numbers and letters in the Rainbow Six Siege folder. This is working as intended, as the ID is different for every user. Once you've changed the setting, be sure to save the file.

Please reach out, should the issue persist.

@Loketheboiii Sorry about the mix up! Since you're on console, please take the time to complete the troubleshooting steps in this FAQ article including port forwarding.

Once those have been successfully done if this 4-0xFFF0BE20 error code still occurs, please submit a new support case for this issue with a screenshot showing your forwarded ports and one of our agents will be able to follow up with you directly.

Hey @Garde-_, thank you for posting.

The provided path above is the default path for the game's file.
Maybe you have guided the game to create the GameSettings.ini file to be somewhere else.

Also, have you correctly performed the steps of this troubleshooting article?

Thanks!

Strange. Which file did you find it in?

Hey @Garde-_

If you're having problems with other Ubisoft games too it could be Ubisoft Connect that is causing the connectivity error, as that will need to be open regardless if you launch the game from Steam or straight from there. Can you try adding it to any whitelist or exception list if you have an antivirus?

Also, check the other suggestions on Ubisoft Connect troubleshooting here.

@Garde-_ I am sorry to hear that you are still encountering this error message. To help us look into this further, please submit a support ticket for further assistance.

Hey there @WH1SP3R0420,

I'm sorry to hear that you're still encountering this issue.
Usually the issue can be related to an issue with firewall rules, or not running as admin.
The latest patch update, should have given you a popup, to confirm firewall rules again.
Let us know if the issue persists, after the latest patch via a support ticket.