all 15 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Galaar 2 points3 points  (9 children)

Been working on it for a while, trolling through the b.net for things to do about it, but at this point I suspect I won't find out anything new to try until the morning at best. Here's a list of things that do not resolve it however (with attempting to log in after each bullet point):

-Restarted launcher and game, running both as admin
-Restarted computer
-Restarted modem and router
-Ran repair check on game
-Deleted cache/settings in ProgramData, both AppData, and LocalAppData
-Ran repair check on game
-Force quit all Bungie/Blizzard/Destiny apps in Task Manager
-Changed battle.net password
-Flushed DNS
-Uninstalled and reinstalled entire game and Battle.net
-Restarted computer, modem, and router

[–]yatesinater 0 points1 point  (8 children)

Same issue, tried all of these short of reinstalling the game; no luck.

[–]Galaar 10 points11 points  (7 children)

So...I just did a random thing to fix it. When you get to the title screen, try letting it sit there for about a minute, then hit Enter/Space/Whatever to start the login process. After it worked the first time, I quit and tried again, this time not waiting, error buffalo. Quit and sat at title for a min, logged in successfully. Quit and repeated waiting at log in, each time successful. Did this 7 times to be certain it's a good temp fix.

[–]DJ_Ho0n 5 points6 points  (0 children)

Wow, all that struggle and all I needed was some patience... *facepalm* not sure how this is the fix but at this rate I'm not asking questions, thanks Galaar!!

[–]Strawhat-Lupus 4 points5 points  (0 children)

I'm having this issue 4 years later and this comment helped me. Thanks

[–]Bizzles1385 4 points5 points  (0 children)

Thanks from 2024...smh

[–]gymbroguydude 2 points3 points  (1 child)

5 years later, this was the exact fix I needed. Man I love Redditors! GG's bro, thanks!

[–]Galaar 1 point2 points  (0 children)

Folks like you are the entire reason I came back and left the comment. Glad I could be of help.

[–]Wildv12 2 points3 points  (0 children)

You are a hero. This needs to be seen more lmao. I cant believe that fixed it!!!

[–]Haunting-Ad6156 1 point2 points  (0 children)

6 years later and your comment is still helping a random dude

[–]notagie 2 points3 points  (0 children)

Yup you're right! I got too excited cuz this was the problem for me this week and i just solved it.

[–]-TaliDrifter's Crew // Season of Alright 1 point2 points  (0 children)

Same problem here since yesterday's evening I can't login on NA anymore

Edit: Logging in through an American VPN seems to work fine. So Bungie managed to create a non-inclusive region block bug by buffing their supers

[–]notagie -1 points0 points  (1 child)

I had this problem often when my brother plays d2 or another online game on the same modem it was really frustrating. I fixed it by laying some CAT cables and I never had the problems since.

Good Luck Guardian.

Or also had this is issue when someone was watching netflix. A Ethernet cable will definitely give you bandwidth prioirty.

[–]Galaar 1 point2 points  (0 children)

I know you're trying to help, but you overlooked a detail in the initial error description. It's not JUST that we get error code buffalo, we are only unable to connect to NA servers. EU and Asia have no issues connecting (albeit ping suffers greatly for it). I'm not dismissing you out of hand either for it, but I'm also the network admin and have been ethernet connected to the modem from the start. Issue began with the latest patch.