Home Gaming Destiny 2 – How to fix the new Olive, Weasel, Guitar and other error codes

Destiny 2 – How to fix the new Olive, Weasel, Guitar and other error codes

4 min read


Nine times out of ten, Destiny 2 pretty much works ten out of ten times. Bungie’s space-sandbox was remarkably stable upon launch, even with its servers being hammered by the full force of over a million players at one time. That doesn’t mean that some problems haven’t slipped through. In fact, you might have been on the receiving end of a few new members of the Destiny 2 animal error hierarchy.

If you got any of the following errors, here’s what Bungie has to offer in terms of fixes:

Olive, Pony and Sheep

A holdover from the Beta days, an Olive, Pony or Sheep fix is easy enough: Restart your console with a power cycle by switching it off and back on (No standby mode here chaps) and you’ll be back in the EDZ soon enough.


Bungie says that this error might be born from testing on its side, so just exit the Destiny 2 client and try again.

Weasel and Centipede

Bungie calls these Centipede errors general networking faults when they kick a player into orbit after they inspect their gear, which may be the result of your online connection. While having a wired connection is always preferable, checking to see if your NAT is set to Type 1, 2 or 3 could be the solution here. Ideally, you want to make certain that your NAT is as open as possible, as a strict setting may be hampering your connection. Yelling at your ISP usually helps in this scenario.

As for Weasel, the Destiny sub-Reddit recommends changing your clan settings.

Mongoose error code

Apparently unique to Xbox One players, Mongoose error codes result in matchmaking for the Crucible taking longer than usual.

Guitar error code

Another general networking error that results in disconnects, Bungie has a whole host of fixes listed right here for it. Party on Wayne. Last week also saw a few other error codes pop up. You can read about them here, or you can say that I’m a nice guy because I just copied and pasted them below this sentence.

Cabbage error code

Contrary to popular belief, this isn’t the error code that pops up onto your PS4 whenever Matty shows up, but rather an annoying boot from a mission zone and back into orbit. Cabbage error codes apparently hit those players with technicolour modems rather hard, with the Bungie forums having found a solution of sorts.

A restart always helps, as does port forwarding on your main router. I’d tell you how to forward your ports, but the last time I did that I managed to set my router on fire. Have a look here though. Bungie is of course, on the case.

ce-34878-0 error code

You’ve booted up Destiny 2 and already you’re facing the toughest Raid boss yet: The PlayStation blue screen of death. Apparently a major issue on PlayStation 4 Pro consoles, here’s the method for sorting that problem via PlayStation (though it doesn’t actually work and you’ll hon4estly just be wasting your time):

  • 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.

Nightingale error code

You’re on the main menu of Destiny 2, you’re ready to rock and the screen keeps on telling you that it’s searching for updates. And then BLAM! Nightingale error. It’s a frustrating technical issue that won’t allow you to even access your character, let alone the game. So how do you fix it? Bungie has two fixes, one of which is moderate and the other…extreme. The first method involves clearing your console cache:

  • Exit Destiny and shut down your console.
  • Once your console is fully shut down, unplug the power supply from the console for at least 5 minutes.
  • Plug in and turn on your gaming console and launch Destiny.
  • Attempt to reconnect and play Destiny.

Whereas the second solution? Reinstalling Destiny 2 from scratch. Y’know, which isn’t a problem if you have South Korean internet which can grab the sequel’s near 40 gigglebyte’s worth of info back while you’re off to lunch. With that out of the way, the rest of you should be experiencing calm waters and smooth sailing.

Last Updated: September 13, 2017


  1. What is this? Error codes for a barnyard?


Leave a Reply

Your email address will not be published. Required fields are marked *

Check Also

Manchester United Sues Football Manager Over Use of their Name and Fan Mods

Manchester United, that massive global football brand whose fans are as equally annoying a…