JavaScript is required to use Bungie.net

Service Alert
We are actively investigating issues impacting players' ability to sign in to all Destiny releases on Xbox Platforms. Until resolved, players may experience disconnects or be unable to sign in. Please stay tuned to @BungieHelp for updates.

Help

Help us help you.
10/4/2023 6:01:04 AM
2

Constant „Cabbage“ Error [with detailed information about Setup/Hardware/tried solutions]

Dear Bungie, I‘m aware about the ongoing DDoS attacks and the resulting Server issues. Until 26.09.2023 i was able to play Destiny 2 without any big problems, but since update 7.2.0.5 dropped 1 1/2 weeks ago i get constant „cabbage“ errors like other players. The login and character selection works fast and without any issue. When i‘m in orbit I can’t get to a destination. I see the animation that my ship flies to the selected destination but after a short blackscreen I’m back in orbit with „cabbage“ error. I was hoping, that yesterdays update 7.2.0.6 would maybe fix this problem, but it wasn’t the case. I got only „cabbage“ errors, no other errors appeared. Other online activities and other online games work without any problems. Some details about my setup: Region: Germany, Northrhein Westphalia ISP: Deutsche Telekom (German Telekom) with dynamic IPv4/IPv6 addresses (Dual stack, NOT Dual Stack lite) Speed: 250 MBit down / 50 MBit up Hardware: - Zyxel VMG3006-D70A DSL Modem - pfSense Firewall as Router - Wired(!) connection to PlayStation 5 My Setup hasn’t changed over the last year and it worked like a charm. As described above, I had no major problems playing Destiny 2 until the day in question. It worked in what felt like 99.9% of all cases. Since Destiny 2 does not work, I have tried to rule out errors on my part. But I came to the conclusion that everything works from my side. Things I’ve done: - checked every device for Software updates - I have gone through your help pages - NAT2 on PSN - Checked firewall logs (nothing is blocked) - Made sure there is no packet loss on my connection - UPnP for PlayStation is enabled and working - Instead of UPnP put the PS5 as exposed host/DMZ - Double-checked open ports - Tried my old Router (AVM Fritz!Box 7590) - Cleared the Cache of my PS5 - Reinstalled Destiny 2 on PS5 - Disconnected my DSL Modem to receive new IPv4 and IPv6 addresses. All the attempts didn‘t bring any improvement. It remained with the "cabbage" error. As a last resort I routed all the traffic of the PlayStation 5 through a VPN (to a Server in Sweden). What should I say…. It worked… okay… unfortunately via VPN I’ve got a NAT3 connection. Anyway „cabbage“ error dissappeard and I was able to land and play on different destinations without any problems. !!This is of course only a temporary solution for me!! I read that user „bailongma2008“ has experienced the same via VPN in this thread. https://www.bungie.net/de/Forums/Post/263339318?sort=0&page=0&path=1 If you have any other ideas apart from your support pages for troubleshooting on my part... I'm very interested. I hope you can quickly find the problems and hope that you can help us, the players, quickly. Furthermore, I wish you all the best and hope that you get the DDoS attack quickly under control.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Hello, Thanks for reporting and sharing with us the steps you tried to resolve this issue. [quote]We are continuing to investigate ongoing reports of error codes in Destiny 2. Please stay tuned to @BungieHelp for further updates.[/quote] https://x.com/BungieHelp/status/1706458729078759474?s=20

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon