How to fix error code Cabbage in Destiny 2

Destiny 2 Season of the Witch
Credit: Bungie

Destiny 2 Season of the Witch
Credit: Bungie
Players have reported on 19 September a spike in Cabbage errors in Destiny 2. Here is our solution.

Destiny 2 Season of the Witch is finally here, bringing a ton of new stuff to the game, including a brand-new artifact with mods and perks to customise your builds. Still, fans are hoping to learn how to fix error code Cabbage since it's preventing them from logging in.

There are plenty of error codes in Destiny 2, especially popping up when a new season drops as players clog the servers. Error code Cabbage is no different.

If you're looking for solutions, why the error code is showing up, and more, we got you covered. Let's help you figure out how to solve error code Cabbage in Destiny 2.

Error code Cabbage in Destiny 2 - How to fix

Error code Cabbage is described by Bungie as the following:

Error code CABBAGE may occur when router settings block communications to or from Destiny services. We are investigating the impact on various devices. To attempt to resolve this error when using a Technicolor/Thomson router, please proceed through the following steps.

According to Bungie, these are some potential solutions you should look into:

Connect your console directly to the router via Wired or Wi-Fi Connection.

  • Note: attempting to connect to Destiny through a router connected to an alternate router may lead to increased issues. Please attempt to connect to the router connected to your modem for best results.

From the router settings page, proceed from Home > Toolbox > Firewall.

  • Create a new Firewall level within your Router settings.
  • Players may wish to name this "Destiny 2".

From the Router settings page, proceed from Home > Toolbox > Game & Application Sharing and configure the following settings:

  • Enable UPnP.
  • Disable "Extended Security".
  • Disable any "Assigned Games & Applications" settings.

Other than that, there's not a lot much that can be done on your end. So it's all up to Bungie to fix the issue.

And that's it! For more content, check out our picks for best PvE weapons in Destiny 2.