{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/19/2023 5:10:50 PM
17
Destiny 1 error code: marionberry
As of 10/19/23 D1 players are not able to login to their account due to error code: marionberry. I’m not sure if bungie is aware if this issue, so make your voice be heard. Thank you!
English
#Help
-
And the marionberry code returns for another week :( How can you "fix" it if it still comes back?
-
18 RepliesHi there, Thanks for your report. We're currently investigating this issue. What specific platform are you playing on?
-
Bungie fix D1 please.
-
I has the same error in my ps5. I need Somebody help When its fixed. I'm Looking for a clan I want to play crucible and assault
-
The issues with D1 servers are now lasting at least 30h! The only reaction was the question of @BNGHelp7. No statement - Nothing! As we now know that at least all Xbox and PlayStation platforms are affected. No one of my friends list (PS4/PS5) almost all over the world is able to connect to the D1 server. - I assume D1 servers are dead. .....and you (Bungie) are trying to tell us, that you don't notice if your servers are empty, nobody is playing Destiny or your servers are down? .....and you have to ask your customers on which platform they are trying to connect to your dead server? What kind of business are you running there? My desire to start anything again labeled with Bungie is rapidly approaching 0.
-
1 ReplyI can't connect to Destiny 1, solid marionberry error code. Help please?
-
Edited by Trip: 10/20/2023 2:56:13 PMDefinitely something their end. Have reset internet and series x console and still same error
-
Been getting it for the past couple of days. It's a real pain because I was in the middle of streaming an OG story run with people. Feels like a constant DDOS attack similar to what Titanfall 2 had a while back
-
Same here on Series X and One X
-
Same issue for the past few hours on PS4, Destiny 1. Power cycled router, modem, and PS4. Updated firmware on router, power cycled again. Consistent code marionberry throughout. All other games and internet services work as normal.
-
Let's see what Bungle do when I ask for a refund on the £50 I recently paid to get back in to D1. 24 hrs of "their" server/s being down /unavailable is not good enough especially when they try (vainly) to deflect the problem back to me. I'll give them another 24hrs and then not only am I going to request a refund of my £50 spent on D1 but also the money I paid for D2 The Final Shape.
-
Same here on Series X. I've done all the necessary troubleshooting and even had a tech check the router says everything is fine with my connection. Please fix!!!
-
This is happening to everyone trying to log in to destiny 1. I've played this game since 2014 and have literally invested 1k+ over the years on Destiny One. Bungie always wants to blame the user network. It's their server issue and it needs a permanent resolution from their end. Fix it or send me a nice fat refund check.
-
Hey! This happened to me!
-
Neither, issues for around 20 hours now almost.
-
Same here, can't log in due to Marionberry.
