{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by GRUMPY ASSASS1N:
1/1/2018 7:46:19 PM
187
Keep Getting Error Codes
Hello all,
I've been trying to get on Destiny 2 since 15:45hrs GMT yesterday - 31st December - but I keep getting these error codes:
Hare
Lettuce
Centipede
Currant
I'm with BT and have their Smart Hub... All my other games work fine and my NAT settings are open. Some people are thinking that it's a Bungie issue?
Thus far, as of 19:46hrs GMT today, I have still been unable to get on to D2.
Is anyone else having the same issues?
Regards,
Dallas.
P.S. As an afterthought Guardians, can you please state with whom your ISP is, also your location in the world and possibly error codes too? Many thanks.
-
Since 2 weeks i get this f.ucking errors. i had to restart some missions over 20 times about these errors i cannot finish 1 strike or 1 pvp game because of this shity errors!!!! its very lame that nobody from bungie is here to help us!!!!! So many buyers have this problems, they earnd so much mony with us! but nobody bring out a competently solution!!!!! they only give us shit and we must eat it!!!! Seriously bungie why does nobody help us? We paid well for the game and can not play it now!!!!! and many of us think the same: so how about a compensation that you cost us nerves, time and money!?
-
I have had disconnects and getting kicked to orbit since the game came out and the funny part you can't make a ticket just a useless topic on the networking forum with no reply from any tech or mod from bungie.. Never buyin any shit from this company again this was the worst gaming experience I ever had.. Not to mention I am like anyone else all other games running with zero problems.
-
Lot of "network" problems, here, in Belgium too (gabbage and others). I checked all the "solutions" given by Bungie, but nothing helps. Network is fine (86 Mb download, 16 Mb upload, 15 ms ping, on XBox statistics). NAT is open. All other games are working fine, even Destiny 1. Destiny 2 is the only game that's not working. I can't complete some missions. "Bad reception", by instance, (a good name, in my situation), one of the first missions in European Dead Zone. My ISP is "Proximus", belgian ISP.
-
Still cabbage/beaver
-
1 ReplyWas just doing an adventures on my new Hunter & got Cabbage, sent back to orbit
-
7 RepliesUltimately Bungie you have to own this and all service issues, representing us as your customers. It might be a BT issue but as a global software player you will have key contacts at all the major ISP’s, so if it needs a call from you to BT then you can escalate and get action between you to bring resolution and get you Guardians back playing. Your commitment should be to represent the global gaming community, that applies in all countries, yes even outside the US. We were told you are listening to us, are you ? actions talk and BS walks !! There has been major noise about U.K. issues in multiple forums yet the silence is deafening, we want to commit to Destiny but communication is a two way street, so all we ask is respond, or what’s the point of these forums, talk to us...
-
That maintenance they did today did nothing on my end
-
i played destiny just fine till about a week ago now i cant do anything without a bee weasel anteater buffalo virginia Comcast I had comcast replace my router today and still same issue
-
3 RepliesDestiny 2 is working again, for me at least. Hope it works for you guys as well. Happy new year!
-
Seems to be OK here now ... played various public events on IO and 3 heroic strikes. Does anyone know the official reason for the issues?
-
6 RepliesThanks bungie from Bristol with Bt today no problems at all!
-
7 RepliesEdited by Tealeaff: 1/1/2018 12:13:15 PMI play Destiny 2 on the PC and have exactly the same issue - also with BT. It all started yesterday afternoon getting kicked with currant, centipede and lettuce error codes. I can sometimes log into Destiny 2 for a short period, get to the surface of EDZ or a cruicible match. However, it complains that i am using NAT 3 (I am not - my HUB says NAT 2), then it kicks me with an error code. Going to a social space is possible, however, in the unlikely chance you can get there then you will be greeted with a barren, NPC-less experience followed by a swift boot from the game. I have tested the my connection playing other online games such as WOW/guildwars etc and its absolutely fine. No issues at all. ! checked out you tube and all is fine. BT say this is not their issue, but an issue with the D2 servers and i am inclined to agree with them as the connection is fine for everything except Destiny 2. Bungie can you at least acknowledge that there is a problem and that you are looking into it? Thanks.
-
Everything this gaurdian says , plus i deleted D2 in hopes of fix , same probs . Baeal I play Destiny 2 on the PC and have exactly the same issue - also with BT. It all started yesterday afternoon getting kicked with currant, centipede and lettuce error codes. I can sometimes log into Destiny 2 for a short period, get to the surface of EDZ or a cruicible match. However, it complains that i am using NAT 3 (I am not - my HUB says NAT 2), then it kicks me with an error code. Going to a social space is possible, however, in the unlikely chance you can get there then you will be greeted with a barren, NPC-less experience followed by a swift boot from the game. I have tested the my connection playing other online games such as WOW/guildwars etc and its absolutely fine. No issues at all. ! checked out you tube and all is fine. BT say this is not their issue, but an issue with the D2 servers and i am inclined to agree with them as the connection is fine for everything except Destiny 2. Bungie can you at least acknowledge that there is a problem and that you are looking into it? Thanks.
-
Edited by wbacasual: 1/2/2018 4:43:22 PMSeems to be working just very slowly, manage to get to tower and pick up the daily gift for two characters just took a long time to get there Edit: all working fine for last few hours
-
Bungie have acknowledged the problem but posting on Twitter. [url]https://twitter.com/BungieHelp[/url] I was also able to load up a few things this morning with no issues. UK on BT using a Smart Hub. Haven't been able to play smoothly since 6:30 Sunday evening. Have been able to load things after a few attempts so don't know the best way to test whether it's working seems I've had periods where after a few attempts it works. Hopefully it'll be 100% by reset!
-
9 RepliesEdited by PshycoKilla2013: 1/2/2018 1:29:25 AMAny progress with this 'investigation' yet BUNGIE?? Please hurry im starting to get withdrawal symptoms now 😂😂
-
[quote]Hello all, I've been trying to get on Destiny 2 since 15:45hrs GMT yesterday - 31st December - but I keep getting these error codes: Hare Lettuce Centipede Currant I'm with BT and have their Smart Hub... All my other games work fine and my NAT settings are open. Some people are thinking that it's a Bungie issue? Thus far, as of 19:46hrs GMT today, I have still been unable to get on to D2. Is anyone else having the same issues? Regards, Dallas. P.S. As an afterthought Guardians, can you please state with whom your ISP is, also your location in the world and possibly error codes too? Many thanks.[/quote] Looks like the problems solved just played 2 strikes and now loading my 3rd no issues
-
2 RepliesUltimately Bungie you have to own this and all service issues, representing us as your customers. It might be a BT issue but as a global software player you will have key contacts at all the major ISP’s, so if it needs a call from you to BT then you can escalate and get action between you to bring resolution and get you Guardians back playing. Your commitment should be to represent the global gaming community, that applies in all countries, yes even outside the US. We were told you are listening to us, are you ? actions talk and BS walks !! There has been major noise about U.K. issues in multiple forums yet the silence is deafening, we want to commit to Destiny but communication is a two way street, so all we ask is respond, or what’s the point of these forums, talk to us...
-
4 RepliesGetting the same here too, was fine for about an hour from 10am (gmt) but been booted off by lettuce and cabbage since
-
All just logged into the tower no issues. Everyone was there and haven't been booted. Good luck to you all and hope the issue is fixed for you
-
bt uk. also know 3 others with same issue, also bt, 2 friends within 3 miles on different isp no issues.
-
Same with me, I'm with bt and seem to get different error codes every time. Impossible to play. Hope it will be fixed when bungee are back after holiday!! Not a good situation, all other games playing fine.
-
Same problems. Lettuce and Cabbage mostly. I tried adding some port forwarding to hopefully correct it but I got a Beaver error code instead. I reset my router and and talked with my ISP (sasktel) but they were just as confused as me. Since the reset I'm back to getting cabbage and lettuce error codes. I'm convinced it's on bungies end. I'm willing to receive Engram compensation.
-
4 RepliesPretty sure my dreams tonight will involve Coconut , cabbage , lettuce , current and centipede . It’s gonna be trippy .
-
May be due to some server upkeep on Bungie's part, or I may have found a workaround, in either case, I'm now able to log in and stay logged in without being quickly disconnected. Seems it may be to do with BT's handling of IPv6 addresses. Check out my post on the matter if you're still having issues with Cabbage Centipede and Currant: https://www.bungie.net/en/Forums/Post/241361587
-
Edited by GetUpAndGoGamer: 1/2/2018 9:14:57 AMexactly the same issue here. started off as alerts telling me that my NAT was set to strict so sat there for hours unplugging things and changing settings. then that stopped and it refused to let me even log in. error code centipede every time. also using bt in the uk edit: tried logging on this morning and so far all issues seem to have been amended. im logged in. playing strikes and with other players. hopefully this will remain so
