Hello everyone!
Posting here as a last resort after Bungie support redirected me to the forum, and my ISP said the problem is on Bungie's side. I'm hoping someone with technical knowledge or similar experience can point me in the right direction.
TL;DR
I'm locked out of both Destiny 1 (MARIONBERRY error) and Destiny 2 (CABBAGE error) from Ukraine. The issue reproduces on 2 different PS5 consoles, 2 different PSN accounts, and 4 different network paths, but friends in the Czech Republic and Portugal play both games without issues on the same days.
Marathon seems to work fine on the exact same connection, though I am not sure whether it will stop working eventually. I've done and documented all standard troubleshooting below.
Setup
- Platform: PlayStation 5 (Destiny 1 - PS4 version, D2 native)
- Router: Asus RT-AX57, stock firmware, latest version available.
- Started: Sunday, September 13, 2026. Worked fine before; no changes on my end.
Errors:
- Destiny 1: MARIONBERRY immediately after the "Signing in → Preparing" screen.
Never reaches the character select.
- Destiny 2: created character successfully, then CABBAGE on login attempt and back to character select.
- Marathon: works fine for now.
Here are some things I've already tested.
Router/network:
- Full power cycle described in the help article (30+ min off)
- UPnP toggled both ways
- DNS changed to 8.8.8.8 / 1.1.1.1 and multiple others, including DNS4EU
- Both wired Ethernet and Wi-Fi 5GHz
- NAT Type 2 (Moderate) confirmed
- Console placed in DMZ — no effect
- Router firmware is the latest available for the model
- Trend Micro / AiProtection is disabled
- No CGNAT
- Tracert to bungie.net completes in 4 hops with no packet loss
Console/account:
- Tested on TWO different PS5 consoles — same errors on both
- Tested on TWO different PSN accounts — same errors on both
- Deleted and reinstalled Destiny 1 completely
- PS5 system software up to date
- Date/time correct and auto-synced
- Cleared console cache
- Rebuilt database
- Bungie.net web works perfectly — profile, clan, PSN link all visible
- Other online games work fine (tested with The Division 2, Marathon — full matchmaking
and gameplay work)
Different network paths tested:
- Home wired: MARIONBERRY / CABBAGE
- Home Wi-Fi: MARIONBERRY / CABBAGE
- Mobile hotspot (LTE): initial connection works, but kicks to orbit on
every activity load — different symptom, same practical result
- VPN via PC (Mullvad, Warsaw exit) shared to PS5 via Wi-Fi hotspot
- VPN via router (AIirVPN, Germany exit): MARIONBERRY
- VPN via router (AIirVPN, UK exit): MARIONBERRY
Friends in the Czech Republic and Portugal can play the game fine. Marathon seems to be working fine on my end, but not Destiny.
My ISP says everything works fine and that they haven't applied any restrictions on their side. The support team wasn't helpful in pinpointing the cause, so I am writing here as a last resort.
At this point, I've exhausted everything I can test from my end. Any help is greatly appreciated.
-
1 ReplyBump to be noticed ....
-
3 RepliesEdited by BNGHelp8: 9/18/2026 4:30:26 PMHello there, Thank you for your detailed report. We understand you're experiencing persistent Cabbage and Marionberry error codes. We're sorry to hear of this, as we can imagine how this would cause concern. By any chance, do these error codes persist if you sign in with a different game account than those which you normally play with? Also, did you recently link a Discord account? Please let us know the above information when you can, and we'll review.