Perpetual "Connecting..."

[Firesnakeel]

Describe the bug VPN won't turn on; the big button displays "Connecting...", but that never goes anywhere.

To Reproduce Steps to reproduce the behavior:

1. Open the app/program.
2. Click on the "Connect" button.
3. Wait as long as you like.

Expected behavior The app should connect, but that never happens.

Log files AmneziaVPN-service.log

Desktop:

• OS: Windows 11 (don't think I've had the issue before migrating from Windows 10 back in mid-July.)
• Version 23H2

Smartphone: Nothing Phone 1. Curiously enough, my smartphone runs the app just fine. Maybe because I never tried to use the split tunneling there?

Additional context Hey everyone.

At first, my issue was "backend failure" (someone else posted about it (and that issue never got resolved, sadly)), but it seems to have mutated into the permanent "Connecting..." problem. The service just doesn't work anymore. I suspect that split tunneling may be the underlying cause, because I do not remember having that issue before attempting (and failing, since it didn't work) to use that feature.

I'm attaching the VPN-service log, but it's essentially just this over and over: 2024-08-10 19:25:45 debug Amnezia "WindowsServiceManager" "OpenSCManager access given - 0" 2024-08-10 19:25:45 debug Amnezia "WindowsServiceManager" "Opening Service - AmneziaVPNSplitTunnel" 2024-08-10 19:25:45 debug Amnezia "WindowsServiceManager" "Service manager execute access granted" 2024-08-10 19:25:45 debug Amnezia "WindowsServiceManager" "Service start not possible, as its running" 2024-08-10 19:25:45 debug Amnezia "WindowsSplitTunnel" "No Split-Tunnel Conflict detected, continue." 2024-08-10 19:25:45 debug Amnezia "WindowsSplitTunnel" "Try to open Split Tunnel Driver" 2024-08-10 19:25:45 debug Amnezia "WindowsUtils" "Failed to open Driver: - ."

I've also deleted earlier logs (kind of a stupid thing to do in retrospect) when trying to remove everything Amnezia-related for a clean install to try and get rid of the split tunnel prompt on the button page (which I don't think was there before I tried enabling it?..), but after disabling it's still there, and not even a fresh install helped. Also, as mentioned before, I used to have the "backend failure", when I had to reboot the PC for VPN to connect. Not sure if this plays into the current issue or not.

Please look into it. Rebooting the PC used to help with the backend failure thing, but not with "Connecting...". I just can't use the service on my PC at this point.

[Firesnakeel]

Okay, I already have an update after playing around with the app. Feel free to delete the issue if you feel like it's not needed anymore.

I tried "cleaning the active server from Amnezia software" using the relevant button, and then just installed AmneziaWG. Now everything works fine. Note that even a fresh install did not help with that problem.

I hope it lasts, but I'm still afraid of trying to use the split tunneling thing, considering the driver issue (or whatever it is) that my log indicates.

[outspace]

It happens what you have already started windows service. We did some fix around this issue #791 and #738 .

What AmneziaVPN do you use?

[Firesnakeel]

It happens what you have already started windows service. We did some fix around this issue #791 and #738 .

What AmneziaVPN do you use?

Not sure what you mean by which one I'm using... If you're referring to the version, then it's the latest one now (4.6.0.3). Before that it was most likely an earlier one, but, as I said, simply updating to the newest version with a clean install didn't help, I had to clean the active server from Amnezia software (maybe I missed a spot when removing the previous version though).

Also, the issue reappeared today. Amnezia was up and running until I noticed that everything online (browsers, game launchers, etc.) couldn't connect anymore. I tried restarting Amnezia, and, sure enough... "Connecting...".

In the VPN-service.log it's essentially the same thing: 2024-08-14 20:15:14 debug Amnezia "WindowsServiceManager" "OpenSCManager access given - 0" 2024-08-14 20:15:14 debug Amnezia "WindowsServiceManager" "Opening Service - AmneziaVPNSplitTunnel" 2024-08-14 20:15:14 debug Amnezia "WindowsServiceManager" "Service manager execute access granted" 2024-08-14 20:15:14 debug Amnezia "WindowsServiceManager" "Service start not possible, as its running" 2024-08-14 20:15:14 debug Amnezia "WindowsSplitTunnel" "No Split-Tunnel Conflict detected, continue." 2024-08-14 20:15:14 debug Amnezia "WindowsSplitTunnel" "Try to open Split Tunnel Driver" 2024-08-14 20:15:14 debug Amnezia "WindowsUtils" "Failed to open Driver: - ."

Thankfully, cleaning the server worked again, and it's running just fine now. I guess I can live with "flushing" the client every few days... Doesn't seem like the others have that problem, so it could just be my Win 11, I suppose. I have installed all the updates, so it shouldn't be outdated, but Win 11 in and of itself has been quite a headache to deal with.

[zrk4939]

Hello, i have a same problem with "Connect" button. BUT the VPN works!

Just to turn it off - you need to completely exit the program (by closing the program in the tray)

Anyway it still causes some inconvenience

AmneziaVPN 4.7.0.0 (same issue on 4.6.0.3) OS Win10

[Firesnakeel]

Hey, it's me again.

Another thing I noted: this occurs after I download something - via torrents, Steam, browser, etc. I'm not sure how to check at what point does Amnezia decide to stop working (edit: sometimes it works just fine, I think?.. Like, the VPN can work for days without issues, but then still stop working at some point), but it almost feels like it decides to 'break' either after I reach a certain download threshold, or when I download something that is too big?.. I'm honestly not sure.

Not sure how informative it is, but I hope it can be of help if someone decides to look into it. Thankfully, I don't need it 24/7 and can download most things without the vpn on, so it's not a critical issue. But, of course, it would be awesome if it was something that can somehow be permanently fixed.