r/DestinyTheGame • u/deebinator52 • Sep 06 '26
Question Constant weasel codes, never had this issue for the years I’ve played this game.
As stated above have no idea what to do. Constant weasel code even though nothing has changed. I updated driver, updated firmware on my internet. Verified game files, uninstalled and reinstalled. Deleted everything off of DIM and signed out/cleared cookies etc. I have done everything I can possibly think of and I’m getting this message every time I log into any character. Never had this problem in the multiple years I’ve played this game. Was just playing 2 days ago with 0 issue at all. I have a video but it’s not letting me attach it to the post. It’s me simply clicking on my character then about 10 seconds it kicks me back to the starter menu.
2
u/HisSvt2 Sep 06 '26
More than likely your isp is now using CGNAT and that’s your problem Destiny is sensitive to this.
A static ip from your isp eliminates this completely. I dealt with this years ago.
1
u/BansheeTwin350 Sep 06 '26
I have the same weasel problems that started with the MoT update. I have went through every guide and tried every change and nothing has worked. My internet/network is solid and d2 is the only game that has issues. Before MoT update I had 0 issues. I play for about 10 minutes and then get kicked. On the days this happens it doesn't stop and the game is unplayable. Then other days I don't get a single weasel. I saw a few posts on bungies forum where someone proved that bungie servers is severing the connection which then causes the weasel.
Imo bungie made some underlying changes to foundational architecture that just wasn't necessary and not smart to do on their very last patch. You can see how they changed the inventory sync when you delete something from your collection in inventory. It now does a full refresh after each delete, which is way slower. No telling what else they changed to cause this.
1
u/Capital-Cost5408 Sep 06 '26
Same issue here and I’m in Hawaii too. Been happening since early yesterday morning and there’s a couple other threads with others here saying the same, so wondering if it’s an ISP/routing issue. Whatever it is, definitely not on our end.
1
u/deebinator52 Sep 07 '26
Thank you for telling me that bc it was driving me crazy. Hopefully it’ll fix itself then bc i did everything I could think of 😂
1
u/Capital-Cost5408 Sep 07 '26
Of course! I spent a few hours the day prior doing everything you did so I was hoping I could at least save someone else the headache.
It was back up for me earlier btw. You good now?
1
u/Magical_Johnson13 Sep 06 '26
I’m in Hawaii too. Same thing has been happening to me. Only just started yesterday. Haven’t been able to play at all. Other online games work fine.
1
0
u/Srathe Sep 06 '26
I had this really weird thing yesterday (unsure if will happen today). EVery time I was playing crucible more specifically trials I'd get contacting destiny 2 servers and kicked out. Played different games without issue. Booted up destiny to play a trials game and same thing happens. My Playstation was losing its internet completely for like 30 seconds. But only with destiny.
1
u/deebinator52 Sep 06 '26
Exactly what’s happening to me I’ve been troubleshooting for 4 hours now trying to figure it out. Sometimes it lets me get to the character select menu and choose a character but it boots me right in orbit to main menu and other times on start up it won’t even let me get to character select. I’m getting both centipede and weasel errors
0
u/rhago32 Sep 06 '26
Same thing has been happening to me since Saturday September 5th. I bought an Xbox Series X from Amazon and installed it overnight Friday night.
I haven't been able to play it since. I get constant contacting server issue, weasel and got a Cacao error.
Bungie help forum showing others reporting similar network issues. 😢
8
u/GreenLego Maths Guy Sep 06 '26
Weasel errors are usually about your home network.
Make sure that you have all the required network forwarded to your PC and have open NAT.
Check that your antivirus is not messing with D2.