Destiny Error Code Solutions: Centipede, Stingray, Bee, Urchin & More
Bungie wouldn’t be Bungie if it didn’t do things its own way, such as naming error codes by various fauna and flora. Are you getting Destiny error code Centipede? Or Stingray? Or even Beagle?! Well, thankfully there’s a solution to many of these common problems. We’ve collated these problems (and their solutions) below, so just look for the Destiny error code you’re getting and – hopefully – there’s a fix there for you. If any of these solutions don’t fix your problem – or there isn’t an error code associated with your issue – then you can head over to the Bungie Help forums to ask for more direct assistance.
Destiny Error Code: Centipede
This is one of the most common problems you’ll be getting, it seems, since Centipede is based on NAT connectivity. Bungie suggests that, first, you attempt to repeat whatever task it was that you were attempting to do. If it still doesn’t work then you’ve probably got a great connection problem. To solve this you’ll need to customise the port settings of your router to allow the necessary connection responses to Destiny’s servers to pass through unrestricted. These are the ports you’ll need to unlock: 7500-17899 (TCP) – Outbound 30000-40399 (TCP) – Outbound 35000-35099 (UDP) – Inbound and Outbound 3074 (UDP) – Inbound and Outbound If you don’t know how to unlock ports on your router, then a good site to visit is PortForward, which lists practically every router make and model with step-by-step guides on forwarding ports in your router. Alternatively you could head over to the official PlayStation or Xbox connection issues pages to find out how they suggest resolving problems. Sadly if your connection is part of a University or similarly restricted access server then there isn’t much you can do about this if your connection doesn’t allow for customised port forwarding – in this case there isn’t a solution, at least not yet.
Destiny Error Code: Pear
This problem is associated with Xbox One’s Party feature, and is an issue with synchronisation. Simply restart your Xbox One and relaunch Destiny. Hopefully that’ll fix it.
Destiny Error Code: Urchin
This error code appears due to a particular ban or restriction placed on your account. If there’s a ban in place the only resolution would be speak to Bungie to try and get the ban removed. Of course that ban might be justified, so you should check out Bungie’s rules on the matter.
Destiny Error Code: Cat
There’s a new update available for Destiny that you haven’t installed. Restart the game, download the update and try again.
Destiny Error Code: Marionberry
Marionberry is a problem associated with your network connection, often associated with a Wi-Fi blip or changed network settings on your console. Log off Destiny and turn off the console, then reset the router (turn it off for 30 seconds). You should also reset any other electronics you might have associated with providing an internet connection. Once your internet connection is up and running again, turn on your console, restart Destiny and (hopefully) it’ll be working again.
Destiny Error Codes: Blackbird, Chipmunk, Lime
Though there hasn’t been a reason provided for these error code appearing, since the solution is to reinstall the game data for the game it is likely due to some corrupted data. You’ll first need to delete the data from your console before reinstalling the data. After which, restart and the game should work as intended.
Destiny Error Codes: Buck, Camel, Cattle
This problem is encountered when you’re logged out of your account while playing the game, and can be resolved by reattempting whatever it was you wanted to do. If this fails to resolve the problem, then close down Destiny and restart the game.
Destiny Error Codes: Butterfly, Stingray
You’ll receive these error codes when you’re attempting to play Destiny while not signed into the network of the console you’re playing on, so PSN on PS4/PS3 or Xbox Live on Xbox One/Xbox 360. Reconnect to the network and retry. If you are not able to connect to the network, then you should check the network status to see if there are wider problems preventing you from connecting. You can do so here: PlayStation Network Status Xbox Live Network Status If the networks are fine, then there is a problem with your internet connection preventing you from connecting. You can create a new topic on Bungie’s Help forum to see if there is a solution.
Destiny Error Code: Chicken, Chimpanzee
This is a weird one since there’s no explicit explanation for this error code to happen, but no suggestion that it is a network connection problem either. This means it’s likely associated with an unusual bug or glitch in Destiny’s processing, so retry whatever it was you wanted to do and – failing that – restart the game.
Destiny Error Codes: Buzzard, Vulture
First off make sure you are signed into either the PSN or Xbox Live. If not, then this should resolve when you reconnect. If you are connected, however, then this is the message you’ll receive if you don’t have an Xbox Live Gold or a PlayStation Plus subscription. As is the case on consoles, you’ll need an active XBLG or PS+ subscription to play Destiny – it is an always-online game, after all.
Destiny Error Code: Bull
This is a simple error code, telling you that the current user has been signed out for a different one mid-game. You will need to exit Destiny and relaunch it for the new user (or swap back to the previous user).
Destiny Error Code: Caribou
This is an unspecified problem associated with Parental Controls on your console blocking some aspect(s) of Destiny from working. You’ll need to relax these Parental Controls on your console for it to work again.
Destiny Error Code: Beagle
Receiving this error code means there’s a problem with the data of the digital version of Destiny, and that it needs to be redownloaded and reinstalled. Here’s how you do that on PS4, PS3, Xbox 360 or Xbox One: PlayStation 4
- Highlight Destiny on your PS4 home screen
- Press the [OPTIONS] button on your controller
- Select DELETE from the menu
- Visit the PlayStation Store
- Navigate to your Library
- Select Destiny
- Select Download
- Navigate to the Games section of the XMB
- Highlight Destiny, then press the triangle button on your controller
- Select Delete
- Visit the PlayStation Store
- Navigate to your Download History
- Select Destiny
- Select Download
- Once download completes, launch Destiny from your Games List to install
- Navigate to the Settings menu on the Xbox Dashboard
- Select System
- Select Storage then Memory Unit
- Select Games and Apps
- Select Destiny, then select Delete
- Navigate to the Settings menu
- Select Download History
- Select Destiny then select Download Again
- Navigate to the My Games and Apps menu
- In the Games section, highlight Destiny
- Press the [MENU] button on your controller
- Select Uninstall
- Navigate to the Settings menu, then select Account
- Select Download History
- Highlight Destiny, then select Download Again
Destiny Error Code: Penguin
This is a PS4-only problem, and is associated with the parental controls restricting access to voice chat or messages. To resolve this problem, you’ll need to visit the PS4 manual page.
Destiny Error Code: Pelican
The problem here is that you ‘don’t have access to User Generated Content’, which might seem quite weird for Destiny. Truth be told it’s not a problem you should be encountering, and Bungie urges you to post the problem on its Help Forums for help. However it could be that some problem with the Parental Control settings of your console is affecting the way Destiny works. If you have Parental Controls activated, here’s how you can resolve the error code on PS4, PS3, Xbox One or Xbox 360.
Destiny Error Code: Carp
This problem is relevant to PS4 and Xbox One gamers, who have suspended gameplay – by exiting to the home screen for an extended period of time – and so you’ve been kicked back out to the login screen. Log in again and the problem is resolved. Hurray.
Destiny Error Code: Catfish
This simple problem isn’t one many will encounter; you can’t play Destiny without accepting the end-user agreement. Accept that and you’re good to go.
Destiny Error Codes:
Baboon, Badger, Beaver, Bee, Beetle, Blackcurrant, Blueberry, Cacao, Cashew, Cherry, Chihuahua, Chinchila, Chupacabra, Chokeberry, Duck, Elderberry, Elephant, Elk, Flamingo, Flatworm, Fly, Goat, Goose, Gooseberry, Gopher, Grape, Grapefruit, Grasshopper, Groundhog, Hare, Hawk, Jackal, Jackfruit, Jasmine, Kingfisher, Kiwi, Leech, Lemon, Leopard, Lemming, Lemur, Lion, Lionfish, Snail, Tangerine, Tamarind, Tangelo, Tapir
These are a connection general network problems, and there are no specific reasons for their appearance – nor any explicit solutions. In this case retry the same action a couple of times, if it still happens then try restarting Destiny and seeing if the problem occurs. If it does, Bungie suggests it could be caused by tests to Destiny – so you’ll just have to try again later. Failing that, attempting to resolve the router/NAT problems with port forwarding could help – take a look at the Destiny error code Centipede (above) to find out how to do this. Here’s Bungie’s official comment on these ‘general networking errors’: Bungie is actively tracking this general networking error. Your disconnect was reported the moment it occurred. If you continue to receive this error, please consider following the suggestions at bungie.net/networking