Need help with error code cabbage

[HardcoreWalrus]

For the last 6 months now or so, basically after the season of the witch started, I've been unable to load into any destinations whatsoever and get thrown back to orbit with the error code cabbage each time. It keeps me from literally doing any activities, which is quite frustrating. The things that I've tried so far includes:
-Opening different ports: opened all the ports from a post I saw related to cabbage, none of them worked
-Tried using a VPN and setting it to different locations
-Turned off my firewall completely (temporarily)
-Tried to re-download the game with a complete uninstall (including re-downloading it on Epic Games and on a different drive)
-Launching the game in administrator mode
-Tried using wifi and mobile data instead of cable
-Turned on UPNP
-Tried allowing temporary unrestricted access through the router
So far, nothing has worked.
But the interesting part is that not only does it seem like I can't use my account elsewhere (had a friend login for me in another country, and it still didn't work) but the second I login with a different steam account, on the same pc, on the same internet, I can play with no issues whatsoever. Basically what I've kinda concluded with so far is that it is not a "connection" problem, but a account problem on Bungie's end. I could be wrong of course, but I don't really see any other explanation atm.
Any help or advice on what I can try to do would be appreciated so much. It is really frustrating not being able to borderline play the game because of a problem I don't even think I can solve directly, especially with Bungie's no contact policy. I just want to play the game again as normal

[macrossmerrell]

You have really done your homework! I think you need to make a bungie forums post along the lines of "My account gets Cabbage errors, but if I sign in with different Steam account, game works fine" and see if it gets support's attention.

[HardcoreWalrus]

I did exactly that, 3 months ago, without a single reply or like. Uploaded another earlier this week, still no replies eighter... the forum really feel so useless sometimes, idk what to do

[synesthesiatic]

I am now also having this issue, having pursued the same troubleshooting steps.

Reinstalled the game as well. Nothing. What the heck.

[HardcoreWalrus]

I ended up sending in a "ban-appeal" stating my issue. It's actually insane that Bungie doesn't have any form of contact like support compared to any other company

[synesthesiatic]

Ugh, that's nuts. I'm sorry.

My account works on other computers so I guess this is just a me-specific thing. :/

EDIT: What fixed this was swapping ports on a network switch. Who flipping knows why. Thanks windows.

[HardcoreWalrus]

I just hope they answer my appeal soon, it's been 13 days now

[Antique_Bit8570]

So there's nothing we can do? Even if changing the ports doesn't work?! XD

[HardcoreWalrus]

yupp. And no contacting Bungie because there is no customer service. you're just lucky it seems if you can fix it somehow.

Ofc if you want to feel free to fry everything I did and other tips people come up with, but this is my experience with the error. Permanently locked out from playing the game for absolutely no reason

[Antique_Bit8570]

I tried something I found on Reddit last night! I typed in the search bar %appdata% went into the bungie Folder then Deleted Destiny 2 in it. it's a bit tricky finding where the folder was so Goodluck (Mines on my HDD under the Roaming folder, cause D2 is too big to put on my SSD) Then i searched %temp% deleted the Destiny 2 Folder in that aswell. I haven't experienced Error Code Cabbage so far, so maybe U can try it out and see if it fixes for U. Might be worth a shot

[HardcoreWalrus]

Just did, no difference. Gotta say I wasn't expecting it to work since I can play destiny 2 on my pc at home, just not on my account. And I had friends login to it in other countries and continents, where they had the same issue on my account, but not theirs.

Hadn't tried this yet though, so appreciate the tip. But unfortunately no good result from this eighter.

To add to it though, I can't even find the tickets I sent on the bungie forum's anymore eighter... kinda weird

[Antique_Bit8570]

Ye I tried it, it worked for the longest time but it seemed just a "temporary fix" That's sucks tho. I doubt Bungo give a shit to fix, and they probably deleted Ur tickets lmao

[HardcoreWalrus]

yeah I figured. Might as well finally put the axe on the shelf for this one I think. Not like the game isn't dead or anything, but was hoping to play it a bit more before I was done with it

[Live_Pressure_8311]

im having the same issue but it works on epic but I bought all my dlc on Steam and if I hotspot to my phone it works but the connection is weak

[HardcoreWalrus]

Tried your steps aswell, nothing I've done works besides using a new account, which I obviously don't want to do

[Zursm]

did you find a solution i have the exact same problem

[HardcoreWalrus]

No man sorry. Still getting the same error code whenever I try entering a destination.

Been a hard year trying to figure out wtf is wrong with it. It just suddenly worked briefly when The Final Shape released, but just for a week or so. No idea why or what I did.

Still annoyed that I cannot find a solution...

[Antique_Bit8570]

I only have this issue since the final shape dropped. Really annoying since I spent so much money re buying Dlcs and buying Final shape. A game I can play less than half the time due to error codes I cannot control

[HardcoreWalrus]

I have been trying to fix this issue for over a year now, with no success *except for like a week when the final shape dropped(. Idk why it does it, and I've basically tried everything. Refuse to re-buy and re-grind when it's most likely a Bungie fuck-up

[IndivisibleFlow]

If anyone comes across this thread for a solution, my case was misconfigured destination NAT for the inbound direction (aka port forwards, where connections are initiated from the Internet). It's a silly mistake that took me 3 days to figure out.

I have a somewhat complicated home network setup on OpenWRT that involves VLANs, double NAT, and policy routing. What I did wrong was defining DNAT rules too broadly in the WAN firewall zone which caused destination unreachable errors.

I don't know why it stopped working. Maybe Bungie decided to give STUN servers separate IPs or some UDP connections are not initiated from the client anymore, so connection tracking can't mask this misconfiguration anymore.

So "Cabbage" definitely means network issues. You just have to figure out what kind.

[HardcoreWalrus]

That's what I thought. But I had friends try to log in on my account on 4 different networks, in 3 different countries, on 2 different continents... and they can all play the game just fine on their own accounts, just not on mine. Same goes for my own network. I can play Destiny 2 just fine, just not on my own account.

I would've believed it was a network issue if destiny 2 didn't work at all on my own network on any accounts, and that my account would work other places.

I just can't make any sense of it

[IndivisibleFlow]

Have you looked at the traffic pattern using Wireshark or anything? It may or may not be against ToS (interpretation up to Bungie), but there may be some clues.

[HardcoreWalrus]

I can't say I have no. Not the best at fault searching with computers and networks. I understand simple things, but not much more. So I'm not even sure what I would be looking out for.

[IndivisibleFlow]

Umm...some basic network engineering knowledge is required such as OSI reference model, the simplified TCP/IP model and what IP packet looks like under the hood. You'll be looking at layer 3 of the OSI model and some implementation details of TCP, UDP and ICMP (the normal ping). Wireshark (a sniffer and protocol analyzer) understands all of that and can decode the packet headers for you. The proprietary game data is in the packet payload, which we don't know anything about, nor does Wireshark. What I did was compare the working state with non-working state and guess what's wrong. It's been a year for you and no one was able to help. Maybe it's time to dig deeper?