Ever since the release of Destiny 2 for PC I have had this cabbage error code come up throughout the initial mission. I thought it was just a simple bug that would be fixed throughout the week. The beta had shown me that after the initial mission I would be able to play normally, and I did randomly connect one day and complete it, but it still stops me from continuing. No one spawns in the farm and no assets of the mission are shown. I have not been able to reach level 2 after all this time. I read the help forums regarding the router settings, which I can not do because of it being a college ISP. After realizing that the error would not have a fix soon, I went home with my computer to attempt to play on a different ISP and router type but the cabbage continues to pursue me, even after messing with my router's settings as Bungie and others in the community have suggested. I do not understand how the game is denying any connection from my computer after trying vpns, hotspots, different access points, wired connection, wireless connection, etc. I would not want to refund the game even if I could because of the enjoyment I had with friends on the first one. If there is any kind of workaround that I have not tried and does not require access to the router/router firewall settings, then please enlighten me.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.