JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by FoxyMari: 10/23/2019 5:01:21 AM
8

Help i can't play the game Error Codes: Weasel, Centipede and Currant

Hello, ever since the update on 10/22 I haven't been able to connect to Destiny 2. Before this update I did have minor problems with lag, however I was still able to play and connect to the game. Now, however I keep getting error codes Weasel, centipede and Currant when trying to go to any planet, and already taken many measures to see if it's my own connection. I restarted my modem, tested my connection, activated a VPN to further test connection issues i used a service like ExitLag, connected to other games and websites to check my internet stability, and accessed Speedtest.net to run a test on my connection, along with making sure the game is not blocked by my Firewall, and everything on my end seems to be working with working ping. When Steam went down for Maintence, I was able to access the game and connect to things like Planets and the tower, but once Maintence was over the error codes Centipede and Currant returned and I am unable to connect. I am not sure if it has any correlation but i am sharing that none the less. update : to clarify I typed the first part wrong, when I wrote Update, I meant the weekly reset and the unlock of Leviathan's Breath. Every tuesday as well, Steam puts their servers down for about an hour maintence as well and that is when I was able to access the planets and Tower. The errors themselves only showed up once the Weekly reset happened, last night and this morning I was playing fine.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • I am having the same issues sense the Tuesday reset, was kicked 3 times Weasel error right before our full premade fireteam started Gambit Prime. Also multiple disconnected from Destiny 2 server errors, but those would resolve themselves. The weasel error kicked me out of Gambit 3-4 times leaving our team 1 short, or not letting me start it at all without getting kicked to the main page. Internet was tested as Voice, Battlnet and, other games played just fine online without issue. Is there any specific port that needs to be open? Is Teredo Tunnel needed? I will test DMZ on a static IP to see if that fixes it. Also this is the most issues I have had with Destiny 2 sense the switch to Steam, Battlenet rarely kicked me out.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon