news\ Sep 7, 2017 at 9:45 am

Destiny 2: PSN, CABBAGE, NIGHTINGALE, and ce-34878-0 errors

And some shameless plugs to other articles.

Destiny 2 has launched and if you've been playing the game since then, you have probably experienced plenty of Public Events (here's how to trigger Heroic ones) and got some Exotics (how to get the Rat King). Unfortunately, the game launched with known issues.

When it comes to the PlayStation 4 issues, Bungie has released a statement saying that PSN issues should be resolved.

"Issues causing players on PlayStation 4 to receive an error indicating permissions to access online multiplayer have been resolved."

The CABBAGE error seems to remain a mystery and Bungie is continuing their investigation into it. Information gathered on forums points toward Technicolor brand modems seeing the most issues related to this error.


Limited to PS4 Pro, this error causes crashes. Some users have reported the issue having cleared up, however, Bungie released the following statement via forums:

"We are aware of reports of some PS4 Pro players encountering crashes and are working with our partners to investigate the issue. Some players have reported that turning off "Boost Mode" has reduced the frequency in which this issue occurs."


This code appears when the game cannot access the proper save files, and is tied to a corrupted cache.

To fix this, exit Destiny 2 and power down your console. Unplug it and wait for the power to cycle then plug it back in, power up, and restart the game. If that doesn't work, try completely uninstalling and reinstalling Destiny 2.


According to Bungie, this update “can be due to packet loss or disconnections between your home network and Bungie. It can be caused by certain WiFi setups, or mobile hotspots that may have experienced a blip or loss of connection.”

It is suggested you first ensure that your NAT type is open. If it is and the game still isn't working, try to switch to a wired connection (if possible) or restart your router. 

If this fails, you can always turn the console off then back on again.



Oh and here's an easy way to access the map.

1 2
About The Author
Tatiana Morris I work here, so at least I've got that going for me. Catch me on Twitter @TatiMo_GZ
In This Article
From Around The Web
blog comments powered by Disqus