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 exact thing happened to me today.
-
Yes I've had this happen to me as well. Have to unplug both the Xbox 1 and my wireless router. Once I wait 30 secs and plug everything back in I'm good to go again on Destiny. Bungee says that you need to plug your wireless directly into the Xbox. My wireless is in another room so that's not happening. This sucks. Errors tend to be more prevalent on Tuesdays because everyone is back playing as it's the weekly reset.
-
Same here on the error
-
Happened once to me as well and I did the same thing hard reset and worked fine
-
Same was happening to me. I had to turn off xbone and unplug it for my Xbox to connect again
-
Had the same error last week. Was down almost 24 hours. Eventually after hard resetting my router, modem and Xbox one......numerous password tries.....it started to work.
-
I can confirm. Once a day I have to hard reset my Xbox one after weasel error.
-
When I get the weasel error on xbox one, it's usually a whole lag sequence that I have to wait for to pass. Resetting internet doesn't work
-
This happened to me once
-
Buy a ps4. Never have network issues.
-
I do all those steps daily too. Its pissing me off. Its all since this new companion app was added. Never been same since for me and i dont use it. After seeing your post though im kind of glad im not the only 1
-
It broke my router the last time it happened.
-
I had this issue until I spoke to Virgin Media and asked to to setup Port Forwarding to my Xbox One. Took them about 10 minutes on the phone and I've not looked back since. After weeks ok Weasel errors I think I've had one error code since then (a bee I believe). I'd seriously consider it if you're having the same issues.
-
I received 2 new error codes recently one was jackrabbit and I can't think of the other one it was a small word lol but I never received it before
-
I'm in the same boat. This only happens when I play destiny. If you don't hard reset your Xbox and turn it off normally it gets stuck in this loop and just keeps blinking so you have to unplug it.
-
I get canary, and there's some days where this game will literally shut off my internet for seconds at a time every 10-15 minutes, and it restarts like nothing happened, and I have to restart the game all the time
-
Same cap happens to me. Also, for the people saying it's because I'm using Wifi or its the Xbox: it only happens when I play Destiny.
-
i also have the same issue,at first i thought it was my router i had a top of the line apple router returned it and got a top of the line linksys did the same thing,ports are open,open nat,and still have the issue here and there it's very annoying and it's a issue on bungies end not ours.i have no issues with any other game any other wireless device in my house
-
At least you dont get Wasp
-
Bungie corrupting hardware?! Gasp!
-
I have the same thing happen to me on a daily basis
-
I and others are getting Weasel, Fig and Elk and am hard wired, not using the companion app, not using cell phones/mobile devices/hot spots or the web site while playing. Errors codes are a joke now. We have checked and double checked our settings, reset the router and this all has happened since the last update. It is not you or anyone else having these current issues. It is Bungie's own handy work that is causing these problems.
-
Or Maybe, you know, your console is disconnecting itself from your wireless and that's resulting in the weasel error. Don't you think perhaps that's the more likely scenario?
-
I don't feel like it's the error code doing it, my 360 does that on wireless or wired. I'll get kicked offline mostly without an error code and then have to restart my Xbox just to get back online. Plus it'll happen when not even playing a game, when I'm watching videos or just on the dashboard sometimes.
-
I don't feel like it's the error code doing it, my 360 does that on wireless or wired. I'll get kicked offline mostly without an error code and then have to restart my Xbox just to get back online.
-
Using an Ethernet cable might solve your problem. Are you able to hard wire your console?