{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Josev_Spaceface:
4/29/2020 11:19:30 PM
24
Consistent Error Code Weasel
Once every 2 hours or so, I encounter "contacting destiny servers" for a bit, then get kicked from the game with error code "[b]weasel[/b]". This only started occurring a couple weeks after Forsaken launched, but it's been consistent ever since. Interesting, it tends to happen towards the start, or end of events, like right before getting rewards after a Crucible match, right after a round ends or starts in Gambit.
-I am hardwired to LAN, have a very consistent 250+mbps down / 10+mbps up connection.
-I have tried all the port forwarding instructions, REPLACED my modem and router with new models.
-I have upgraded my internet service to a better connection speed.
Nothing changes the consistency of this error code.
I ran a ping test, too:
--- bungie.net ping statistics ---
300 packets transmitted, 300 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 6.019/9.873/20.094/1.409 ms
Looks pretty good to me, but nothing works to resolve this, so I'm reporting it to the forum.
Any ideas on how I might fix this?
English
#Help
-
Updating again... After a couple months of no problems at all, the consistent error code Weasel issue every 2 hours has returned, perfectly in sync with the April 21st update. Even after the update today it still persists. A new development too, now after the weasel error occurs, the game crashes! I've reported it maybe 6 times through PSN. I've done everything suggested on network troubleshooting, nothing is working. Here's hoping it goes away again soon, but man in the meanwhile it really really really sucks getting kicked out of high level activities. As always, open to any ideas, albeit getting sick of being recommended the same 6-10 of them over and over again. At this point I've replaced literally every element of my setup and service since these first started happening, so I hope Bungie might take a closer look at what's causing it.
