Getting cabbage error codes, especially when connecting to games with other people in my fireteam.
1. Use a wired connection rather than Wi-Fi
Yes, wired.
2. Quit any program or turn off other devices that are streaming
Destiny 2 and Discord only.
3. Clear your console cache or, if on PC, verify the integrity of your game files.
Yep, Steam says the files are fine.
4. Power cycle your internet router
Done. No change.
5. Improve your latency and packet loss
5ms latency to Sydney, Australia and no packet loss that I can see
6. Follow our Network Troubleshooting Guide for best optimizing your connection to Destiny. If issues persist, try our Advanced Steps Networking Guide for possible router solutions, such as enabling UPnP or changing your NAT type.
I have forwarded 3074, 3097 manually but as far as I can tell neither Steam nor Destiny 2 are making any UPNP requests at all - even when I didn't have those forwarded.
-
Edited by IamZeN: 5/22/2021 6:49:07 AMSo us Aussies are getting F#@#ed over I too am getting cabbaged in any activity will be going fine then there are no enemies then bam orbit with error message: cabbage , I am also on PC... i'm a D1 vet and would have liked to LFG some VOG but alas that can't happen :( Edit: I have Open Nat.
-
2 RepliesRang my ISP, Aussie Broadband. They said they've been getting a fair few calls about this.
-
Error code currant now too.
-
There are multiple people in the AUS area that are having this same issue. It kicks you when you fly into matchmaking for any activity with Cabbage error codes. I can’t even go into the tower. It was fine last night, I’ve never had this problem. And then this morning it started happening. About 10:00 AEST I started getting “contacting Destiny servers” and it has been happening ever since.
-
Same issue as well but on Xbox series x In AUS too
-
3 RepliesEdited by Chenson: 5/22/2021 5:59:53 AMI have the exact same issue, only started occurring today. Done the same steps through 1-6 as well and still nothing EDIT: Located in Aus too.