{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Изменено (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.
-
Same thing happened to me, but I get centipede, coconut, lettuce and sometimes destiny 2 servers are down. Did everything I could on my side but no help. Couldn't find anything beyond generic answers everywhere.
-
those of us in south east asia been having weasel or baboon then weasel for over 2 weeks randomly since iron banner closing to end. Could it be asian servers are overloading? free to play attracts alot of casual freebies cafe players after all. my worse experience we had was doing gardens of salvation raid on the last boss encounter, we randomly get disconnected and weasel. Took us 3 hours of retry finally beat the boss and on the way to the chest 4 of us got weasel before the chest open, it denied our completion and out loot. Only 2 of of members left inside and we cant even join in cause the instant location is locked. Almost a week no changes, we still live with random weasel, so one of us decide to connect to a friend in US , let him be the host for the raid, and behold zero weasel, we tried again on local asian players still get weasel, this time baboon first then weasel.
-
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.
-
1 ответИзменено (Lord Magris): 10/23/2019 2:32:55 AMCurious. Are you referring to an update to Steam or an update to the PC version of Destiny 2 itself? I know you mentioned Steam went down for maintenance. Destiny 2's Xbox servers didn't have any update recently since the beginning of Iron Banner. I haven't seen Weasel or Centipede in a long time, but Currant has appeared here and there for me along with other errors for about a month. For the most part, the errors you mentioned aren't really giving me a lot of trouble, but I do know that some of them have started happening to players a lot since Cross-Save was implemented.
-
1 ответThe moment i grabbed the quest i started receiving errors... centipede, current, weasel, cabbage, lettuce, whatever. Can't pass the login screen - sometimes it let me select a character but this is as far as i can go. And in my case i didn't have problems at all in the past besides random errors in the rush hour. Why not make clear what is wrong like "the game is current not available in your area" instead of random names with no meaning (all attached to generic internet problems with no real solutions - all the help page can offer is "wait" or "use a cable").
-
I'm able to login now... but things got worse. I literally re-downloaded the whole game (while playing WF listening to a podcast because i don't have any internet as Bungie says) to find out that was not the problem; followed every step in every tutorial, nothing (double the work to undo all the "fixes"). Today it "fix" itself... Now the errors are internal ones (disconnecting and reconnecting me all the time) and never the same one (way to many names to remember all, but beaver and weasel are common ones for everybody). And i'm still having the "servers not available" at start - i need to click three or four times to log in... is unbelievable the amount of error you can receive in 6h playing D2... i'm somehow impressed.
-
3 отв.Hi there, Thanks for reaching out. As we continue to investigate players receiving WEASEL errors please refer to our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]network guide[/url], [url=https://www.bungie.net/en/Support/Troubleshoot?oid=13603]optimization guide[/url], and [url=https://www.bungie.net/en/Support/Troubleshoot?oid=13610]advanced troubleshooting[/url] for assistance on minimizing connection issues and best optimizing your connection to Destiny 2.
-
Hello, I am having the same problem, the only difference is that the error Weasel, does not seem to me, I tried to connect with the docked phone and once it worked, the second time did not, just tried the mobile internet of that phone and it worked too but trying a second time is giving error, is there more people, someone has any good tips, already tried everything, leave the NAT open modem, UPnP, and so on and nothing, everything works, several others Steam games also minus Destiny 2, and the funny thing is that yesterday was working well, anyone have any ideas?
