{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
11/7/2018 8:14:29 PM
3
Costant "Cabbage" and "Beaver" errors.
Isn't it lovely when you can play every online game on earth beside Destiny 2? Yes, I have a Technicolor modem ('AGVTF_5.3.3': which doesn't even let me open ports because -blam!- me I guess), but still, why on earth is this the only company with this kind of problems? I can't even finish a single quest, or public event that I get disconnected...
-
Hello. Thank you for your report. We are tracking an issue with players who have Technicolor and Thompson routers and the CABBAGE error. There seems to be an issue with the security configuration on these routers and connecting to Destiny 2 properly. Some players have found a fix for this issue by following the steps [url=https://www.bungie.net/en/Forums/Post/231008613]in this thread[/url] or [url=https://www.bungie.net/en/Forums/Post/241743364]in this thread[/url].
-
Sometimes it doesn't even stop the cabbage errors after changing your router unless you get a new console or PC too. The best fix is setting up a hotspot and connecting your console to that, it doesn't eliminate cabbage errors but I only get 2 or 3 a week.
-
Same here man unbelievable that you can find report online of this since day 1
