Destiny 2, a renowned looter shooter by Bungie, faces occasional bugs like the error Centipede, mainly on PC. While it might affect consoles with different titles, the error generally stems from networking issues. Bungie’s guide highlights network restrictions or server problems as potential causes, often related to NAT type or regional server issues.
Before we get into the complicated stuff, try these easy fixes first:
- Use a VPN for secure connections.
- Upgrade internet speed if necessary.
To resolve Error Code Centipede in Destiny 2 on PC, consider the following steps:
- Check Bungie’s Maintenance List.
- Switch from NAT Type 3 to NAT Type 1 or 2.
- Enable Port Forwarding for Destiny 2.
Evaluate The Server Status
Multiplayer games like Destiny 2 rely on Bungie’s backend servers for smooth operations. Bungie maintains an updated Maintenance List, informing players about server downtimes and addressing issues in patch notes post-maintenance.
Centipede errors are often linked to server problems according to Reddit and Official Forums. If servers are offline, the error will appear on Destiny 2’s login screen. Following Bungie Support on Twitter provides real-time updates on maintenance procedures.
Switching From Nat Type 3 To Nat Type 1
Now the most crucial steps of fixing the error code, as listed accordingly from Bungie’s website for Destiny 2, revolves around switching some of your internet connection properties. It is called the Network Address Translation (NAT), which in layman’s terms can be described as a bridge or internal link between connecting your system’s IP address with the game’s backend servers. It has a total of three kinds:
- Nat Type 1 (Open)
- Nat Type 2 (Moderate)
- Nat Type 3 (Restricted)
To resolve Destiny 2’s Centipede error, adjust your router settings for Port Forwarding and switch to a Moderate or Open Nat Type, ensuring it’s not Nat Type 3. Contact your ISP for assistance or follow these steps to manage it independently.
- Press Windows + R > type ‘CMD,’ > run it.
- In the Command Box > enter “ipconfig /all” > press Enter to find your IPv4 Address, Subnet Mask, Default Gateway, > DNS Servers information for later use.
Next up is assigning the static IP to get a secure connection of your System to your internet router or modem and remove the Nat Type 3 from your PC, which is covered in the following step-by-step procedure:
- Press Windows + R.
- Type “ncpa.cpl” > press Enter.
- Choose your current Network connection.
- Click on Properties.
- In the Network Connections menu (ncpa.cpl) > locate your connection > choose Properties.
- Click on “Internet Protocol Version 4 (TCP/IPv4)” > select Properties.
- Choose “Use the following IP Address”.
- Input the IP address, Subnet mask, Default gateway, and DNS servers obtained earlier.
Click on OK to apply the changes that you made, and then head back into Destiny 2 to verify if it fixed the error code.
Port Forwarding Destiny 2
If even adding a static IP didn’t do the job, you can further add another ray of hope of connecting to the Bungie servers of Destiny 2 to resolve the error code.
It essentially involves heading into your router settings manually and setting up various port numbers from two different port destinations: TCP & UDP. Just keep in mind that the router menu may differ for everyone, so here is how you can enable ports in Destiny 2:
- Access router settings using the Default Gateway IP address.
- Log in with ISP-provided credentials.
- Find the Port Forwarding menu.
- Enter Static IP if required.
- Input TCP and UDP port numbers for Destiny 2 (PC version).
TCP: 80, 443, 1119-1120, 3074, 3724, 4000, 6112-6114, 7500-7509, 30000-30009 UDP: 80, 443, 1119-1120, 3074, 3097-3196, 3724, 4000, 6112-6114, 27015-27200
So using this method should ultimately fix any network issues with your internet connection as well as remove any presence of NAT type 3 from your system.
Winding Up Destiny 2 Centipede Error Guide
The Centipede error in Destiny 2 appears predominantly on PC, though it may also affect consoles under different names. Many players on several forums (Reddit, Steam, and Bungie) have come face to face with this issue.
Fixing it involves tweaking network settings like NAT type. While Bungie maintains server updates and acknowledges issues, the community reports persistent server-related problems on forums and Twitter.
During troubleshooting, I experienced mixed success while adjusting router settings for NAT types and port forwarding. Bungie’s official Twitter provides updates, but dedicated Centipede Support post lacks comprehensive solutions.
We are investigating an increase in CURRANT, COCONUT, and CENTIPEDE error codes.
— Bungie Help (@BungieHelp) September 19, 2023
More Destiny 2 Error Fixes by eXputer;
Thanks! Do share your feedback with us. ⚡
How can we make this post better? Your help would be appreciated. ✍
