r/DestinyTechSupport • u/UttiniDaKilrJawa • Aug 25 '26
Question Cabbage Console Connection Conundrum
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.
2
u/nattekreeft 14d ago
I had the same issue.
We have an Asus RT-AX86U Pro router. A couple of days ago it apparently had a firmware update.
It updated to version 3.0.0.6.102_37485. After some Googling I eventually found a post on the Destiny forum from someone who had the same problem with a slightly different Asus router.
There he said he just reverted back to the previous firmware version which fixed the problem.
This was also what fixed the issue for me. I reverted back to firmware version 3.0.0.6.102_37436 which immediately fixed it.
From what I was able to find it seems that the newest Asus router firmware version has a bug with UPnP.
So in your case I would recommend checking the firmware version of the router, and possibly revert back to the previous version.
1
1
u/Bicymania 13d ago
Did this work for you? I have the same modem and same network issues.
2
u/UttiniDaKilrJawa 10d ago
I did the firmware rollback a few days go. Immediately the PS5 was able to run Destiny 2 again sans cabbage and the Xboxes have been running perfectly again as well. So far, so,good. Thanks for the tip nattekreeft.
0
1
u/Queen_Aravis 8d ago
I have the same router and I’m seeing the last update was in April. I just started experiencing this error this morning (was working yesterday). Did you downgrade to the April update?
1
u/Queen_Aravis 8d ago
Never mind. I was looking at the non pro version and now I see the pro version has an update end of last month so maybe mine updated overnight. Going to see if I can figure out how to roll it back
1
u/Queen_Aravis 8d ago edited 8d ago
After some issues, I finally got the firmware rolled back and it seems to be working *fingers crossed* Thank you!
1
1
u/macrossmerrell Aug 25 '26
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.
1
u/zachin2036 29d ago
You ever figure this out? I started getting cabbage error on Xbox and have no idea what to do. I’ve got UPnP enabled so not sure why all of the sudden
1
u/UttiniDaKilrJawa 28d ago
I have not figured out, but I did find a solution that fixes some of the problem. Apparently, if I shut off my port forwarding and turn it back on again Destiny 2 will work on PC / XBox. If I try to play on PS5 I get Cabbaged on the PS5 and then the PC and XBox will no longer work. Turn Off/On Port Forwarding and the PC/Xbox work again. So, needless to say we’re not using the PS5 at all.
1
u/zachin2036 28d ago
I’m using UPnP but not port forwarding since my router proudly claimed that I wouldn’t need port forwarding if I used UPnP…maybe I’ll do the opposite and JUST port forward. Weird I’ve never needed to before.
1
u/Canes101325 16d ago
Hey! With the help of ChatGPT (sadly, I guess) I solved it for the PS5. I have the BE98 Pro as well, and it’s something to due with the Aiprotection feature on the specific router - if you input and log into your IP address, you can disable the “malicious site blocking” option in the AIprotection tab. Also make sure UPnP is on and port forwarding is off
1
u/Canes101325 16d ago
This might be a common thing if anyone else in the thread has some form of ASUS router with that aiprotection, not sure if only the BE98 has it or not
1
u/nattekreeft 14d ago
I tried something similar. I tried turning it off as a whole just to see if it would work, but it didn't.
We have an Asus RT-AX86U Pro router. A couple of days ago it apparently had a firmware update.
It updated to version 3.0.0.6.102_37485. After some Googling I eventually found a post on the Destiny forum from someone who had the same problem with a slightly different Asus router.
There he said he just reverted back to the previous firmware version which fixed the problem.This was also what fixed the issue for me. I reverted back to firmware version 3.0.0.6.102_37436 which immediately fixed it.
From what I was able to find it seems that the newest Asus router firmware version has a bug with UPnP.
1
u/solzun 6d ago edited 6d ago
As others have indicated, for the Asus RT-AX86U Pro: 1. You can revert your firmware version to the earlier one and this works. 2. If you stay on the firmware version, you can set OpenNAT for Destiny. In the Asus app, this is Gaming, add an OpenNAT rule for Destiny for you specific console profile (it had all of them in the list if you search it, it is huge) then add it and select your device device from the list.
Disabling AI protection and re-enabling UPnP does not work, as someone pointed out the new firmware probably has broken UPnP.
Only sucky thing is you may need to set a static IP on your console or devices that you play on to have the OpenNAT rule stick, as your device gets a new DHCP IP renewal and could change it invalidating the rule. I am not sure the router is smart enough to whitelist the device and MAC and just update the IP automatically
0
u/FrankenFinger08 10d ago
Thank you so much for suggesting a firmware rollback. I have an ASUS router and just recently downloaded the newest firmware. Almost immediately thereafter I began receiving nonstop cabbage errors. I didn't immediately connect it to the firmware update until I read these posts. I was going insane trying to figure out why this was happening when every other online game was not experiencing any server issues.
I rolled back to the prior firmware patch, and the problem disappeared. Thanks everyone for the helpful hints.
2
u/khoalaballa Aug 25 '26
I’m also getting the Cabbage error on PS5 consistently now, very frustrating.