VLESS VPN Connected but IP Not Changing: Fix Guide

When your VLESS VPN shows as connected but your IP address doesn’t change, it typically indicates that either the traffic isn’t being properly routed through the VPN, there’s a configuration issue with the 3x-ui panel, or there’s a client-side problem preventing proper IP masking. This is a common issue that can be resolved through systematic troubleshooting.

Contents

• Common Causes of IP Address Not Changing
• Server-Side 3x-ui Troubleshooting
• Client-Side Configuration Issues
• Network and System-Level Solutions
• Advanced Troubleshooting Steps
• Prevention and Best Practices

---

Common Causes of IP Address Not Changing

The IP address not changing despite a successful VPN connection usually stems from one of these root causes:

Traffic Routing Issues: Even if the VPN appears connected, your device might still be routing some or all traffic through your regular internet connection rather than the VPN tunnel. This can happen when the VPN client isn’t configured to force all traffic through the encrypted tunnel.

Configuration Mismatches: The 3x-ui panel configuration might have settings that prevent proper IP masking, such as incorrect Listen Domain settings or subscription service issues where the wrong IP address is being used.

Network Interference: Your ISP, router, or local network might be interfering with the VPN connection, either by blocking traffic or causing leaks that reveal your real IP address.

According to SuperUser discussions, a simple traceroute test can reveal whether traffic is actually going through the VPN - if the path changes when connected, the VPN is working but there may be other issues causing IP detection problems.

---

Server-Side 3x-ui Troubleshooting

Check Listen Domain Configuration

The most common server-side issue with 3x-ui and VLESS is the Listen Domain setting. As noted in the IvanBayan guide, if the Listen Domain is not set properly, the subscription service substitutes the IP address from the X-Real-IP header instead of using the correct connection address.

Steps to fix:

1. Log into your 3x-ui panel
2. Navigate to the Inbound configuration for the affected user
3. Verify the Listen Domain/IP field - it should be set to your server’s IP address or domain
4. If empty, the server will listen on all IP addresses, which can cause routing issues

Verify Subscription Service Configuration

If you’re using subscription links (which appears to be the case based on your setup), the subscription service might be generating incorrect configurations. As mentioned in GitHub issue #3142, subscription configs sometimes don’t work while manual VLESS links do.

Solution: Try generating a manual VLESS configuration instead of using the subscription service to see if this resolves the IP change issue.

Check Server Firewall and Port Forwarding

Ensure that:

• The VPN ports are properly forwarded on your router
• The server firewall allows traffic on the configured ports
• No CGNAT issues are affecting the connection (as mentioned in GitHub issue #3200)

---

Client-Side Configuration Issues

Verify Client Mode Settings

You mentioned using “Invisible Man” client in proxy mode. For VLESS to properly mask your IP address, it typically needs to be in full VPN mode, not just proxy mode. A proxy only routes specific application traffic, while a VPN routes all device traffic.

Steps to correct:

1. Change the client from proxy mode to full VPN/tunnel mode
2. Ensure the routing settings are configured to force all traffic through the VPN
3. Check that the client has proper permission to modify network routing

Test with Different Clients

Since you’ve already tried both “Invisible Man” and “Nekoray” with the same results, the issue likely isn’t client-specific. However, testing with other popular VLESS clients like V2RayN, Clash, or official Xray clients can help isolate whether it’s a client configuration issue.

Configuration File Validation

The VLESS configuration link might have incorrect parameters. Check that:

• The UUID is correct and matches what’s in the 3x-ui panel
• The transport protocol (WebSocket, TCP, etc.) is properly configured
• Security settings (TLS, etc.) are appropriate for your network

---

Network and System-Level Solutions

Disable IPv6 to Prevent Leaks

IPv6 can cause IP leaks even when IPv4 VPN is working properly. As noted in SNBForums discussions, IPv6 enabled on your device can cause data leaks.

Steps to disable IPv6:

1. Go to Network Connections in Windows
2. Right-click your active connection and select Properties
3. Uncheck “Internet Protocol Version 6 (TCP/IPv6)”
4. Restart your network connection and VPN client

Check for DNS Leaks

DNS leaks can reveal your location and ISP even when the IP is masked. To test:

1. Connect to the VPN
2. Visit a DNS leak test website like dnsleaktest.com
3. If your real DNS servers appear, you have a DNS leak

Fix: Configure the VPN client to use the VPN provider’s DNS servers or manually set DNS servers to reliable ones like Cloudflare (1.1.1.1) or Google (8.8.8.8).

Clear Browser Cache and DNS

Sometimes browsers cache your real IP information. Try:

• Clearing browser cache and cookies
• Flushing DNS cache with ipconfig /flushdns in Command Prompt
• Restarting your computer before connecting to the VPN

---

Advanced Troubleshooting Steps

Perform Traceroute Testing

As recommended by SuperUser experts, run traceroute commands to verify traffic routing:

1. Open Command Prompt
2. Run tracert google.com (VPN disconnected)
3. Connect to VPN
4. Run tracert google.com again (VPN connected)

If the traceroute paths are different, the VPN is working but there may be IP detection issues.

Test with Different IP Detection Methods

Different websites detect IP in different ways. Try multiple IP detection tools:

• whatismyipaddress.com
• ipinfo.io
• checkmyip.com
• browser-based IP detection extensions

If some show the VPN IP and others don’t, it might be a detection method issue rather than a VPN problem.

Check for ISP Blocking

According to Reddit discussions, your ISP might be blacklisting the VPN server’s IP range. Try:

• Connecting from a different network (mobile hotspot, friend’s network)
• If it works there, your ISP is likely blocking the VPN
• Consider using different ports (like 443 for WebSocket) or obfuscation techniques

---

Prevention and Best Practices

Regular Configuration Audits

Periodically review your 3x-ui configuration to ensure:

• All users have proper settings
• No outdated configurations are being used
• Server IP/domain settings haven’t changed

Monitor for IP Leaks

Use browser extensions like IPLeak or VPN Check to continuously monitor for IP and DNS leaks while connected to the VPN.

Keep Software Updated

Ensure both your 3x-ui panel and VPN clients are up to date, as updates often include fixes for routing and connection issues.

Create a Troubleshooting Checklist

For future setups, create a checklist that includes:

• Server-side configuration verification
• Client mode settings
• IPv6 disabling
• DNS configuration
• IP testing methods

This systematic approach will help you quickly identify and resolve similar issues in the future.

---

Sources

1. r/dumbclub - Set up a Vless with X-ui but doesn’t work
2. 3X-UI VPN on Your Server: Install & Configure Easily [Guide]
3. 3X-UI | FASTVPS Documentation
4. How to proxy a 3x-ui subscription service via Nginx on a different host | IvanBayan
5. Running 3x-ui Behind CGNAT with VLESS WS/WS+TLS - GitHub Issue #3200
6. 3X-UI Graphics Panel - Documentation & FAQ
7. r/dumbclub - Slow download speeds with 3X-UI + VLESS (Nekoray)
8. VPN is working but IP address not changing - Super User
9. Windows - My IP address doesn’t change when connected, why? - IVPN Help
10. My IP Address Doesn’t Change, Is Wrong, or Is Not Displayed - VPN Proxy Master Help
11. Solved - VPN setup on router but IP Address not changing - SNBForums
12. GitHub - VLESS subscription config doesn’t connect, while manual VLESS link works - Issue #3142

Conclusion

The issue of VLESS VPN showing as connected but IP address not changing typically stems from configuration issues rather than fundamental connection problems. Based on the troubleshooting steps above, you should:

1. Start with server-side checks - Verify your 3x-ui Listen Domain settings and ensure the subscription service is using the correct IP address
2. Move to client-side verification - Confirm the client is in full VPN mode, not proxy mode, and test with different configuration methods
3. Address network-level issues - Disable IPv6, check for DNS leaks, and verify your ISP isn’t blocking the VPN
4. Use advanced testing methods - Perform traceroute tests and check multiple IP detection websites to isolate the exact nature of the problem

Since your VPN works on 11 other devices successfully, the issue is likely specific to this new Windows 11 PC’s configuration rather than a server-wide problem. Focus on the client-side settings and network configuration on this particular machine to resolve the IP masking issue.