[b]**EDIT: Made note of Finelicker's solution**[/b] As of [b]0545 25 July 14[/b] Bungie time, it seems like two versions of Canary. 1) the first version is that you cannot connect to the servers at all. This version won't let you move into character creation and you're stuck just past the start screen. A fix for many people is to do a hard reboot of the Xbox One (hold down the power button for 15 seconds, the console shuts down, wait for a minute then start back up). If it still persists, repeat and unplug your console for a min, then start back up. This should resolve Canary. 2) The second version appears to revolve around a particular modem/router. The system allows you to start a game and right before you get to a checkpoint, Canary shows up. [b]Finelicker[/b] has a solution here: [quote]I've had the widely reported problem with the game disconnecting after 10 minutes (VIRGIN SUPERHUB 2) with the canary error. I've tried everything advised but nothings worked so far, apart from the following. I've been playing for several hours no with not one problem or diconnect. Go to your xbox 1 network settings and establish which of the two networks you're on. (either the 5ghz or the 2.4 one) The go to your PC browser and login to your router settings 192.168.0.1 (password by default is changme) Go to advanced settings then select Wireless radio you'll then see three speed options for each bandwidth, the 2.4ghz and the 5ghz. My xbox one was on the 5ghx channel with the speed set to 450mbs, I selected the 54mbs option and applied and saved. Your xbox will then disconnect and re connect to the network as your router applies the settings. Once done, happy gaming :)[/quote] Alternatively [b]Bambusbieger[/b] suggested the following: [quote]As soon as the error message pops up (right after starting the game in my case), press the Xbox home button and head over to the network settings. Run the multiplayer test and wait for it to finish. Press A, return to the homescreen and close Destiny. Wait a couple of seconds, then launch it again. There error message should be gone now.[/quote] NathanLHD's thread (the one you're reading now) is the main thread for solutions so keep reading here if you have more issues. We are still investigating the issues but for now these are the fixes available. Hopefully this works. Hats off to Fine and Bam for solutions, to Nathan for keeping this thread going and for I Pye for pointing me towards Fine's solution. Get the word out so we can be Legends together. See you starside. JTS