amnezia-vpn/amnezia-client

Fork 0

mirror of https://github.com/amnezia-vpn/amnezia-client.git synced 2026-10-14 21:34:26 +00:00

[GH-ISSUE #1870] No connection on created tunnel, no tunnel interface IP acquisition #804

New issue

Open

opened 2026-10-13 20:28:53 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-13 20:28:53 +00:00

Owner

Originally created by @VladislavKaganov on GitHub (Sep 17, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1870

Describe the bug
Hello.
Encountered an ambiguous issue.
I try to connect my VPS server via Windows application 4.8.10.0 using XRay. Application goes through connection establishment and says "Connected".
But, if I see, that tunnel interface, created by application, does not acquire IP address and stays with APIPA one. Therefore, all of my traffic goes through regular cable interface and routes via my ISP without routing into the tunnel

To Reproduce
Steps to reproduce the behavior:

Open Amnezia App.
Press "Connect" in order to establish XRay tunnel.
Wait loading, see "Connected".
Try seeing public address via myip.com or other such service and see your regular ISP address.
Open command prompt and see ipconfig. Amnezia's created tunnel has APIPA address.

Expected behavior

Open Amnezia App.
Press "Connect" in order to establish XRay tunnel.
Wait loading, see "Connected".
Try seeing public address via myip.com or other such service and see your VPS address.
Open command prompt and see ipconfig. Amnezia's created tunnel has some normal assigned address.

Log files
AmneziaVPN.log
AmneziaVPN-service.log

Screenshots

Desktop

OS: Windows 11 24H2
Version 4.8.10.0

Server (please complete the following information):

OS: Ubuntu 24.04

Additional context

First of all, I tried using these same settings on my other devices, connected to the same LAN (i.e. my phone, tablet and laptop). On ALL of them connection to the same server works just fine, no issues. Configuration on the problematic PC is imported from a working device (laptop with the same Amnezia VPN app version) via sharing amnezia_config.vpn file. That imo proves that it's not an ISP blockage issue, because no matter the device, they reside behind the same public IP.
Disabled my antivirus, firewall. No effect.
Uninstalled my other VPN apps I use for work. No effect.
Reinstalled Amnezia app, rebooted several times. No effect.
Ended several processes, which I thought could affect the connection. No effect.
Rebooted both of my routers (one in AP mode and the Gateway (main) one). No effect.
Checked log files - no errors (see files above). Tried collecting a dump via Wireshark - saw no serious issues with connection to my VPS address while establishing and ending session via Amnezia app.
Disabled other interfaces on PC. No effect.
Cleared VPS from Amnezia software serveral times. No effect. Also with reinstalling OS. No effect too.

This Issue appeared suddenly. I didn't see any updates or major installations affecting my network settings. Windows updates I have disabled totally.
On this machine I also have VMWare workstation, which could potentially be the case, but I don't think so. It didn't update at the time the problem appeared.

Gotta mention again, that all this setup, including VMWare and other VPN apps, didn't disturb Amnezia's work until recently. Everything worked just fine, but suddenly it didn't.

Originally created by @VladislavKaganov on GitHub (Sep 17, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1870 **Describe the bug** Hello. Encountered an ambiguous issue. I try to connect my VPS server via Windows application 4.8.10.0 using XRay. Application goes through connection establishment and says "Connected". But, if I see, that tunnel interface, created by application, does not acquire IP address and stays with APIPA one. Therefore, all of my traffic goes through regular cable interface and routes via my ISP without routing into the tunnel **To Reproduce** Steps to reproduce the behavior: 1. Open Amnezia App. 2. Press "Connect" in order to establish XRay tunnel. 3. Wait loading, see "Connected". 4. Try seeing public address via myip.com or other such service and see your regular ISP address. 5. Open command prompt and see ipconfig. Amnezia's created tunnel has APIPA address. **Expected behavior** 1. Open Amnezia App. 2. Press "Connect" in order to establish XRay tunnel. 3. Wait loading, see "Connected". 4. Try seeing public address via myip.com or other such service and see your VPS address. 5. Open command prompt and see ipconfig. Amnezia's created tunnel has some normal assigned address. **Log files** [AmneziaVPN.log](https://github.com/user-attachments/files/22393777/AmneziaVPN.log) [AmneziaVPN-service.log](https://github.com/user-attachments/files/22393778/AmneziaVPN-service.log) **Screenshots** <img width="622" height="155" alt="Image" src="https://github.com/user-attachments/assets/1cfd6522-3d32-43c6-aae6-3e30fda2c6a4" /> **Desktop** - OS: Windows 11 24H2 - Version 4.8.10.0 **Server (please complete the following information):** - OS: Ubuntu 24.04 **Additional context** 1. First of all, I tried using these same settings on my other devices, connected to the same LAN (i.e. my phone, tablet and laptop). On ALL of them connection to the same server works just fine, no issues. Configuration on the problematic PC is imported from a working device (laptop with the same Amnezia VPN app version) via sharing amnezia_config.vpn file. That imo proves that it's not an ISP blockage issue, because no matter the device, they reside behind the same public IP. 2. Disabled my antivirus, firewall. No effect. 3. Uninstalled my other VPN apps I use for work. No effect. 4. Reinstalled Amnezia app, rebooted several times. No effect. 5. Ended several processes, which I thought could affect the connection. No effect. 6. Rebooted both of my routers (one in AP mode and the Gateway (main) one). No effect. 7. Checked log files - no errors (see files above). Tried collecting a dump via Wireshark - saw no serious issues with connection to my VPS address while establishing and ending session via Amnezia app. 8. Disabled other interfaces on PC. No effect. 9. Cleared VPS from Amnezia software serveral times. No effect. Also with reinstalling OS. No effect too. This Issue appeared suddenly. I didn't see any updates or major installations affecting my network settings. Windows updates I have disabled totally. On this machine I also have VMWare workstation, which could potentially be the case, but I don't think so. It didn't update at the time the problem appeared. Gotta mention again, that all this setup, including VMWare and other VPN apps, didn't disturb Amnezia's work until recently. Everything worked just fine, but suddenly it didn't.

bsakaguchi commented

2026-10-13 20:28:54 +00:00

Author

Owner

@VladislavKaganov commented on GitHub (Sep 18, 2025):

Today also:

Tried installing older application versions: 4.8.9.2, 4.8.8.3, 4.7.0.0. Didn't help, nothing worked. Tunnel interface still isn't being configured with an IP address.
Tried uninstalling Amnezia, showing hidden in a device manager and uninstalling tun2socks Tunnel adapter. Then rebooting and installing Amnezia again. Also didn't work.
Tried changing my LAN interface static IP address to the DHCP one, which I got. No result.
Tried changing my NIC's MAC to a virtual one (i.e. AAAA.AAAA.AAAA). Didn't work.
Tried connecting USB network adapter, disabling primary one and establishing connection via USB one. Same result. Internet connection via ISP, tunnel "Connected", tunnel interface without the address.
Tried flushing dns via ipconfig /flushdns and routing via netsh interface ip delete destinationcache. No result.

Still can't understand what stops the application from configuring network address. From what I can see in the app on my laptop, when the tunnel is established, the tunnel interface has its network settings configured as if they're manual and not DHCP.
When I try to open tunnel interface while "Connected" on the problematic PC, all the setting are blank.

@VladislavKaganov commented on GitHub (Sep 18, 2025): Today also: - Tried installing older application versions: 4.8.9.2, 4.8.8.3, 4.7.0.0. Didn't help, nothing worked. Tunnel interface still isn't being configured with an IP address. - Tried uninstalling Amnezia, showing hidden in a device manager and uninstalling tun2socks Tunnel adapter. Then rebooting and installing Amnezia again. Also didn't work. - Tried changing my LAN interface static IP address to the DHCP one, which I got. No result. - Tried changing my NIC's MAC to a virtual one (i.e. AAAA.AAAA.AAAA). Didn't work. - Tried connecting USB network adapter, disabling primary one and establishing connection via USB one. Same result. Internet connection via ISP, tunnel "Connected", tunnel interface without the address. - Tried flushing dns via ipconfig /flushdns and routing via netsh interface ip delete destinationcache. No result. Still can't understand what stops the application from configuring network address. From what I can see in the app on my laptop, when the tunnel is established, the tunnel interface has its network settings configured as if they're manual and not DHCP. When I try to open tunnel interface while "Connected" on the problematic PC, all the setting are blank.

bsakaguchi commented

2026-10-13 20:28:55 +00:00

Author

Owner

@VladislavKaganov commented on GitHub (Sep 19, 2025):

Today I tried switching to AmneziaWG and it worked.
My belief now is that apparently XRay configuration or application isn't properly deleted when uninstalling Amnezia or at some other step, which makes it not to configure the tunnel interface.
I guess I'll stick with AWG for now.

But if dear developers come to explore this issue and it's really some improper installation or so, I'll leave it open for now.

@VladislavKaganov commented on GitHub (Sep 19, 2025): Today I tried switching to AmneziaWG and it worked. My belief now is that apparently XRay configuration or application isn't properly deleted when uninstalling Amnezia or at some other step, which makes it not to configure the tunnel interface. I guess I'll stick with AWG for now. But if dear developers come to explore this issue and it's really some improper installation or so, I'll leave it open for now.

bsakaguchi commented

2026-10-13 20:28:55 +00:00

Author

Owner

@simptom569 commented on GitHub (Nov 2, 2025):

It's the same situation, but even AmneziaWg doesn't work.
Moreover, AmneziaVPN on linux and android work well with the key.

@simptom569 commented on GitHub (Nov 2, 2025): It's the same situation, but even AmneziaWg doesn't work. Moreover, AmneziaVPN on linux and android work well with the key.

bsakaguchi commented

2026-10-13 20:28:55 +00:00

Author

Owner

@kuitog commented on GitHub (Dec 21, 2025):

Same Issue +1, made me go crazy

@kuitog commented on GitHub (Dec 21, 2025): Same Issue +1, made me go crazy

bsakaguchi commented

2026-10-13 20:28:56 +00:00

Author

Owner

@SkivHisink commented on GitHub (Jan 22, 2026):

What worked for me

On Windows 11 25H2, the TUN interface (tun2) was created successfully, but it ended up with an APIPA address (169.254.x.x). Because of that, traffic was not routed through the tunnel, even though the client reported a Connected state.

Manually assigning an IPv4 address to the TUN interface resolved the issue immediately:

netsh interface ipv4 set address name="tun2" static 10.33.0.1 255.255.255.252 10.33.0.2

After applying this:

routing started working as expected
the public IP changed correctly
VPN traffic was properly routed through Xray

It seems that, in some cases on Windows 11, the TUN interface does not receive an IPv4 address automatically.

@SkivHisink commented on GitHub (Jan 22, 2026): **What worked for me** On Windows 11 25H2, the TUN interface (tun2) was created successfully, but it ended up with an APIPA address (169.254.x.x). Because of that, traffic was not routed through the tunnel, even though the client reported a Connected state. Manually assigning an IPv4 address to the TUN interface resolved the issue immediately: ``` netsh interface ipv4 set address name="tun2" static 10.33.0.1 255.255.255.252 10.33.0.2 ``` After applying this: * routing started working as expected * the public IP changed correctly * VPN traffic was properly routed through Xray It seems that, in some cases on Windows 11, the TUN interface does not receive an IPv4 address automatically.

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

amnezia-vpn/amnezia-client#804

No description provided.

Rows
Columns