Destiny 2 Error Code LETTUCE: How to Fix It
Medium 20-60 minutes Medium Severity
Verified June 2026
- Error Code
- LETTUCE
- Brand
- Destiny 2
- Product Type
- game
- Severity
- Medium
- DIY Difficulty
- Medium
- Estimated Fix Time
- 20-60 minutes
Ad
Tools You'll Need
- Web browser (to access router admin panel)
- Ethernet cable (for wired connection test)
- Your router's admin username and password
- Your console's or PC's local IP address
How to Fix Error Code LETTUCE
-
Check Bungie's Server Status First
-
Restart Your Router and Modem
-
Check Your NAT Type
-
Enable UPnP on Your Router
Only enable UPnP if you trust all devices on your home network. UPnP can expose ports automatically, so avoid using it on shared or public networks. -
Manually Forward Destiny 2's Required Ports
-
Assign a Static Local IP to Your Gaming Device
-
Check Windows Firewall or Third-Party Antivirus (PC Only)
Do not leave your firewall permanently disabled. Only disable it briefly to test, then re-enable it immediately after. -
Try a Wired Ethernet Connection
-
Use Google or Cloudflare DNS
-
Consider Using a DMZ as a Last Resort
DMZ removes all router-level firewall protection from the designated device. Only use this option on a gaming console (which has its own security), not on a general-purpose PC. Remove the DMZ setting if the error is resolved by other means.
Ad
When to Call a Professional
If you have tried every step above and still receive the LETTUCE error, contact your Internet Service Provider (ISP). Some ISPs use carrier-grade NAT (CGNAT) on their network, which makes it impossible to achieve an Open NAT type without their intervention — they may be able to assign you a dedicated public IP address. Additionally, if your router firmware is outdated and its admin panel is inaccessible, a network technician can help you update it or replace the device.Frequently Asked Questions
What does Destiny 2 error code LETTUCE mean?
LETTUCE is Bungie's error code for a NAT or firewall connectivity issue. It means something on your network — your router's NAT settings, a firewall rule, or your ISP's infrastructure — is blocking the network traffic Destiny 2 needs to communicate with Bungie's servers.
How do I fix a Strict NAT type for Destiny 2?
To change a Strict NAT to Open or Moderate, start by enabling UPnP in your router's admin settings. If that does not work, manually forward Destiny 2's required TCP and UDP ports to your console's or PC's static local IP address. Reboot your router after making changes and check your NAT type again in your console's network settings.
Why do I keep getting LETTUCE even after fixing my NAT?
If the error persists after fixing your NAT, check whether Bungie's servers are experiencing an outage at bungie.net/en/Help. It is also worth checking whether a software firewall or antivirus on your PC is blocking Destiny 2. Some ISPs use carrier-grade NAT (CGNAT) which can prevent an Open NAT regardless of your router settings — in that case, contact your ISP.
Does a VPN fix Destiny 2 error code LETTUCE?
A VPN can sometimes help if your ISP is the source of the problem (such as CGNAT), because it can bypass certain ISP-level restrictions. However, VPNs can also introduce extra latency and may worsen your Destiny 2 connection. Bungie does not officially support VPN use, and it may violate the terms of service. Try fixing your NAT and firewall settings before considering a VPN.
Is Destiny 2 error code LETTUCE on my end or Bungie's end?
LETTUCE is almost always a local network issue on the player's end, specifically related to NAT or firewall configuration. However, during widespread Bungie server outages, LETTUCE can also appear even for players with perfect network setups. Always check Bungie's server status page first before making changes to your network.