Have you encountered this error while playing Destiny 2 multiplayer online? This is an issue that has been popping up for PlayStation 4 and Xbox One users alike, so it is likely that if you have spent a fair amount of time playing Destiny 2 online, then you have encountered the marionberry error code.

This article will expand on the causes of the marionberry error code and outline a few simple troubleshooting methods to resolve the issue.

What is the Marionberry Error Code?

There have been a number of online connectivity issues plaguing Destiny 2 since its initial release in 2017. The marionberry error code is essentially just another one of these issues, with users reporting the error code popping up when attempting to sign in online or even on Destiny’s character selection screen.

According to the official Bungie help article, this error code signifies a problem with your networking setup, however, this error code has also been linked to issues on Bungie’s end. The next section will detail the causes for these network issues.

Causes of the Marionberry Error Code

As mentioned in the previous section, Bungie attributes this error code to a problem with the user’s networking setup. This could contain a myriad of potential issues, such as a Wi-Fi outage, changed network settings, parental control settings, faulty router firmware, or even player to player connectivity issues.

However, this error code could also be attributed to an issue with Destiny 2’s servers. If the error code can be attributed to a networking setup issue on your end, then the issue can be easily resolved by applying the troubleshooting methods listed below. If the error code is due to Destiny 2’s faulty servers, then your best course of action is to sit tight and wait out the storm.

How to Fix the Marionberry Error Code

There is a troubleshooting method for each of the networking setup-related issues detailed in the preceding section. However, if the error code is the fault of Destiny 2’s server, then there is nothing you can do but wait it out. Now, with that out of the way, here are a few simple troubleshooting methods to resolve the marionberry error code.

1. Power Cycle Both Your Console and Your Router/Modem

If you believe the root of your issue stems from a faulty network connection on your end, the most effective first step you can take to resolve the issue is to power cycle either your console or your router/modem, preferably both. To power cycle your game console and router/modem, follow these seven steps.

  1. Close out of Destiny 2

  2. Step 1: Turn your PlayStation or Xbox completely off (do not enter rest mode).
  3. Step 2: Turn off every part of your internet network that is connected to a power outlet (router, modem, and any other devices that may be connected to the network).
  4. Step 3: Wait for 60 seconds.

  5. Step 4: One by one, turn on every part of your internet network starting with your modem (start with a router if you do not have a modem)
  6. Step 5: Once your internet network is back up and running, turn your PlayStation or Xbox back on. Launch Destiny and attempt to log in online to see if the issue has been resolved.

2. Change Your Game Console’s DNS

If the troubleshooting method listed above does not work, but you still believe that the issue stems from a faulty network connection on your end, you should change your game console’s DNS.

Users have reported their Internet Service Provider’s DNS interfering with their online connection with Destiny 2. There is a different set of steps for changing your console’s DNS depending on whether you own a PlayStation 4 or an Xbox One. 

Firstly, to change your PlayStation 4’s DNS, follow these eight steps.

  1. Navigate to ‘Settings’ and then ‘Network’.
  2. Select ‘Set up internet connection’.
  3. Select ‘Wi-Fi’ or ‘LAN’ depending on what kind of connection your PlayStation 4 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’, the ‘DNS settings’ to ‘manual’, the ‘Primary DNS’ to ‘8.8.8’, the ‘Secondary DNS’ to ‘’, the ‘MTU settings’ to ‘Automatic’, and the ‘Proxy server’ to ‘Do not use’.
  6. ‘Save’ the changes you have made.
  7. ‘Restart’ your PlayStation 4.
  8. Relaunch Destiny 2 and check to see whether the issue has been resolved.

Secondly, to change your Xbox One’s DNS, follow these nine steps.

  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 the contents of your game console’s ‘Primary DNS’ field with ‘8.8.8’ and the contents of your game console’s ‘Secondary DNS’ field with ‘’.
  8. ‘Save’ these changes and ‘restart’ your console.
  9. Relaunch Destiny 2 and check to see whether the issue has been resolved.

3. Try Other Games with Online Capabilities

Finally, if neither of these troubleshooting methods resolves your issue, it is likely that Destiny 2’s servers are to blame. To make sure that this is the case, try playing other games on your console that also have online modes or capability.

If you are able to successfully play other games online, then you can safely say that Destiny 2’s servers are to blame for the marionberry error code. In this case, the only thing you can do is sit tight and wait until their servers come back up again. Fortunately, this process typically does not take longer than an hour.

In Conclusion

Ultimately, the marionberry error code is a relatively simple fix if the cause of the issue stems from a faulty networking setup on the user’s end. If you follow the troubleshooting methods listed above, you should be able to resolve the issue in no time.