{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by eolene:
6/9/2022 4:02:53 PM
15
Attention: Contacting Destiny 2 Servers - ERROR: weasel - Full Report
This post is to help Bungie diagnosis and solve this issue, not to complain. My real frustrations will be very evident. This is a report on everything that has been attempted to eliminate this recurring issue. I will try to be as descriptive and succinct as possible. Thank you.
Platform: PS5
All other PlayStation Network required games play fine.
PS5 Network - Test Connection: Passed in all hardware testing scenarios listed below.
Location: US, Pennsylvania
Last played prior to errors: May 18, 2022
Started receiving errors: May 27, 2022
Error: weasel
Playtime: Less then 1 hour before receiving the error, recurring.
Errors have been consist every time played since May 27th.
Where it has happened:
- Orbit
- Gambit
- Strikes
- Crucible
- Story Missions
- Tower
- HELM
- Enclave
- Castellum
- All Menus
I’ve only played/visited those areas above since May 27th.
Playing styles:
- Solo
- Cooperative
- Matchmaking
ISP: Comcast since 2013
Download: 1Gbps+
Upload: 50Mbps+
No Firewall
All of the software procedures listed below were tested and did not resolve the issue, every avenue tested still failed with the weasel error.
Deleted the entire game and reinstalled from the PS Store, PS5 version only. I do not use an external drive.
Cleared console cache via Bungie's criteria.
Restored Licenses on PS5.
VPN and DNS tested with:
- Express VPN (paid)
VPN tested with:
- SaferVPN (paid)
DNSs tested with:
- Google (free)
- CloudFlare (free)
- Strong DNS (paid)
All of the hardware procedures listed below were tested and did not resolve the issue, every avenue tested still failed with the weasel error.
- Rebooted Netgear router
- Hardwired from Netgear router
- Hardwired from Netgear modem
- Secured WiFi via 2.4GHz and 5GHz
- Another Router, TP-Link, hardwired and secured WiFi
- Tethered to my iPhone T-Mobile hotspot using cellular data
- Neighbor’s secure WiFi, ASUS router
- xfinity unsecured WiFi
Advanced Troubleshooting: UPnP & Port Forwarding findings
- Port Forwarding of Bungie’s required ports
- Port Triggering
- UPnP enabled & disabled
All above variations still resulted in the weasel error
Hopefully, in being helpful, this information will reach the eyes of Bungie and it will help in finally rectifying this game-crippling recurring error. This error has made my favorite game, literally, unplayable. If anyone has any other suggestions, please share. Thank you.
-
Tried all that you have done, and still cannot load the game getting error code right into the loading screen, nothing works.
-
Same exact thing has been plaguing me since about mid June. Anyone know if bungie knows about this/has acknowledged it?
-
Having more issues when their servers are loaded versus when they are not. Ran some tests during the day & during the night. Weasel errors are almost 10x worse at night. From 6pm to Midnight EST.
-
I think Bungie just removed my other post ([url]https://www.bungie.net/en/Forums/Post/261275288[/url]) which was referencing this post. I hope this means they're aware of the issue & are working on a fix. [url]https://imgur.com/a/4fauYqC[/url]
-
5 RepliesAfter the update, every two hours on the dot, I get error code weasel. This was an issue from back in Forsaken that was plaguing a lot of folks, would periodically rear its ugly throughout the following couple years. It's been great for me this past year or more, but now it's back just as it was. Something is definitely broken, smells like a reversion bug.
-
1 ReplyI am having the same issue, but on PC. Keep getting Weasel. I was not having this issue before the update Tuesday. But since Tuesday's update its been non-stop Weasel and the occasional Baboon followed swiftly by a Weasel. I posted something about this as well and got a response back to do the troubleshooting steps...... which I already did.
-
Edited by eolene: 6/15/2022 12:36:18 AMHow is everyone doing after the maintenance & Hotfix/Update? It didn't fix anything for me. Still getting weasel error all the time. Bungie please fix this.
-
3 RepliesI’m having the same issue. It’s passing me off cause I just got back into playing a few days ago and this is my only free week off. Tried all of that too and nothings changed except I can finally make it past the title screen 🤡
-
Having the same problem I can't play more then 3 mins and it kicks me I never had a problem before til now weasel pops up in a window error but at the bottom I see a baboon error code for a second also
-
Hey guys bungie just posted on Twitter that destiny 1 is going to be fixed.
-
1 ReplySame problem on PS4
-
2 RepliesHave you tried deleting the game and downloading it from a disc? I saw somewhere that that might help because that way the full game isn’t on the internet it said it would help with connection. I’m gonna try it and let you know if it works or not.
-
1 ReplyAll the money we dump into this game with the constant error codes and getting kicked from anywhere in the game is getting OLD! Its obviously not on the players end either...when is this going to be fixed!!!???
-
1 ReplyI can’t even get Destiny 1 to play. What gives Bungie????
-
12 RepliesI’m dealing with the exact same thing and did a majority of this as well with no luck. I hope they fix it cause it’s frustrating to be able to sign in, start a strike or NF and being going good then all of a sudden 5-10 in I get the red banner on the bottom of the screen. Thanks for putting all these details down to let them know what we are doing on our end to try and play.
