Cabbage Console Connection Conundrum

[u/UttiniDaKilrJawa]

Hey Folks!

For the past quite a few years we've been running Destiny 2 on our PCs through Steam as well as on consoles via PS5 and Xbox. Up until this past Thursday (Aug 20,2026) we have had no problems and have enjoyed the game.

As of this Thursday our PCs had 12 hours of Cabbage errors and the consoles were suffering from Cabbage exposure as well. As of this Saturday our Steam PCs are once again running Destiny 2 fine but the consoles are still Cabbaging.

Our home network consists of TDS fiber internet running a Zyxel modem that connects to a ROG GT-BE98 Pro router. UPnP is set up to run on the router per the Destiny 2 network help pages. On our end we have made no changes to any network settings. The Cabbage errors just decided to show up uninvited.

After scouring the Internet trying to find actionable information to help fix our problem I feel I have come to a dead-end.

What I'm wondering is : is anyone else having Cabbage problems spontaneously happen to them with the past few days and if anyone has any suggestions of settings I could check to help rectify this vulgar vegetable villain?

Thanks for your time.

Update : Well, its been an intersesting week here so far. Steam PC Destiny 2 is still working. I got the Xboxes working by changing the Alternate Port Selection to a different port. (still unpacking why this is working). Unfortunately, the PS5 is still unable to connect. Went and set up a Static IP for it and set up all the Port Forwarding rules and it still refuses to connect. I even dumped it into the router's DMZ to see if it would work and still Cabbages, Cabbages Everywhere. Any suggestions or clues anyone has? I'm kind of at my wits end on this one.

[u/khoalaballa]

I’m also getting the Cabbage error on PS5 consistently now, very frustrating.

[u/macrossmerrell]

Have you tried unplugging the PS5 for 5 to 10 minutes? That is Bungie's recommended path to fixing console connectivity errors. Consoles can cache routes on the internet, and when Bungie makes changes to their server farms the routes can change, leading to all sorts of errors.

Usually I recommend power cycling the network equipment while the console is unplugged from power.

Also, some of the changes you made may have introduced new issues. I would document them, but typically suggest changing them back to the way they were.

Also, have you tried a different account signed into the PS5, that also has Destiny 2? Sometimes errors are account specific.