{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Editado por Base:
9/22/2019 5:20:38 AM
2
Buffalo Error Code
I have been trying to get on D2 on pc for over a day now and have been getting nothing but Error Code: Buffalo. This happened after i uninstalled and reinstalled the game and i have tried everything from deleting the file that people suggest after doing %appdata% tto setting up a VPN which was also suggested and have had absolutely no luck. I even tried reinstalling the game for a second time to see if that fixed the problem. The current page for the error code in support is useless for me by the way as all it suggests for PC is that I am logged in from two PC's and ive tried changing my password on blizzard but nothing changed. Hopefully someone that has had this problem before will read this or Bungie will actually respond.
-
Hi. Thanks for your report. The [url=https://www.bungie.net/en/Help/Article/11912]BUFFALO[/url] error occurs when there is a connection issue with Battle.net's servers. You may want to review our [url=https://www.bungie.net/en/Help/Article/11912]BUFFALO[/url] 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. [b]7.[/b] Users have reported that using a VPN may cause this error[/quote]
