[GH-ISSUE #915] critical backendFailure #257

Closed
opened 2026-10-13 20:17:07 +00:00 by bsakaguchi · 20 comments
Owner

Originally created by @Peredery on GitHub (Jul 27, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/915

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Main page
  2. Click on Connect
  3. Wait 20-30s after connect

Expected behavior
Working :)

Log files
AmneziaVPN log.log

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Windows 11 23H2

Additional context

Originally created by @Peredery on GitHub (Jul 27, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/915 **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Go to Main page 2. Click on Connect 3. Wait 20-30s after connect **Expected behavior** Working :) **Log files** [AmneziaVPN log.log](https://github.com/user-attachments/files/16440232/AmneziaVPN.log.log) **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** Windows 11 23H2 **Additional context**
Author
Owner

@Moksggwp commented on GitHub (Jul 31, 2024):

Hi, I have the same problem. I have attached the error logs.
AmneziaVPN.log

`2024-07-30 19:01:48 debug VpnConfigurator::getDnsForConfig "172.29.172.254" "1.0.0.1"
2024-07-30 19:01:48 debug "Con

nectToVpn, Server index is 0, container is amnezia-awg, route mode is" Settings::VpnOnlyForwardSites
2024-07-30 19:01:48 debug IpcClient::init succeed
2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Initializing"
2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Connecting to: \\.\pipe\amneziavpn"
2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Daemon connected"
2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Check status"
2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Reading"
2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Parse command: status"
2024-07-30 19:01:49 debug Amnezia "LocalSocketController" "Reading"
2024-07-30 19:01:49 debug Amnezia "LocalSocketController" "Parse command: connected"
2024-07-30 19:01:49 debug Amnezia "LocalSocketController" "Handshake completed with: 7qOgC/IE37uVypskN3GMctn2342525235234"
2024-07-30 19:02:29 debug Amnezia "LocalSocketController" "Reading"
2024-07-30 19:02:29 debug Amnezia "LocalSocketController" "Parse command: backendFailure"
2024-07-30 19:02:29 critical backendFailure`

The connection lasted for about a minute, after which the connection from the Control Panel was lost. And it is impossible to connect after that, that is, I press the connect button and immediately disconnect, in the logs there is an error

P.s. edited the Amnezia line "LocalSocketController" "Handshake completed with:
I wasn't sure if it contained an access key or not, in general there was a full key in the logs

<!-- gh-comment-id:2259828394 --> @Moksggwp commented on GitHub (Jul 31, 2024): Hi, I have the same problem. I have attached the error logs. [AmneziaVPN.log](https://github.com/user-attachments/files/16437645/AmneziaVPN.log) `2024-07-30 19:01:48 debug VpnConfigurator::getDnsForConfig "172.29.172.254" "1.0.0.1" 2024-07-30 19:01:48 debug "Con nectToVpn, Server index is 0, container is amnezia-awg, route mode is" Settings::VpnOnlyForwardSites 2024-07-30 19:01:48 debug IpcClient::init succeed 2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Initializing" 2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Connecting to: \\\\.\\pipe\\amneziavpn" 2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Daemon connected" 2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Check status" 2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Reading" 2024-07-30 19:01:48 debug Amnezia "LocalSocketController" "Parse command: status" 2024-07-30 19:01:49 debug Amnezia "LocalSocketController" "Reading" 2024-07-30 19:01:49 debug Amnezia "LocalSocketController" "Parse command: connected" 2024-07-30 19:01:49 debug Amnezia "LocalSocketController" "Handshake completed with: 7qOgC/IE37uVypskN3GMctn2342525235234" 2024-07-30 19:02:29 debug Amnezia "LocalSocketController" "Reading" 2024-07-30 19:02:29 debug Amnezia "LocalSocketController" "Parse command: backendFailure" 2024-07-30 19:02:29 critical backendFailure` The connection lasted for about a minute, after which the connection from the Control Panel was lost. And it is impossible to connect after that, that is, I press the connect button and immediately disconnect, in the logs there is an error P.s. edited the Amnezia line "LocalSocketController" "Handshake completed with: I wasn't sure if it contained an access key or not, in general there was a full key in the logs
Author
Owner

@Cregrant commented on GitHub (Aug 2, 2024):

"pressing a connect button"
2024-08-02 21:04:08 debug Amnezia "LocalSocketController" "Reading"
2024-08-02 21:04:08 debug Amnezia "LocalSocketController" "Parse command: backendFailure"
2024-08-02 21:04:08 critical backendFailure
2024-08-02 21:04:08 debug Amnezia "LocalSocketController" "Parse command: disconnected"

This is really annoying error. Not only by the error itself but also by its verbose stack trace. I can fix it only by restarting pc or amnezia-vpn service.. and not forever of course.
Btw stopping the broken amnezia-vpn service gives another Windows hint: "Error 109: The pipe has been ended".

<!-- gh-comment-id:2265491159 --> @Cregrant commented on GitHub (Aug 2, 2024): "pressing a connect button" 2024-08-02 21:04:08 debug Amnezia "LocalSocketController" "Reading" 2024-08-02 21:04:08 debug Amnezia "LocalSocketController" "Parse command: backendFailure" 2024-08-02 21:04:08 critical backendFailure 2024-08-02 21:04:08 debug Amnezia "LocalSocketController" "Parse command: disconnected" This is really annoying error. Not only by the error itself but also by its verbose stack trace. I can fix it only by restarting pc or amnezia-vpn service.. and not forever of course. Btw stopping the broken amnezia-vpn service gives another Windows hint: "Error 109: The pipe has been ended".
Author
Owner

@liondandelion commented on GitHub (Aug 3, 2024):

The same issue is happening on Windows 10 Version 22H2 (x86_64). But downgrading to 4.5.3.0 version seems to fix the issue (working for about an hour already, while previously disconnected within a minute).

<!-- gh-comment-id:2266654170 --> @liondandelion commented on GitHub (Aug 3, 2024): The same issue is happening on Windows 10 Version 22H2 (x86_64). But downgrading to 4.5.3.0 version seems to fix the issue (working for about an hour already, while previously disconnected within a minute).
Author
Owner

@outspace commented on GitHub (Aug 3, 2024):

Please attach service log from C:\ProgramData\AmneziaVPN\log.

<!-- gh-comment-id:2266686987 --> @outspace commented on GitHub (Aug 3, 2024): Please attach service log from C:\ProgramData\AmneziaVPN\log.
Author
Owner

@liondandelion commented on GitHub (Aug 3, 2024):

Sure, i just thought it was the same as already provided here.
AmneziaVPN(1).log

<!-- gh-comment-id:2266697572 --> @liondandelion commented on GitHub (Aug 3, 2024): Sure, i just thought it was the same as already provided here. [AmneziaVPN(1).log](https://github.com/user-attachments/files/16480617/AmneziaVPN.1.log)
Author
Owner

@outspace commented on GitHub (Aug 3, 2024):

Windows desktop client consists of two parts: desktop client and Windows service.
You provided desktop client log.
Please provide Windows service log from C:\ProgramData\AmneziaVPN\log too.

<!-- gh-comment-id:2266705039 --> @outspace commented on GitHub (Aug 3, 2024): Windows desktop client consists of two parts: desktop client and Windows service. You provided desktop client log. Please provide Windows service log from C:\ProgramData\AmneziaVPN\log too.
Author
Owner

@liondandelion commented on GitHub (Aug 3, 2024):

AmneziaVPN-client.log
AmneziaVPN-service.log

This is happening on a friend's Windows PC (i'm not on Windows so can't reproduce it) with the latest version. And we found out that it is happening right after he launches Path of Exile with active connection. As i said earlier, this is not an issue with 4.5.3.0 version, it continues working as expected.

<!-- gh-comment-id:2266765546 --> @liondandelion commented on GitHub (Aug 3, 2024): [AmneziaVPN-client.log](https://github.com/user-attachments/files/16480995/AmneziaVPN-client.log) [AmneziaVPN-service.log](https://github.com/user-attachments/files/16480996/AmneziaVPN-service.log) This is happening on a friend's Windows PC (i'm not on Windows so can't reproduce it) with the latest version. And we found out that it is happening right after he launches Path of Exile with active connection. As i said earlier, this is not an issue with 4.5.3.0 version, it continues working as expected.
Author
Owner

@outspace commented on GitHub (Aug 3, 2024):

Lots of thanks.

We need some more information about this bug.

  1. Please disable killswith on 4.6 and make connection.
  2. Try tunnel.dll from 4.5.3 version and make connection. You can find tunnel.dll 4.5.3 there tunnel.dll

and provide logs from these cases.

<!-- gh-comment-id:2266920311 --> @outspace commented on GitHub (Aug 3, 2024): Lots of thanks. We need some more information about this bug. 1) Please disable killswith on 4.6 and make connection. 2) Try tunnel.dll from 4.5.3 version and make connection. You can find tunnel.dll 4.5.3 there [tunnel.dll](https://github.com/amnezia-vpn/3rd-prebuilt/blob/e568e7d0e8defe8fe009c0127323f2c55fd9be76/deploy-prebuilt/windows/x64/tunnel.dll) and provide logs from these cases.
Author
Owner

@liondandelion commented on GitHub (Aug 3, 2024):

  1. With killswitch disabled everything worked fine, even after PoE launch
    AmneziaVPN-nokillswitch.log
    AmneziaVPN-service-nokillswitch.log

  2. With the old tunnel.dll with or without sha file (with and without killswitch) app stuck in "Connecting..." state.
    AmneziaVPN-service-tunnelsha.log
    AmneziaVPN-tunnelsha.log

<!-- gh-comment-id:2267020787 --> @liondandelion commented on GitHub (Aug 3, 2024): 1. With killswitch disabled everything worked fine, even after PoE launch [AmneziaVPN-nokillswitch.log](https://github.com/user-attachments/files/16482276/AmneziaVPN-nokillswitch.log) [AmneziaVPN-service-nokillswitch.log](https://github.com/user-attachments/files/16482277/AmneziaVPN-service-nokillswitch.log) 2. With the old tunnel.dll with or without sha file (with and without killswitch) app stuck in "Connecting..." state. [AmneziaVPN-service-tunnelsha.log](https://github.com/user-attachments/files/16482272/AmneziaVPN-service-tunnelsha.log) [AmneziaVPN-tunnelsha.log](https://github.com/user-attachments/files/16482273/AmneziaVPN-tunnelsha.log)
Author
Owner

@Peredery commented on GitHub (Aug 6, 2024):

With killswitch disabled everything worked fine, even after PoE launch

Doesn't work for me

<!-- gh-comment-id:2270641854 --> @Peredery commented on GitHub (Aug 6, 2024): > With killswitch disabled everything worked fine, even after PoE launch Doesn't work for me
Author
Owner

@Peredery commented on GitHub (Aug 6, 2024):

Lots of thanks.

We need some more information about this bug.

  1. Please disable killswith on 4.6 and make connection.
  2. Try tunnel.dll from 4.5.3 version and make connection. You can find tunnel.dll 4.5.3 there tunnel.dll

and provide logs from these cases.

  1. still doesn't work
  2. still doesn't work
<!-- gh-comment-id:2271323983 --> @Peredery commented on GitHub (Aug 6, 2024): > Lots of thanks. > > We need some more information about this bug. > > 1. Please disable killswith on 4.6 and make connection. > 2. Try tunnel.dll from 4.5.3 version and make connection. You can find tunnel.dll 4.5.3 there [tunnel.dll](https://github.com/amnezia-vpn/3rd-prebuilt/blob/e568e7d0e8defe8fe009c0127323f2c55fd9be76/deploy-prebuilt/windows/x64/tunnel.dll) > > and provide logs from these cases. 1. still doesn't work 2. still doesn't work
Author
Owner

@Peredery commented on GitHub (Aug 6, 2024):

@outspace logs:
AmneziaVPN.log
AmneziaVPN-service.log

<!-- gh-comment-id:2271333161 --> @Peredery commented on GitHub (Aug 6, 2024): @outspace logs: [AmneziaVPN.log](https://github.com/user-attachments/files/16511128/AmneziaVPN.log) [AmneziaVPN-service.log](https://github.com/user-attachments/files/16511133/AmneziaVPN-service.log)
Author
Owner

@nexterot commented on GitHub (Sep 16, 2024):

same problem here on win10
android client on the same network connects successfully though

<!-- gh-comment-id:2353300169 --> @nexterot commented on GitHub (Sep 16, 2024): same problem here on win10 android client on the same network connects successfully though
Author
Owner

@Peredery commented on GitHub (Sep 20, 2024):

still doesn't work on windows 11

<!-- gh-comment-id:2363394091 --> @Peredery commented on GitHub (Sep 20, 2024): still doesn't work on windows 11
Author
Owner

@FuckingSherlock commented on GitHub (Oct 8, 2024):

Same problem. Has anyone fixed this?

<!-- gh-comment-id:2401003849 --> @FuckingSherlock commented on GitHub (Oct 8, 2024): Same problem. Has anyone fixed this?
Author
Owner

@siseen commented on GitHub (Oct 10, 2024):

same, appears only on lan connected device

<!-- gh-comment-id:2403795568 --> @siseen commented on GitHub (Oct 10, 2024): same, appears only on lan connected device
Author
Owner

@xobot-real commented on GitHub (Oct 11, 2024):

In my case restarting AmneziaVPN-service service helped, when you see in log cyclic error:

2024-08-06 18:40:27 debug Amnezia "LocalSocketController" "Parse command: disconnected"
2024-08-06 18:40:29 debug Amnezia "LocalSocketController" "Reading"
2024-08-06 18:40:29 debug Amnezia "LocalSocketController" "Parse command: backendFailure"
2024-08-06 18:40:29 critical backendFailure
<!-- gh-comment-id:2406489577 --> @xobot-real commented on GitHub (Oct 11, 2024): In my case restarting `AmneziaVPN-service` service helped, when you see in log cyclic error: ```code 2024-08-06 18:40:27 debug Amnezia "LocalSocketController" "Parse command: disconnected" 2024-08-06 18:40:29 debug Amnezia "LocalSocketController" "Reading" 2024-08-06 18:40:29 debug Amnezia "LocalSocketController" "Parse command: backendFailure" 2024-08-06 18:40:29 critical backendFailure ```
Author
Owner

@ivanmem commented on GitHub (Oct 16, 2024):

The same problem on Windows 11 and restarting the service for a while also helps.

<!-- gh-comment-id:2418010103 --> @ivanmem commented on GitHub (Oct 16, 2024): The same problem on Windows 11 and restarting the service for a while also helps.
Author
Owner

@nexterot commented on GitHub (Oct 17, 2024):

guys, for those who have troubles on Windows with only LAN - I found the solution

In my case connection was OK with WiFi adapter, but didn't work with LAN. What I did:

  • run command Get-NetIPinterface | where AddressFamily -eq "IPv4" in windows powershell
    this will list your interfaces, what we need is column InterfaceMetric

In my case it was:

  • 2 for LAN adapter
  • 5 for Amnezia Adapter
  • 55 fof WiFi adapter

Sooo this was exactly why all trafic went smoothly via Amnezia in case of WiFi because it has higher priority (5 vs 55) and also this is why there were no traffic via Amnezia because LAN adapter had higher priority than Amnezia (2 vs 5) - the lower the value, the highest priority it has.

If your case suits my case, then next you have to change the metric value of LAN adapter. Open your LAN adapter properties -> IPv4 (TCP-IPv4) properties -> Advanced -> (uncheck Automatic metric if checked) set Interface metric to any(?) value higher than Amnezia's metric (which was 5 in my case, so i set LAN metric to 6). As an option, there is also a powershell command Set-NetIPInterface for this action, you can google it yourself.

Spend hours finding out the problem, hope this will help anybody.

<!-- gh-comment-id:2418987617 --> @nexterot commented on GitHub (Oct 17, 2024): guys, for those who have troubles on Windows with only LAN - I found the solution In my case connection was OK with WiFi adapter, but didn't work with LAN. What I did: - run command `Get-NetIPinterface | where AddressFamily -eq "IPv4"` in windows powershell this will list your interfaces, what we need is column `InterfaceMetric` In my case it was: - 2 for LAN adapter - 5 for Amnezia Adapter - 55 fof WiFi adapter Sooo this was exactly why all trafic went smoothly via Amnezia in case of WiFi because it has higher priority (5 vs 55) and also this is why there were no traffic via Amnezia because LAN adapter had higher priority than Amnezia (2 vs 5) - the lower the value, the highest priority it has. If your case suits my case, then next you have to change the metric value of LAN adapter. Open your LAN adapter properties -> IPv4 (TCP-IPv4) properties -> Advanced -> (uncheck Automatic metric if checked) set Interface metric to any(?) value higher than Amnezia's metric (which was 5 in my case, so i set LAN metric to 6). As an option, there is also a powershell command `Set-NetIPInterface` for this action, you can google it yourself. Spend hours finding out the problem, hope this will help anybody.
Author
Owner

@gitmeatarru commented on GitHub (Apr 10, 2026):

same error, last fresh version amnezia:
[2026-04-10 07:57:16.147Z] [DEBUG] Amnezia : Logger::setServiceLogsEnabled(): Logs transitioned to be enabled
[2026-04-10 07:57:16.147Z] [INFO] Amnezia : Logging has enabled on AmneziaVPN version 4.8.14.5 477afb9d
[2026-04-10 07:57:16.147Z] [INFO] Amnezia : Windows 11 Version 24H2 (x86_64)
[2026-04-10 07:57:28.896Z] [DEBUG] Amnezia : VpnConfigurator::getDnsForConfig "1.1.1.1" "1.0.0.1"
[2026-04-10 07:57:28.896Z] [DEBUG] Amnezia : "Trying to connect to VPN, server index is 0, container is amnezia-awg2, route mode is" Settings::VpnOnlyForwardSites
[2026-04-10 07:57:28.896Z] [DEBUG] Amnezia LocalSocketController : Deactivating
[2026-04-10 07:57:28.896Z] [DEBUG] Amnezia : VpnProtocol::setConnectionState "Отключено"
[2026-04-10 07:57:28.966Z] [DEBUG] Amnezia LocalSocketController : Deactivating
[2026-04-10 07:57:28.966Z] [DEBUG] Amnezia : VpnProtocol::setConnectionState "Отключено"
[2026-04-10 07:57:29.176Z] [DEBUG] Amnezia : "Site split tunneling is disabled, route mode is 0"
[2026-04-10 07:57:29.176Z] [DEBUG] Amnezia : "App split tunneling is disabled, route mode is 0"
[2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Initializing
[2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Connecting to: \.\pipe\amneziavpn
[2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Daemon connected
[2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Check status
[2026-04-10 07:57:29.239Z] [DEBUG] Amnezia LocalSocketController : Reading
[2026-04-10 07:57:29.239Z] [DEBUG] Amnezia LocalSocketController : Parse command: status
[2026-04-10 07:57:59.698Z] [DEBUG] Amnezia LocalSocketController : Reading
[2026-04-10 07:57:59.698Z] [DEBUG] Amnezia LocalSocketController : Parse command: backendFailure
[2026-04-10 07:57:59.698Z] [ERROR] Amnezia LocalSocketController : generic backend failure error (fatal or error none)
[2026-04-10 07:57:59.698Z] [WARNING] Amnezia LocalSocketController : Invalid command received: {"errorCode":1,"type":"backendFailure"}

its connected only in 1st time, then i disconnect and try use split atunneling for apps
try connect - fail
turnoff split tunneling - fail
app not work now

<!-- gh-comment-id:4222101329 --> @gitmeatarru commented on GitHub (Apr 10, 2026): same error, last fresh version amnezia: [2026-04-10 07:57:16.147Z] [DEBUG] Amnezia : Logger::setServiceLogsEnabled(): Logs transitioned to be enabled [2026-04-10 07:57:16.147Z] [INFO] Amnezia : Logging has enabled on AmneziaVPN version 4.8.14.5 477afb9d [2026-04-10 07:57:16.147Z] [INFO] Amnezia : Windows 11 Version 24H2 (x86_64) [2026-04-10 07:57:28.896Z] [DEBUG] Amnezia : VpnConfigurator::getDnsForConfig "1.1.1.1" "1.0.0.1" [2026-04-10 07:57:28.896Z] [DEBUG] Amnezia : "Trying to connect to VPN, server index is 0, container is amnezia-awg2, route mode is" Settings::VpnOnlyForwardSites [2026-04-10 07:57:28.896Z] [DEBUG] Amnezia LocalSocketController : Deactivating [2026-04-10 07:57:28.896Z] [DEBUG] Amnezia : VpnProtocol::setConnectionState "Отключено" [2026-04-10 07:57:28.966Z] [DEBUG] Amnezia LocalSocketController : Deactivating [2026-04-10 07:57:28.966Z] [DEBUG] Amnezia : VpnProtocol::setConnectionState "Отключено" [2026-04-10 07:57:29.176Z] [DEBUG] Amnezia : "Site split tunneling is disabled, route mode is 0" [2026-04-10 07:57:29.176Z] [DEBUG] Amnezia : "App split tunneling is disabled, route mode is 0" [2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Initializing [2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Connecting to: \\.\pipe\amneziavpn [2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Daemon connected [2026-04-10 07:57:29.176Z] [DEBUG] Amnezia LocalSocketController : Check status [2026-04-10 07:57:29.239Z] [DEBUG] Amnezia LocalSocketController : Reading [2026-04-10 07:57:29.239Z] [DEBUG] Amnezia LocalSocketController : Parse command: status [2026-04-10 07:57:59.698Z] [DEBUG] Amnezia LocalSocketController : Reading [2026-04-10 07:57:59.698Z] [DEBUG] Amnezia LocalSocketController : Parse command: backendFailure [2026-04-10 07:57:59.698Z] [ERROR] Amnezia LocalSocketController : generic backend failure error (fatal or error none) [2026-04-10 07:57:59.698Z] [WARNING] Amnezia LocalSocketController : Invalid command received: {"errorCode":1,"type":"backendFailure"} its connected only in 1st time, then i disconnect and try use split atunneling for apps try connect - fail turnoff split tunneling - fail app not work now
Sign in to join this conversation.
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#257
No description provided.