{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Recon Number 54:
9/8/2014 10:04:43 PM
12
So, the Canary error
Was this error ever addressed by Bungie? I mean, we know that it was apparently a 'connection error on my end' but when my GF is playing Destiny in the same room, on the same connection, and she doesn't have this problem, that can't be right. I was getting that error every 8 minutes on Xbox One and it was unplayable, even when there weren't two consoles running on the same connection. On 360 I had no problems. I've obviously pre-ordered for Xbox One, but I must admit I have my concerns about this error popping up again. I know that that was only a beta and issues like that are to be expected, but I'm terrified of it happening at launch. I'm just wondering if anyone had heard anything/knows anything new about it.
-
5 RepliesI remember seeing a post just after the beta ended where someone from Bungie had said that the error is being looked into - I don't know if they fixed it though. Wish they would at least let us know. I hope it's been fixed. Otherwise my money will end up going down the drain because every 5 mins I was getting thrown out of the game while playing the beta.
-
4 RepliesWell if it happens on launch it's simple.. Just return and get a new copy or get it on 360
-
12 RepliesWell I can confirm right now it's not fixed. NAT open, multiplayer connection fine, all connection tests come back fine on the console. Destiny can't stay connected for more than five minutes.
-
3 RepliesDoes this error mean the game is broke and I can not play it as I have brought it on digital and cannot play it cheers for any Feed back
-
9 RepliesI'm experiencing it right now, everything else is working on my connection and it worked from 2am till 7am before I took a break and came back to the error. Anyone else have a similar situation?
-
3 RepliesI got my Limited edition in the mail from Amazon around 9:00am PST... I installed, and I never got passed the start screen... immediately gives me canary error... I tried uninstalling/reinstalling, I tried the Hard Reboot, Reset router/modem, tried setting my WiFi down to 54mbps, NOTHING works!!!! IDK what else to do! My NAT is open, and both Internet and Multiplayer connection are good... HELP!?
-
I even had this problem in Beta it's ridiculous
-
3 RepliesThis error simply means Network issue on your side.
-
***Hasnt worked with mine but may work with you, i spoke to Xbox (microsoft)**** If this doesnt work they basically said its because bungie servers cant handle so many people on it.... GTA V all over again... You are now chatting with 'Steef' Steef: Hello, thank you for contacting Xbox Customer Support. My name is Steef. Please give me a moment to review your question. Steef: Hi! Am I chatting with Josh? Steef: Is this your GamerTag? Silent Eskimo josh: It tis indeed. Steef: Cool. Thanks. Steef: Josh, first I want to know the download speed and the latency your console is getting. Steef: On your console, please go to Settings >> Network >> Detailed Network Statistics josh: Its just running test now... Steef: Alright. josh: 72.13 Mbps Download 162ms Latency 6.03 Mbps Upload Steef: Great results actually. [b]Steef: What's the NAT type showing? Steef: Is it open or moderate? josh: Open, ive opened the ports bungie requested, Steef: Good. josh: *also Steef: What about the ports required for Xbox One? Steef: These. Steef: •Port 88 (UDP) Steef: •Port 3074 (UDP and TCP) Steef: •Port 53 (UDP and TCP) Steef: •Port 80 (TCP) Steef: •Port 500 (UDP) Steef: •UDP Port 3544 (UDP) Steef: •UDP Port 4500 (UDP) Steef: Have you added them on your router before? Steef: Josh, Destiny is quite a heavy game, Bungie has generated some ports for a home router to connect to their server, this does not stop there. Microsoft also has ports for Xbox One need to be open for games like this. Steef: This will allow heavy internet packets to go through in and out the router, also to connect multi-player on Xbox Live. Steef: Basically, you just have to access your router interface on your PC, under port forwarding add the following ports I have just sent. josh: im on it now, Do i need an end port or am i just opening the start port Steef: It must be start and end ports, Josh. :) Steef: I'm glad to know you are knowledgeable on this, sadly not all members are good at this. josh: haha i could imagine, ive studied a little in system support little websign and little networking but tbh have done it for while, so the ports you sent me before I.e "Port 88 (UDP)" is that both the start + end port? josh: havent** Steef: Cool. Steef: Yes, that's correct. josh: So ive put "Start port: 88" / "End port:88" Steef: Good.[/b] Steef: Once you're with all seven ports, save it and let me know when you're done. josh: Done them :) Steef: Great! Steef: Josh, after saving the changes it is advised to reboot your router and the console. I'm afraid this will disconnect our chat session if the PC you're using is connected to the same network. Steef: Let me know if you have further questions. josh: Cheers thats great Steef: Thank you josh: you too, enjoy rest your shift.
-
1 ReplyMine still hasnt been fixed.
-
2 RepliesHey I am hit, too. XOne with permanent Canary errors. And it really starts to kick me off... Since Tuesday I have the same effect over and over and over again. No session longer than 10 minutes. Sometimes instant disconnects, sometimes after 10 minutes of fluent, wonderful gaming. I tried two routers by now, did everything stated in forums, on the help page, NAT, static, opening up everything, it just disconnects again and again and again, while everything else runs perfectly, no matter if Tablet, Mobile, Laptop or 360 or PS3. This by far just doesn't look like a "client" error anymore and annoys heavily. Please please please get around this somehow. If it is really the solution to hack something on the routers I am sorry for people that don't have any insights, but so far even that did not proof 100% for me, at all. Right now the situation is plain horrible, unplayable, and for such a game... sorry. I was more happy with Diablo IIIs errors, there I couldn't play AT ALL ^^' Maybe that would be better. Cheers
-
I was having same problem but been fine since update
