In Destiny 1 whenever launching to the Tower or other space (Iron Temple), the game boots me out with a Beaver error, this is so strange as I can launch strikes, patrol zones on all the planets, yet I can't get to the tower at all, this has been happening now for the last few days, and no it is not the network it is something with the game, as if it was network then strikes and patrol zones would be doing the same, also so would Destiny 2, but no, just the Social Space in Destiny 1.
						
					
					
				- 
   
	Hello there, Thank you very much for reaching out to us. I'm sorry to hear that you are seeing this error code specifically in the Tower in Destiny 2. This error code is generally seen when there are issues connecting with other players, specifically. To help further with this, we'd recommend going through our [url=https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide]Basic Network Troubleshooting[/url] if you haven't already, along with, more importantly, our [url=https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types]Advanced Network Troubleshooting Guide[/url] to rule out any NAT-related issues.
 
										 
					 
		    