JavaScript is required to use Bungie.net

Ayuda

Ayúdanos a ayudarte.
6/15/2019 7:32:10 PM
2

Excessive Buffalo Errors.

Ever since the launch of Season of Opulence. I have gotten AT LEAST three buffalos a day. And it wasn't too bad to start, but we're nearly in week 3 of Opulence, and I've seen people complaining about this left and right, myself included. Does anyone have a fix for this or does anyone know if Bungie is working on fixing it, cause it's making the game practically unplayable.
English
#Help #Errorcodes

Publicando en idioma:

 

Pórtate bien. Echa un vistazo a nuestro Código de conducta antes de publicar tu mensaje. Cancelar Editar Crear escuadra Publicar

  • Same here. Every hour I play I get kicked. First Weasel, I clicked to rejoin then Buffalo, telling me I have to close the game and the Blizzard app completely. It been happening since a couple of weeks. I tried I few suggestions and nothing fix it.

    Publicando en idioma:

     

    Pórtate bien. Echa un vistazo a nuestro Código de conducta antes de publicar tu mensaje. Cancelar Editar Crear escuadra Publicar

    1 Respuesta
    • Hi there. 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]

      Publicando en idioma:

       

      Pórtate bien. Echa un vistazo a nuestro Código de conducta antes de publicar tu mensaje. Cancelar Editar Crear escuadra Publicar

    No se te permite acceder a este contenido.
    ;
    preload icon
    preload icon
    preload icon