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....
-
Lol pleb tier Xbox That's all.
-
It happened to me for three days a week ago. I took off power from router and the console. Waited 30 sec then restarted. It worked for me each time.
-
Happens to me around 1:00-3:00 PM everyday.
-
This shit! This happens to me like three times a day. My brother is on the same connection and doesn't have any issues
-
Yeah, when I see weasel pop up I shut off the xbox and turn it back on. Nothing else works. Doesn't matter if I am playing over wifi or hardwired.
-
I have the exact same thing happen to me all the time. It's incredibly annoying. I've even tried proactively resetting routers but to no avail. And only my Xbox gets disconnected, phone and computer are fine.
-
Lol maybe it's because of Netflix users around the house. Another thing, I Ethernet cable my Xbox for the full experience.
-
I've had weasel actually knock out whole house off the internet. I got weaseled, hard reset, and still nothing.
-
I play on ps4 but I get a crap ton of errors even though my internet is running at an amazing speed. It's always weasel, bee, baboon, Rabbit or centipede.
-
I had a few errors mess with my Xbox one also I don't know y but it's Destiny all other games r fine.
-
Ever since the first time this happened to me, I skip steps 2 through 5 and just immediately do a hard reset on my xbox. But yes, this exact thing happens to me.
-
Happens to me as well. Been about 4 or 5 times so fae so not horrible but took me forever the first time to figure it out.
-
Last night was HORRIBLE!!! I was swordbearer and crota had 25 percent health on hard mode and just as I was about to say take him down. Weasle!
-
Last night I was doing vog and got the same error as you although my internet wasn't cut off, xbox live just went offline!
-
Happens on ps4 aswell
-
i have an xbox 360 they call it an xbox 360 cause when i see it i do a 360 and then walk away
-
This is news to me is this just an Xbox problem or is it on playstation too ?
-
Ive had this happen a couple times. Unplug everything from your xbox, wall, and tv, then wait like 5-10 mins and you should be fine.
-
Yes, I've had to hard reset my Xbox week after week because it wouldn't connect to the wifi or the dashboard wouldn't work or something. Someone told me to start closing my apps before shutting off my Xbox, and I've not had to hard reset for about a week in a half now. Not sure if it's the same problem but I guess it fixed it for me.
-
i've gotten weasel 3 times today... been having to hard reboot the xbox each time...
-
everyone says hard wire hard wire, why? Half of glamour of these consoles is playing wirelessly...duh, so having to run a mile of Ethernet, or rearrange the house to place TV, console closer to the source is ridiculous. How about the machine works as intended, quit placing a band aid on the issue with hardwiring. How does my 360 work perfect but my One keeps saying "contacting destiny servers"?
-
This happened yesterday, except it knocks out Internet on all of my devices
-
I get this error code daily and a few times a night. Only on my Xbox one. Doesn't happen on my ps4. I don't know wtf this is but it needs to be fixed. Everyone in my clan has this issue as well. Hence the clan motto, gotta hard reset.
-
I get it all the time too. Thought it was my Xbox but destiny is the only game it happens with.
-
[quote]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....[/quote] Use wired internet
-
I've had weasel disconnect me many times. More so in the last week than ever though. It kicks me off my wifi too and it won't reconnect until a hard reset on the box, and reset my wifi. Hasn't been an issue until this last week.