{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Editado por BNGHelp0:
4/15/2018 3:49:22 PM
22
Error codes: CABBAGE and CURRANT
Hello!
I've been playing Destiny 2 since release with no problems except for minor hiccups. Last night I got a couple server errors, but my friends had one of those too so I didn't worry much.
Today, the game was near unplayable. I did have a centipede error too, and that prompted me to follow the upnp steps and nat configuration stuff. Did it all on my pc, started getting cabbage and currant. Slightly better connectivity, lets me at least play for a bit before disconnecting, but getting errors eventually.
My router isn't a thompson or technicolor either, as far as I know the brand's mitrastar.
Any reason why this might be happening? Any other steps I should follow? Didn't do the redirect step in rooting (nat thing) because I don't really know how so that might be it.
-
39 RespuestasEditado por BNGHelp0: 4/17/2018 5:59:13 PMHello all, Thank you for all of your reports! We are aware of elevated CABBAGE, LETTUCE, and COCONUT errors across all platforms. We are currently investigating the causes of these errors. Please stay tuned to [url=https://twitter.com/BungieHelp]@BungieHelp[/url] for updates. UPDATE 04/17/2018 11:00 AM PST: We are continuing our investigation into the elevated rates of CABBAGE, LETTUCE, and COCONUT errors that began around Saturday 4/15. Players encountering these errors may also see CURRANT and RABBIT error codes. [b]If you are encountering these error codes, you can aid in our investigation by including the region in which you are playing along with the error codes you are encountering[/b] in your reports of this issue here on the #Help forums.
-
https://www.bungie.net/pt-br/Forums/Post/244548601?sort=0&page=0
-
[b]It's already working fine for me. Thanks[/b] Country: Colombia ISP: Movistar
-
6 RespuestasEditado por gaxconj: 4/16/2018 2:30:58 PMHello, I have the same problem since Saturday(I live in Spain) in all my devices. Same errors on PS4, Xbox One and PC. I've been playing Destiny 2 since release without problems. And all my other games are working. Only I have the problem with Destiny 2. I try to power cycle my devices. I try a factory reset on my ps4 and my xbox too. I try a factory reset of my router... Nothing works When I try to play in PS4 the game says that my NAT is type 3. But when I going to Networks Settings mi PS4 says that I have NAT2 as always. In my PS4, Xbox and PC i'm getting centipede, cabbage, currant and lettuce errors. The game is unplayable And I try to do all things in bungie troubleshooting guide. But doesn't work Sorry for my bad English
-
1 RespuestaHey everyone. Friend of mine having trouble too. Not as much or as often as me, but points to a server problem instead of a connection one I think. As far as I know there's no news from bung but I guess there'll be.
-
I have been playing 1 hour (12 A.M TO 1:00 P.M (UTC+01:00)) in PS4 without much problems, I have only received 1 cabbage in 5 or 6 games of iron banner. Please try to power cycle your devices and try if it's working better or if I was lucky to have been able to play one hour. Disconnect from power source of the router and the PS4, or Xbox, from 5 or 10 minutes and try again. Please test it. Thanks. I hope that this things could help Bungie
-
4 RespuestasEditado por mikethor007: 4/18/2018 12:42:34 AMSame thing here. Problems seem to have started friday or saturday. PS4 system. Brazil. VIVO ISP (which is a company related to movistar). Cabbage, lettuce, coconut and centipede here, at the very least. I can at most get into the tower. Can't join other player's sessions. Can't start a matchmade strike. I spawn into the world, see no one whatsoever for a time (no enemies/npcs/players) and then get booted with the error. The thing here is that this particular problem might not be easily solvable on bungie's side. Or our side either. It's starting to look like some router along the way on the internet is interfering with our games badly. Might be Movistar dropping/filtering/blocking certain stuff that passes through their network. And for me it's not only D2 that's affected. I'm getting tons of errors in Monster Hunter World too.
-
Same here, Europe region, spain. Lettuce, currant, rabbits ERRORS
-
1 RespuestaBungie doesnt do anything for a fix you have to get a laptop or something and hotspot like its a real router so that you dont get the errors It will slow down your connection but if you want to play do that
-
Hello everyone, This also happens to me, as is described in this post. I have a PS4, since D2 came out I never had these problems. It began all Saturday and remains until now. Coconut, Lettuce, Rabbit errors codes, I try to enter an activity and the connection is lost immediately, I can not even enter the tower. I could only play crucible, although I also got the errors codes there. I also got the CENTIPEDE code when I tried to enter the game. I have released the cache from my console and from my router several times but the result is the same. Additional to this, also happened to me since last week, that does not allow me to enter the game with the message "servers are not available" This happened a few weeks ago but then resolved, deleting the game and re-download. Which I did again on Friday but without positive results. On Saturday I was able to enter the game but with the results described at the beginning of this post. Please your recommendations and help. Thank you
-
3 RespuestasEditado por XXVIII VII LXI: 4/16/2018 4:06:58 PMsame problem, I live in Spain and I am playing by Xbox One I never had problems like those before.... since last sunday 15/april I can not play well. PLEASE "Bungie" answer us something !! apparently everything on my conection is OK I have 300mb with Movistar company my NAT is open even I have open all my ports 3074 etc... !!! PLEASE HELP !!!!!!!! :( also Mitrastar ...
-
Editado por eLGato: 4/16/2018 9:53:29 PMI'm having this same issue and I have the same kind of router as do a bunch of people I've seen online, I talked with my ISP earlier today and they say that there are no restrictions in either my NAT or my firewall and even after messing around with the router settings nothing has really improved. looking at the upnp log on my router it seems to be opening the 3097 port just fine everytime I try to play but it still kicks me to orbit after about a minute.
-
3 RespuestasHeya ppl same problem, had any luck anywhere else??? btw modem`s mitrastar too
-
Editado por Nicko: 4/16/2018 9:43:32 PMHaving almost the same issue here, up to yesterday everything was fine, as a (kinda) guilty pleasure I've quite spent some time playing D2 so as far as I know I could play easily for hours (like a whole day) without a single problem, but since yesterday I can't play almost a run in a strike, today I barely go to the tower, if I don't manage to go there and nothing (NPCs or Players) loads, always currant, cabbage and lettuce, hardly a different code but sometimes is, even feels like it got worse from yesterday to today, I really wanted to know what's happening because I'm seeing this happen with A LOT of other players, when it doesn't happen to me it happens to someone in my fireteam --" Edit: Whole post was in the 2nd day, today's the 3rd.
-
Editado por Bais: 4/16/2018 2:14:31 AMSame here. Cabbage, lettuce, currant and even a hare error popped up once... Never had any real problems playing Destiny 2 but I guess today was the day. I forgot to mention the CENTIPEDE error when trying to log in. Playing on PC.
-
Same problem here! started this weekend and still happening until now. I play on pc and dont have any of these routers
-
1 RespuestaBungie might be tweaking the game/servers to ready it for the update. I have fibre speed of 100mb/s and still get the same error codes so it's the game not us.
-
2 RespuestasNo worries every error code states it's on your end an not on Bungie's side. All the fanboys will come agree and spew BS for things they do not know to defend Bungie and never admit it's Bungie's fault.
-
-
Same issue here, same codes..., did they said anything?
-
Editado por Spartan 18877: 4/15/2018 6:46:42 PMSame thing, in a 300/300 FTTH conection with upnp and DMZ.is not a thomsom/Thecnicolor router, and it has started 2-3 days ago. Cache has been cleared in xbox and router. Its a bungie issue, as usual.
-
I'm have all these 3 error since yesterday: cabbage, currant, centipede. I can't stay 10 minutes inside tower without get one of this errors. I'm surely the problem isn't my router, cause i fix it settings and my Nat is open. Sorry for my bad English.
