{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Hibimiku-9000:
7/29/2019 5:43:10 PM
1
Repeated Buffalo errors
I've been experiencing repeated Buffalo errors for quite a while now.
It started around the same time Joker's Wild came out, and it prevented me from playing Destiny 2 for the first month or so of Season of the Drifter. After that, it vanished for the rest of the season, only for it to come back with a vengeance at the beginning of this season (Season of Opulence), and has made logging in consistently almost impossible for me, preventing me from logging in for entire days, kicking me out of games for no apparent reason, and then stopping me from logging back in, leaving my teammates to believe that I abandoned them.
I have found and used every possible avenue of repair I could find, from resetting my password, to even uninstalling and reinstalling both Destiny 2 AND the Battle.net application multiple times in a row, with no success what so ever. Please, if there's something that you can do to fix this, let me know!
-
Hi Dracus, Thanks for your report. We are investigating ongoing connection issues resulting in error codes/ The BUFFALO error occurs when there is a connection issue with Battle.net's servers. You may want to review our BUFFALO help article for more information about this issue. If that doesn't help: [quote][b]1.[/b] You may also want to try opening the battle.net launcher "Settings" and change the "When I open a game" option to "close the battle.net launcher completely" option. [b]2.[/b] Some players have suggested disabling Internet Protocol Version 6 (TCP/IPv6) on the PC might help with this issue. [b]3.[/b] You may want to change your region/server to another location. [b]4.[/b] Some players have suggested disabling the "Always require authenticator for login" option in your Blizzard account settings. [b]5.[/b] Some players have reported that disabling IPV6 has helped them with this issue. [b]6.[/b] Some players have reported that logging into their Battle.net account and Destiny 2 on another PC then logging out and logging into them on their first PC have resolved this issue. [/quote]
