When launching into Destiny 2 Season of the Witch, I played through the first half of the Way of the Witch starter quest only to have the cabbage error return me to orbit. If you’re experiencing this error too, here is your guide on how to fix the cabbage error in Destiny 2.
Related: Aztecross calls out Destiny 2 devs for “lack of PvP content” – and I agree
How to Fix the Destiny 2 Cabbage Error
The cabbage error, like all errors, is extremely annoying in Destiny 2. I have started and been returned to orbit four times when trying to complete the Way of the Witch starter quest in Destiny 2 Season of the Witch.
Unfortunately, the cabbage error isn’t tied to a quest or a season. This error can come and go in Destiny 2, and if it’s rearing its ugly head for you, we’ve got a few fixes you can try.
Check Your WiFi
On the Destiny 2 community forum, one player commented that the cabbage error is caused by your router not working properly. While this may be true and you should check your router and consider connecting your device via ethernet to ensure your WiFi isn’t the problem, the cabbage error can affect everyone playing Destiny 2 regardless of WiFi strength.
Shut Off Destiny 2 and Power Cycle
You can also try shutting off Destiny 2 completely and trying again. I recommend power cycling your device for the best results.
To power cycle your device, shut it down completely and then pull the power cable from the outlet. Wait 15 seconds and then plug it in and boot it up. This should help resolve any withstanding issues that may have interfered and given you the cabbage error.
Wait for Bungie to Fix the Cabbage Error
Here’s the problem with Destiny 2 error codes: you usually can’t fix them. Error codes are queues to Bungie that something is broken. And the first quest in Destiny 2 Season of the Witch is, unfortunately, broken thanks to the cabbage error code that returns you to orbit.
The only fix for the Destiny 2 cabbage error code is to wait for Bungie to fix it. You can keep trying to replay whatever mission is stuck with the cabbage code to try and get lucky. However, I highly recommend visiting the Bungie Help Twitter (or X) to know that they are working on the problem.
In fact, Bungie Help has already identified an increase in currant, coconut, and centipede error codes so they are likely working to resolve the cabbage error now.
In the future, if you ever get plagued by a Destiny 2 cabbage error code, the best thing you can do is try to play a different activity and wait for Bungie to fix the error. It’s extremely unfortunate when error codes keep players from enjoying Destiny 2, but that’s the world we live in.
Regardless, I am hyped for Season of the Witch and am excited for The Final Shape. Error codes and bugs come and go, but Destiny 2 is a fun sandbox that I’ll always enjoy. I’ll just enjoy it more when Bungie fixes their game.
