amnezia-vpn / amnezia-client

Amnezia VPN Client (Desktop+Mobile)
https://amnezia.org
GNU General Public License v3.0
4.47k stars 291 forks source link

Can't connect: another VPN connection is active #358

Open ADWadmin opened 12 months ago

ADWadmin commented 12 months ago

Describe the bug Cannot connect to the newly created and only VPN. Error: "Can't connect: another VPN connection is active".

To Reproduce

  1. By VDS
  2. Go to "Set up your own server" and enter the connection data.
  3. Click "Run setup Wizard" and select medium level.
  4. Waiting configuring...
  5. Once the configuration is complete, we are returned to the main screen where we click on the enable button.
  6. We're getting an error.

Expected behavior The connection should be established.

Log files AmneziaVPN.log

Screenshots Untitled

Desktop (please complete the following information):

Server (please complete the following information):

Additional context I don't see a new network adapter in Windows. I assume that it must have been created when installing the application or creating the VPN server. On the server, I can see the created container:

CONTAINER ID   IMAGE                 COMMAND                  CREATED          STATUS          PORTS                                       NAMES
19cfdf60a1d3   amnezia-shadowsocks   "dumb-init /opt/amne…"   12 minutes ago   Up 12 minutes   0.0.0.0:6789->6789/tcp, :::6789->6789/tcp   amnezia-shadowsocks

UFW does not display new rules for VPNs. Iptables is very complicated for me..... All I can say is that I don't see anything containing "1194" (OpenVPN port). But I see one line with "6789" (ShadowSocks port):

Chain DOCKER (2 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             {unknown to me ip}         tcp dpt:6789
ADWadmin commented 12 months ago

Going to "Server settings" then to "protocols and services" I created two more connection options. "OpenVpn" and "WireGuard". On the server, they are created:

CONTAINER ID   IMAGE                 COMMAND                  CREATED          STATUS          PORTS                                           NAMES
3d9410357ddf   amnezia-wireguard     "dumb-init /opt/amne…"   4 minutes ago    Up 4 minutes    0.0.0.0:51820->51820/udp, :::51820->51820/udp   amnezia-wireguard
8c8af7f5f947   amnezia-openvpn       "dumb-init /opt/amne…"   5 minutes ago    Up 5 minutes    0.0.0.0:1194->1194/udp, :::1194->1194/udp       amnezia-openvpn
19cfdf60a1d3   amnezia-shadowsocks   "dumb-init /opt/amne…"   48 minutes ago   Up 48 minutes   0.0.0.0:6789->6789/tcp, :::6789->6789/tcp       amnezia-shadowsocks

"OpenVpn" and "OpenVpn over ShadowSocks" have the same error. "WireGuard" works, but the app won't let me change the mode from "For all connections". I'm attaching a new log file: AmneziaVPN.log

ADWadmin commented 12 months ago

I moved on and installed the remaining protocols.

OpenVpn over Cloak Have the same error.

IPsec Windows has seen a new internet adapter "AmneziaVPN IKEv2" When trying to connect using the app, the connection is activated and immediately disconnected. When trying to connect using windows tray, I get an error: image

I am attaching a new log (it has been cleaned up since my last posts) AmneziaVPN.log

It turns out that out of the whole range of protocols, only WireGuard works for me. And the one only in the mode for all sites.

Any help would be appreciated. I would like to get a solution that I could recommend to my friends.

ADWadmin commented 12 months ago

The basic error "Can't connect: another VPN connection is active" was solved by disabling TAP-Windows Adapter V9. On the next attempt to connect, the adapter enabled and the connection was established.

ADWadmin commented 12 months ago

This operation has to be performed every time the OS is rebooted.

The basic error "Can't connect: another VPN connection is active" was solved by disabling TAP-Windows Adapter V9. On the next attempt to connect, the adapter enabled and the connection was established.

pokamest commented 7 months ago

Please report if issue still exists in AmneziaVPN 4.4