{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
6/9/2020 7:12:39 PM
13
Error code chicken, Constant contacting D2 Servers
Error code chicken, Constant contacting D2 Servers
-
[quote]Error code chicken, Constant contacting D2 Servers[/quote] Same exact thing here. It’s happening for me and my friend. It’s an on/off thing. One day it’s good the other day it’s chicken error spam.
-
I did all of Bungie’s suggestions and the error is still there (and all my progress is probably lost after initializing my PS4).
-
Yeah me too, deleted and reinstalled twice so far, only get past shadowkeep screen then its just constant loading and eventually hits out with chicken error message. Have followed all steps and its definitely not a problem on my end
-
let's get this back to the top of the forum, this really needs some attention
-
I get this every time since the update
-
Having the same issue, trying to log in but constant chicken codes. Followed the guide suggested, and it didn't help. Not having any issues with anything else on the internet either, just Destiny. Anyone find a fix?
-
1 Reply[quote]Error code chicken, Constant contacting D2 Servers[/quote] Same got a cloudberry error code while playing crucible and then constant contacting D2 server
-
11 RepliesHi there, Thanks for reaching out. Please refer to our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]network guide[/url], [url=https://www.bungie.net/en/Support/Troubleshoot?oid=13603]optimization guide[/url], and [url=https://www.bungie.net/en/Support/Troubleshoot?oid=13610]advanced troubleshooting[/url] for assistance on minimizing connection issues and best optimizing your connection to Destiny 2.
-
Same. It also kicks me off with a "pardon our dust" message every now and then as if the maintenance is still going. Been playing right before the update and everything was a-ok then.
-
1 ReplySame here.
-
same here .... worked fine before the update.
-
Same here
