{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/9/2014 5:10:40 PM
31
bee error code
Cant get past first 6 minutes of the game without being disconnected from 'the world' due to the error code 'bee' I call bullshit.. 120 minutes I have been playing now and I've spent 114 of them downloading updates and trying to get around this 'bee' error code.
-
Edited by Raser85: 12/9/2017 4:19:31 PMThis is a pain in the butt...the problem is and always has been Bungies side of things all the way thru Destiny1, and now its happening on D2 . My internet is fine. No other games complain! So I spend a ton of money on my Xbox One and Destiny 2, plus a monthly Internet bill which I am told is one of the best around right now - (the technician said I should be able to connect as many consoles as I wanted, and play fast paced PVP with no issues at all) And after not playing Destiny for a few weeks I was dead excited that I have new stuff to do, after spending even more money on the Curse of Osiris DLC About 10 mins in I get the dreaded message "Attention - Contacting Destiny Servers" and I just knew that I was not going to be able to play my new content today at all... I can't get more than a few minutes through a strike, which is frustrating as fck, or play through a new DLC mission without getting forcibly booted back to my "Press A to Play screen" pretty soon after starting. Bungie have an official page explaining the Bee error and it is pretty much what someone seems to have copied and pasted in an answer on here, but Bungies page is filled with more reasons why it is supposedly MY fault. Just to note though - I pay a few other games online, on Xbox Live, using my internet connection, most are Online PVP or coop, and don't have ANY problems at all. I have been a victim of this right from the days of when I first played Destiny1 and throughout the whole time I played it - over the years I have used numerous connections and internet providers, even now I have access to both neighbours WiFi and it don't matter who I am connected to, I will always get the same problem with Destiny and Destiny2. and Bungie will always say it's my problem some-how - yet it is ONLY ever Destiny that does this shit You would think they would sort their "Servers" out, because they aren't providing a good "Service" to me and tons of other paying and loyal fans of Destiny. And especially seeing as this was a huge problem in Destiny 1....continuosly....and still is. So with that in mind, they must have anticipated that there is going to be HUGE amounts of people playing D2, yet they didn't make preparations for that extra traffic clearly....buy a bigger server, or connect more up I dont know, but it aint working as it is and this is the ONLY thing that is putting me off playing - in fact it is physically stopping me from playing the game I have spent all this money on. PLEASE SORT IT OUT SOON BUNGIE - or I am have no choice but to play Warframe - they dont behave in this way and they are FREE
-
1 ReplyEdited by TEH G0D: 2/27/2015 3:46:06 PMFor bee there is no solution. It is caused by disconnects between your router and Bungie's servers. It can also be caused by certain WIFI setups or faulty in-home wiring, as well as other devices such as your phone or tablet being on the WIFI the same time you are trying to play Destiny. This is very very likely to happen on a college campus.
-
Unplug your consul and restart it. That should work. That is what I do.
-
8 RepliesI get kicked with error code Bee daily - its incredibly frustrating and weirdly will let me play most of a crucible match before kicking me right before the end [u]every[/u] time. Same goes for strikes but less regularly - when you're 30 minutes into a coop mission and it randomly boots you right at the end then emotions run VERY high. I have never had any issues with any other multiplayer game - wired connection seems to make no difference so I'm looking at Bungie - please get this sorted guys, the lows are outweighing the highs at the moment because of this - large portions of the game are effectively rendered redundant, this has been happening since day 1 and i'm massively dissapointed that its still ongoing especially with so many people who are clearly affected - mine and i'm sure other's patience is seriously running out!
-
I'm really getting tired of these destiny servers I'm about ready to say "-blam!- you bungie got back to xbox"
-
Bloody 2015, still getting bee.. never used to get it, but recently ive been doing strikes and raids and it.BOOTS.ME.AT.THE.END. Destiny: Trollololololololololololol
-
I'm getting bee error code now as well been playing for 2 hours all of a sudden can't join
-
Same here. I can play PvE fairly smooth. As soon as I go to the tower.....BEE. If I try to play PvP, I am "contacting Destiny servers before I even get out of orbit, then kicked with BEE Error. When I try to raid with 6 people, I am kicked to orbit with BEE Error within 5 minutes. I have tried every trick and fix. Nothing seems to fix it. Just waiting for a real fix, or Hardline to be released.
-
1 ReplyI got bee right after I killed omnigul in the nightfall today right after I killed her and I didn't get anything I was so mad
-
Started a new topic: any one else but me getting error code bee today
-
Getting the bee code since today and that nearly every 10 minutes. Already opened all ports and changed to wired connection. Got open nat and everything -.-''
-
I have been getting the bee error for 2 days now and its -blam!-ing annoying I can hardly play. This is ridiculous fix this shit now!!! Today is extra horrible I get kicked every 5 mins so ima turn my xbone off now. Smh!!!
-
1 ReplyEdited by Steel Revenant: 10/2/2014 12:03:41 AMPorts forwarded, wired connection, cache cleared, and still getting bee errors. Obviously this is on bungie and not a personal router issue. If someone plays without a bee error then give it a little while, it'll happen. It's been hit and miss on whether I have a day without bee errors but it seems like once it starts, it continues for awhile. It's ridiculous. The claim of 53% reduction in new errors by bungie just means it's got a 47% failure rate, and to be honest I think even their claim is false as it seems a lot higher than that. I'm thinking their figure of 53% less failures is actually due to them losing 53% of their player base due to all of these errors which has showed 53% less errors being reported than previously because there's less total people actually trying to play now. The decrease in reported bee errors is only because there's less people still around to actually report said errors. If no one is playing this game then no one's reporting errors. Good job on the fix bungie!!!
-
Ive been usin the same router since i got the game. This bee error only started for me the past few days. My router is my modem to so i cant switch routers. This problem is extremely irritating n hope xbox/destiny can fix it
-
1 ReplyI have played this game all the way to level 15 ay home on WiFi,with no problem,until right in the middle of level 15 ...error bee,then error m, n next error c,so clearly it not my wifi,or psn, it bungie, they need to get there shit together fast n in a hurry!
-
Edited by damentor: 10/10/2014 1:33:39 AMI can't start anything due to this bee error code, followed by fly on occasion. It is consistently bee. I didnt do any changes to my network. It was working fine and then all of a sudden, ive been getting this error code that makes this game virtually unplayable.
-
I've this error every day in the crucible. I tried with the connection settnings of my router but the bee error continues. I think this is a bungie's problem...
-
Edited by jcorne: 10/20/2014 12:18:36 AMSame issue. This problem is absolutely crippling and unacceptable. Bungie made a broken game, bottom line. I am almost sure it is the Bungie servers too. My internet connect has not changed since I bought the game, plus these errors always come up during peak hours (weekends, etc). I might get 20 secs of gameplay before getting booted. But on off hours, like a weekday, it works fine. That shows the problem is not local and on their end. Since I only play on the weekends, it basically makes the game unplayable.
-
same issue
-
I to experienced bee if you have not already try moving you system closer to the internet router Note: I am on ps3 and don't if this will work for the other systems
-
2 RepliesCant play 5 Minutes of Multiplayer without connection loss and error message "bee". I hate how they waste all this money without having a decent infrastructure. I wont recommend the game to anyone.
-
Bee. I've done everything Microsoft has told me to do. They said they'd call me back. Suprise nothing. This is my one weekend to play w out my 2 kids. The only thing that will work is them fixing their servers. No1 will get their precious expansion packs w their busted network
-
3 RepliesIn the beta I found error code bee is a issue with your router. I can't play a strike mission for more then 20 mins before getting kicked. However if I plug my ps4 directly into my modem I never see that error again.
-
1 ReplyHey guys I might just be the hero that you need, I've had this problem since destiny came out, I've tried everything under sun to try and fix it, I've been port forwarding setting static ip's basically everything that anyone says to do I've done it But mines now fine and all I did Was I went to my grandmothers and borrowed her old ass router and plugged that in instead, and now it's perfect, I highly suggest trying it, doesn't have to be a top of the range one this was just one given by her ISP I spoke with someone at Microsoft and Apparently some routes peak out and a certain range and destiny needs the high range So good luck Post backet me know how you got on :)
