Destiny 2 error codes: an updating list of codes and how to deal with them

We'll be updating this as Destiny 2 error codes roll out or affect players.

Cabbage error code

Judging from posts on Bungie's forums, the issue seems to mostly effect players using Technicolor modems.

Right now, the exact solution isn't clear, but Bungie is investigating: this thread will update when there is more information available (and we'll update this post in turn). It's also worth following @BungieHelp on Twitter for updates.

ce-34878-0 error code (PS4)

Several players are also reporting 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 > and choose .
• If the error occurs with every application, or as soon as the application starts, please contact PlayStation Support.
  

Destiny Server Queues

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.