There’s no shortage of quality free-to-play games whether you’re playing on a console, PC or even a smartphone. These games aren’t always perfect and run into bugs and glitches from time to time.
This article discusses the Centipede error code in Destiny 2, its causes, and how you can fix the problem.
What causes this issue?
The error is mainly caused by connectivity issues on the user’s end. Some common causes include:
- Loss of connection or dropped packets.
- Strict NAT type.
- Issues with the ISP.
Also read: How to fix error code Calabrese in Destiny 2?
How to fix this?
Here are five fixes you can try out.
Restart your router
Restarting your router can help eliminate any unseen network or connectivity issues you may face. You have to turn off your router, wait a bit, and then turn it back on again.Â
Try ethernet
As convenient as it might be, WiFi can sometimes be unstable, especially when playing online games. So instead, try a wired connection between your router and PC or console to see if that solves your problem.
Also read: How to fix BC 153 error code?
Change NAT type
If your router has a NAT type 3, otherwise called strict, you will run into problems with a game, as strict NAT types often block internet traffic to non-essential programs. If you have admin access to your network, try changing the NAT type to see if that resolves your error.
Check out our detailed guide on how to change NAT type on consoles here.
Disable VPN
If you’re using a VPN while gaming, some games can experience issues due to geo-restricted content policies. Disable it and try rerunning the game if you’re on a VPN. It should work just fine. The same goes for any firewalls you might have as well.Â
Verify Game Files
Corrupted game files can often lead to issues like this, not just in Destiny 2 but other games. Luckily, Steam has a built-in feature that verifies your game files and reinstalls any files that might be damaged. Follow these steps.
Step 1: Head over to your Steam Library, right-click on Destiny 2 and select Properties.
Step 2: Head over to the Local Files tab.
Step 3: Click on Verify integrity of local files… and let Steam do its thing.
Now try relaunching the game.Â
Also read: How much time have I wasted on Destiny and Destiny 2?
