Can't get to tower, every PVP game is a yeet before the game starts. This has been going on for a loooong time now for loads of players. @bungie ever going to fix it?? trying to do some quests I never did now that D2 is on a quiet period but as I can't PVP or talk to NPC's in the tower so I'm just stuck. And yes all the recommended stuff has been done (I'm wired 1GB fibre, router settings all set as per Bungo instructions etc.). Come on let me play!!! Pleeeeease
English
-
2 RepliesHello there, Thank you for reaching out. BEAVER is a Destiny networking error that means P2P matchmaking between you and other players failed, usually because of problems with NAT, your router/ISP, or Bungie’s relay network during maintenance. Try these steps in order: Full reboot of network + device Power off your console/PC. Unplug modem and router for 60 seconds, plug back in, wait until everything is fully online. Turn your console/PC back on and launch Destiny 2 again. Use wired and simplify your network If possible, connect via Ethernet, not Wi-Fi. Avoid powerline adapters, Wi-Fi extenders, or campus/office guest networks; they often cause heavy packet loss or strict NAT. Check NAT type / UPnP On your console/PC network settings, make sure NAT is Open or Moderate, not Strict. On your router: Turn UPnP ON. If you were using manual port forwarding or DMZ, remove conflicting rules and rely on UPnP first. Make sure there isn’t double NAT (modem in router mode + your own router). If there is, put one device in bridge mode. Avoid multiple Destiny consoles on the same network If more than one console/PC is running Destiny on your home network, temporarily have only one online and see if BEAVERs stop. Shared NAT/ports can trigger repeated BEAVER errors. Disable VPNs / extra filtering Turn off any VPN, custom DNS, or security software doing deep packet inspection. Use a normal home connection with your ISP’s or a standard public DNS (e.g., 8.8.8.8 / 8.8.4.4). Check for maintenance / try another network Look at @BungieHelp and the Help site to see if there’s active maintenance or known networking issues (these can cause temporary BEAVER spikes). If you can, test Destiny 2 from a different connection (friend’s house, mobile hotspot). Works there but not at home → likely your router/ISP.