How to Fix Destiny 2 Error Code Cabbage (Connection Blocked)

By FixMyError · Updated October 17, 2026 · 6 min read

What Error Code Cabbage means

Error code Cabbage is one of Destiny 2's signature network errors, and it always arrives at the worst possible moment: you are loading into a destination, a strike, or a raid, and instead of the activity you get a small CABBAGE error message and a one-way ticket back to orbit with a prompt to try again. Sometimes it strikes mid-activity too, cutting the session off without warning.

Bungie's official help page gives the cause in one sentence: CABBAGE may occur when your router's settings block communications to or from Destiny services. That makes it different from most other Destiny 2 errors, which can be triggered by the game servers themselves. Cabbage points squarely at your home network. Your router, its firewall profile, or the way your devices are chained together is stopping the game's traffic from reaching Bungie, and the game has no choice but to drop you.

Certain hardware is famous for it. Technicolor and Thomson routers — the kind many internet providers hand out — ship with strict security profiles and a background feature called an application layer gateway, or ALG. Specifically, a helper named CONE(UDP) is bound to UDP port 3074, the same port Destiny 2 uses for its traffic. That helper misreads the game's UDP packets as something suspicious, the packets get mangled or dropped, and Cabbage appears. Players on these routers often find the error is completely consistent: it happens every session, in the same places, until the router settings change.

The reassuring part is that nothing is wrong with your account or your game installation. Cabbage is not a ban, not a corrupted file, and not a deleted character. Your Guardians, weapons, and seasonal progress all live on Bungie's servers, untouched. The fix is entirely about the path your traffic takes from your console or PC to those servers, which is why every step below starts at your router.

Common causes

• Router firewall or Extended Security blocking Destiny traffic: strict firewall profiles on your router flag the game's UDP packets as suspicious and quietly drop them, which Bungie identifies as the main trigger for Cabbage.
• A second router chained behind your main router: playing through a router that is itself connected to another router (or an extender running in router mode) doubles the NAT layers and breaks the game's connection handshake.
• UPnP disabled or bad Game and Application Sharing rules: without UPnP enabled, Destiny 2 cannot open the ports it needs, and leftover assigned-application rules can conflict with the game's traffic.
• The Technicolor/Thomson CONE(UDP) helper: the ALG helper bound to UDP port 3074 on these routers interferes directly with Destiny 2's connection, producing Cabbage even when every other setting looks fine.
• ISP-level filtering or outdated firmware and drivers: an ISP-side firewall, old router firmware, or outdated network adapter drivers on PC can all contribute to blocked or unstable traffic to Bungie's servers.

How to fix Error Code Cabbage — step by step

Work through these fixes in order. Cabbage is a router problem, not a game problem, so the steps that touch your router settings are the ones most likely to end it for good.

1. Check Bungie's server status first Before touching your router, rule out a Bungie-side problem. Open the Bungie Help status page or the @BungieHelp account on X and look for maintenance notices, background updates, or a known outage. Connection errors spike during scheduled maintenance and major content drops, and when that is the cause, no router change will help. If maintenance is announced, log out and wait until Bungie confirms the servers are stable again before working through the steps below.
2. Connect directly to your main router Bungie's official guidance for Cabbage says to connect your console or PC directly to the router that is linked to your modem, not to a second router chained behind it. If you are running a router plugged into another router, an extender in router mode, or a second Wi-Fi box, unplug that middle device and connect your gaming device straight to the main router. A wired Ethernet cable is best for the test session because it removes Wi-Fi instability from the equation.
3. Create a custom firewall profile in your router settings Log in to your router's admin page, usually at an address like 192.168.0.1 or 192.168.1.1, using the credentials printed on the router or in its manual. On Technicolor or Thomson models, go to Home, then Toolbox, then Firewall. Create a new firewall level and give it a name like Destiny 2 so you can recognize it. Menu names differ by manufacturer, so check your router's manual for the exact path if the labels do not match.
4. Enable UPnP and loosen Game and Application Sharing In the router settings, find the Game and Application Sharing section (on Technicolor or Thomson routers it sits under Home, then Toolbox). Enable UPnP so Destiny 2 can open the ports it needs automatically. Turn off Extended Security, and disable or clear any Assigned Games and Applications entries tied to Destiny. These strict rules are the most common reason the router blocks the game's traffic, so loosening them usually clears the error. Save your changes.
5. Power-cycle your router and modem Unplug both your router and your modem from power. Leave them unplugged for at least 60 seconds, then plug the modem back in first and wait until its connection lights are steady. Plug the router back in next and give it a minute to finish booting. Relaunch Destiny 2 and try loading into a destination or activity to see whether Cabbage still appears.
6. Fix the CONE(UDP) helper on Technicolor or Thomson routers If you own a Technicolor or Thomson router and the error persists, the culprit may be the router's application layer gateway: a CONE(UDP) helper bound to UDP port 3074 that interferes with Destiny 2's connection. If your router allows telnet or SSH access, connect to it, run connection bindlist to see which helpers are bound to which ports, then run connection unbind application=CONE(UDP) port=3074. Note that many ISP-issued routers lock the command line, so if you cannot get in, call your ISP's support line and ask them to unbind the CONE(UDP) helper from port 3074 for you.
7. Update router firmware and network drivers Outdated software on either end of the connection can keep the problem alive. Check your router's admin page for a firmware update and install it if one is available. On PC, open Device Manager, expand Network adapters, right-click your adapter, and choose Update driver. As a quick test, try playing over a mobile hotspot or a different network for a few minutes: if Cabbage disappears there, you have confirmed the issue lives in your home router and can focus your troubleshooting on it.

Did this fix it? Quick checklist

• You can load into destinations and activities without a CABBAGE error
• UPnP is enabled and the router's Extended Security setting is off
• Your console or PC connects directly to the main router, not through a second router
• Bungie's status page shows no active maintenance or outage

If Cabbage keeps coming back, double-check that no leftover port-forwarding rules or DMZ settings from other games are interfering with port 3074, and confirm your NAT type shows as Open in your console's network settings. As a last resort, a factory reset of the router (reconfiguring from scratch afterward) clears any hidden rule that the menus do not show — but save that for after the steps above, since it wipes every device's settings on your network.