So I thought I was crazy until a few days ago, when one of my raiding team confirmed that he experiences exactly the same thing.
How widespread is this problem? What the -blam!- is even going on? The implications, from my layman's perspective, are equal parts perplexing and unsettling. Here's what's been going on for me since about the time 1.1.1 was released:
Pretty much once a day, every day, I get kicked off of the Destiny servers, and am given the so-called 'weasel error'. No big deal, everyone and their mother has gotten this at least once. But what happens immediately afterwards is much more unnerving:
1. The wireless internet connection to my XBOne is completely cut off. I'm disconnected from my home wifi network completely, despite the fact that my wifi signal continues to function perfectly on all other devices.
2. I attempt to reconnect to my wifi signal on my XBOne manually (my wifi network still appears in the list at this point, although the console no longer automatically connects to it, as it normally would). I am prompted to enter the password for my wifi network.
3. I enter the password for my wifi network. Password is rejected.
4. I re-enter the password for my wifi network, being extra careful to use the proper case and punctuation. Password is rejected.
5. Repeat step 4 again several times. Give up.
6. Perform a hard reset my XBOne (hold down power button for several seconds until the console powers off completely, then power up the system again after waiting several seconds).
7. XBOne loads up, automatically connects to my wifi network, everything is exactly the way it should be.
8. Skip to the next day. Repeat the previous 7 steps, ad infinitum.
Until I happened to mention this issue during a recent raid, I was pretty sure it was either something wrong with my XBox itself, or it was something having to do with XBox's most recent update, or a number of other things. Honestly, I was guessing.
But to hear that some other guy is having the exact same issue, makes me think that others are experiencing the same thing.
Seriously, what the actual -blam!-. Somebody smack me with some knowledge, please.
UPDATE: Wow there are a lot of you. Wasn't expecting it to be this widespread. Still seems like there's some debate over whether it's an XBox problem, or a Destiny problem (as in, did the Weasel error/Destiny cause the internet to stop working on the XB1, or did the internet stop working on the XB1, causing the Weasel error?)... to which I would say, why haven't I experienced this with any other XB1 online multiplayer games? Why do I get this exact string of issues (loss of XB1 internet connection, followed by it refusing to accept the CORRECT wifi password) consistently, and ONLY when I'm playing Destiny? I mean, it's possible it's the XB1, but it seems like an awful lot of coincidence.
Anyway, it sucks regardless. One thing that seems to work for people is foregoing wifi entirely, and 'hard-wiring' the XB1 with an Ethernet cable. If you've found another solution, please let us know!
Just For Fun: Here's a list of errors people have reported!
Baboon, Weasel, Elk, Centipede, Beaver, Cattle, Coconut, Oyster, Wasp, Beetle, Hare, Canary, Banjo, Chimpanzee, Cockatiel, Hawk, Marionberry, Vulture, Quail, Bass, Sheep, Nightingale, Drum, Caterpillar, Flatworm, Leopard... and it just goes on from there....
-
Same but I can usually just reconnect to it manually right after
-
It's more of a complicated issue a believe, I get the weasel error and I just get kicked from whatever Activity I was doing but I'm still signed into Xbox Live and my internet still stable It's all on Bungie's side
-
Weasel disconnects me from xbox live every time. Hello Bungie?? Is any one there??
-
Yeah, pretty much happens to me at least 75% of the time I get the weasel error. Other 25% I have to go to the home screen, kill the game, and relaunch because it won't log me back in by staying in Destiny (always says I have to be connected to XBLive and won't load).
-
Happens to me too, and i have no reason why but to every other devices has perfect connection to the wifi but when i play destiny i red bar so much, and yes i reboot my router all the time
-
Fix your game Bungie, i trying to play Iron Banner and i get weasel error only in PvP, and btw is LAG Banner not Iron Banner.
-
Изменено (Jake ): 5/3/2015 3:07:32 AMCentipede does it as well. It sucks. Funny that it's this widespread. I had a mentor tell me it's because [i]my[/i] Internet dropped connection with their services. I'm like yup. I knew that but it's not my internet that's the problem here.
-
I have this exact issue as well. I don't have the ability to go Ethernet cable instead of WiFi, although I've heard that using a wifi bridge also solves this issue as it "tricks" the Xbox into thinking it's running on a line connection.
-
Omg this happens to me too and I'm on the 360
-
Yup this is exactly what happens to me. Frequently enough that now I just skip the "Attempt to re-enter password" steps and jump straight to the hard reset.
-
Изменено (Jebus): 6/23/2015 5:41:55 PMI too get the dreaded Weasel error code that shuts down the network on my Xbox One completely. I thought I was going -blam!-ing crazy blaming my DSL router for this. This only ever happens to me when I'm playing Crucible and sometimes when I'm at the tower, never in PvE. Surely this shit can get fixed soon?
-
I see your problem it easily fixed watch this video shows you how to fix it https://youtu.be/dQw4w9WgXcQ will take seconds
-
I've gotten at least 80% of those error codes... [i]BABOON.[/i]
-
When I was wireless on cable internet, I used to get this once or twice a day. The only way to get internet back on the Xbox is to unplug the console from the wall and plug it back in and restart the console. Ever since I went wired connection on fiber internet, no issues whatsoever.
-
I'd be willing to accept that weasel is a problem on my end but... my Xbox never gets booted from the wifi when playing other games. At least, not this frequently. But let Iron Banner show up and I guarantee I'll get around one weasel per day.
-
Same. Every day.
-
Add Apple and Rabbit to your list of error codes! Haha
-
I havent seen an error code on my xbox yet so I cant say much about it but when I get it on playstation it just puts me to orbit, nothing else
-
There are two types of weasels for me. The normal kick to orbit error code. And the -blam!- your Xbox better unplug that shit cause it won't work again till you do bitch...code.
-
Weasel doesn't always kill my WiFi connection but only weasel kills my WiFi. Haven't experienced this issue with other games but I don't use my xbone much
-
Im on the ps4 and got the blaming weasel right after killing skolas... my ps4 is wired so its not only a wifi problem... kicked me out of psn and everything...fix dis crap
-
I used to be plagued by error codes, until I forwarded my ports on my xbox one- now error codes are rare. It is really simple to port forward, honestly only takes 5 min- to do so first set your xbox one to a static IP address, then login to your router through a computer and go to portfowarding and select the ports to open that you find here http://support.xbox.com/en-US/xbox-one/networking/network-ports-used-xbox-live really simple, I don't have much computer knowledge and I was able to do it Good luck
-
I fixed my Weasel errors a few days ago and haven't had a single error since. This is what I did. I disabled port forwarding and DMZ and switched my router to UPNP. I previously tried Comast and Google DNS and finally set my DNS to Open DNS. Set DNS on your router to Open DNS: 208.67.222.222 208.67.220.220 Then I cleared alternate mac address on my Xbox One Go to Settings -> Network -> Advanced Settings -> Alternate Mac Address -> Clear (This will force a restart) Boom! No errors since.
-
I was having some strange connection issues so I started doing the full shut down (holding power for 5 sec) every time I turn it off. Haven't had much issue since I started doing that.
-
Bungie does it if your cheating
-
I have the exact same thing and it's not Xbox cuz no other game does this and my internet never has a problem at the time on any other device and it also doesn't accept my password for like 20 tries. Very odd