{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by 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 RepliesEdited by 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.
