Destiny 2 error codes: Cabbage, PS4 crashes and other issues, with the latest updates and workarounds
Problems with Destiny 2? Here’s all the latest informaiton on error codes, workarounds, solutions and resolutions.
Destiny 2 seems to be pretty stable on consoles, but release has not been entirely smooth. As part of our Destiny 2 guide, we’ll be tracking these errors to keep you across the latest information that’s not so much how to get Exotic weapons or trigger Heroic Public Events but “get online and actually play”.
The error codes and reported issues below are arranged in reverse chronological order by update status, so you should always find the latest news on Destiny 2 error codes at the top of the page – and get an idea of how long your particular bugbear has gone unactioned, if you don’t have enough reasons to blow a gasket today.
Check back with this page for regular updates on Destiny 2 error codes, plus solutions and workarounds when we find them. As of the latest update, Cabbage error seems to be the most common and persistent Destiny 2 issue, followed by PS4 crashes, especially on PS4 Pro.
Cabbage error code
Destiny 2 players are enjoying healthy fibre and vitamins as they experience the Cabbage error code. The issue seems to especially affect players using Technicolor or Thompson modems.
The developer suggests the following workarounds, with the caveat “players may need to inspect the manual for their router to proceed through these steps, as some settings pages may have alternate naming conventions per manufacturer”.
- 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”.
If this doesn’t work for you, please send all the details to Bungie via its Help forum – it specifically wants to know your router hardware – version numbers and manufacturers.
The latest update from Bungie dropped on September 18 and confirmed investigations are ongoing.
Baboon, Cacao, Panther and Anteater error codes
What the heck? All of a sudden on the evening of September 14 US time Destiny 2 players reported a whole little menagerie of errors: Baboon, Panther, Anteater and, for some reason, Cocoa. Why are some of these food and other animals…? Anyway, about an hour later Bungie declared all four errors resolved.
Some PS4 players are reporting crashes in Destiny 2. We haven’t seen this ourselves despite having the console and game client running for 4 hours or longer at a stretch, but others have been unable to progress through the story as a result. As of September 10, Bungie and Sony are investigating the matter together.
Olive, Chicken, Pony and Sheep error codes
We’re not sure what the problem actually was, but all four issues were declared resolved seven hours after initial report.
Centipede error code
This error is attributed to a networking. One way to combat the issue is to use a wired connection. If that fails, change your NAT type (from Strict / Type 3 into Open / Type 1) if possible. It is one of a trio of networking error codes (see below) that new players noticed on Destiny 2’s first full weekend after launch.
Although there are several networking troubleshooting steps described in this entry and those that follow, Bungie seems to have changed something on its end, as well. As of September 9, the issue seems to be resolved.
Guitar error code
This is a general Destiny 2 networking error. Player disconnect is reported the moment of occurrence. Those who continue to receive this error should check out Bungie’s Network Troubleshooting Guide.
Weasel error code
This error occurs after a Destiny 2 player is returned to orbit during an activity or when inspecting gear. Bungie does not yet have a solution, but redditors discovered a workaround related to clan invites. If that doesn’t help, follow the same steps as you would with a “general” networking error such as Centipede.
As of September 9, the issue seems to be resolved.
Mongoose error code
Xbox One players reported longer than usual matchmaking times in Destiny 2 this week, resulting in Moongoose error notifications.
As of September 8, the issue had been resolved.
PS4 online permissions
Earlier this week, PS4 players encountered the following error message:
“You have lost connection to the Destiny 2 servers. Your permissions to access online content may have changed or your profile may have been signed in elsewhere.”
ce-34878-0 error code (PS4)
Destiny 2 players have reported a ce-34878-0 error code on PlayStation 4 Pro consoles, which is a Sony-specific code. The process for dealing with this code is as follows:
- Close the application, install the latest System Software and game updates and restart the system.
- If you have upgraded the Hard Disk Drive (“HDD”) in your system, please re-install the original HDD.
- If the error occurs again, back up your saved data, and then go to [Settings] > [Initialization] and choose [Initialize PS4].
- If the error occurs with every application, or as soon as the application starts, please contact PlayStation Support.
Destiny 2 servers at capacity
This may be an issue for some during launch period, as Destiny 2 is going to be popular. Server queues are designed to regulate the Destiny experience and to make sure that stability can be assured. The Bungie Help page notes that:
- If a player loses connection or is removed from the queue, their placement will not be retained
- If a player reaches the front of this queue and is unable to connect to Destiny servers, they will have to re-enter the queue to try again
- Queue times may vary, depending on server traffic and concurrent population
We’ll be updating with workarounds, solutions, and comments from Bungie as they come in, so bookmark this page if you want to stay on top of Destiny’s various error codes post-launch.
© 2020 - Slaying Bodies Clan