Fix: Destiny Error Code Marionberry

Destiny is a multiplayer action role-playing game developed for the Xbox and PlayStation with a ton of first-person shooter elements baked into it. Destiny has been one of the most commonly played multiplayer games ever since it was released back in 2014. As stated before, Destiny is a multiplayer game – that being the case, Destiny requires players to be connected to the internet in order to enjoy the multiplayer spectrum of the game. An array of Destiny players have reported seeing error code Marionberry when they launch Destiny and attempt to sign in. Some players affected by this issue can’t even get to Destiny’s character selection screen and are instead just stuck with error code Marionberry. Error code Marionberry comes with an error message that reads:

“Could not connect to the Destiny servers. Please try again later. For more information, visit help.bungie.net and search for error code:  marionberry”

Okay so here’s what the error message tells us about error code Marionberry: the error code was caused by your console not being able to connect with Destiny’s servers. This means that the culprit is either some part of your internet connection or the Destiny servers themselves. The following are the absolute most effective solutions that you can use to get rid of error code Marionberry and successfully sign in and play Destiny online:

Solution 1: Power cycle both your console and your router/modem

Your modem/router is responsible for your entire internet network, so power cycling both it and your game console should eliminate any temporary hindrances that were somehow causing you to see error code Marionberry every time you tried to play Destiny online. To power cycle your game console and router, you need to:

1. Close Destiny.
2. Turn your PlayStation or Xbox off.
3. Turn off every part of your internet network that is connected to a power outlet (your router, modem and any other devices on the network).
4. Wait for 60 seconds.
5. One by one, turn on every part of your internet network starting with your modem (or your router, if you don’t have a modem).
6. Once you have your internet network back up, turn your PlayStation or Xbox on.
7. Launch Destiny and try to get online to see whether or not the problem has been resolved.
   Note: PowerCycling often gets rid of the corrupt cache for both Xbox One and PS4. Since PS4 and Xbox One don’t have dedicated folders that contain their game cache, it is usually just cleared after power-cycling the console.

Solution 2: Change your game console’s DNS

Your Internet Service Provider’s DNS can also cause you to run into error code Marionberry whenever you try to get online on Destiny. If that’s the case, simply changing your  DNS to a different one should be enough to get you signed in, back online and kicking butt. In almost all cases, Google’s DNS works like a charm and manages to get rid of the problem. To change your game console’s DNS, you need to:

On the PlayStation 4:

1. Go to Settings > Network.
2. Select Set up internet connection.
3. Select Wi-Fi or LAN depending on what kind of connection your PS4 uses to connect to the internet.
4. Select Custom.
5. Set the IP address settings to Automatic, the DHCP host name to Do not specify, DNS settings to manual, Primary DNS to 8.8.8, Secondary DNS to 8.8.4.4, MTU settings to Automatic, and Proxy server to Do not use.
6. Save the changes you have made.
7. Restart your PS4.
8. Check to see whether or not the issue has been fixed when the console boots up.

On the Xbox One:

1. Navigate to your console’s Home screen.
2. Press the Menu button on your controller.
3. Select Settings.
4. Select Network.
5. Select Advanced settings.
6. Highlight and select DNS settings.
7. Replace whatever is in your game console’s Primary DNS field with 8.8.8 and whatever is in its Secondary DNS field with 8.8.4.4.
8. Save the changes and restart the console.
9. Check to see whether or not the issue has been fixed when the console boots up.

Note: If Google’s DNS turns out to, for some reason, not work for you, you can simply use OpenDNS instead. The Primary DNS for OpenDNS is 208.67.222.222, and the Secondary DNS for OpenDNS is 208.67.220.220.

Solution 3: Wait out the storm

If neither Solution 1 nor Solution 2 worked for you, chances are the problem simply isn’t on your end and Destiny’s servers are simply down for all or a portion of the game’s player base for the time being. An excellent indicator of this would be whether or not you can get online while playing titles other than Destiny on your game console. If it turns out that you’re getting error code Marionberry simply because Destiny’s servers are down, all you can really do is patiently wait for the servers to come back up again so you can jump back into action and play some Destiny.