github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1680] "Barrier Is Starting" on client, doesn't connect. VPN to blame? #1242

New issue

Open

opened 2026-05-05 07:38:51 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 07:38:51 -06:00

Owner

Originally created by @noveltomatillo8 on GitHub (May 30, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1680

What happened?

I use Windscribe VPN on my W10 client with "ephemeral port forwarding" set up. When I connect to the VPN, Barrier hangs up on "Barrier Is Starting" with IPC Connection Error 7, and the log below. W10 server connects just fine with Windscribe (without port forwarding). As soon as I turn off the VPN on the client, Barrier starts with no problems whatsoever.

I've browsed here to try to find a solution, but haven't found reference to Connection Error 7, and the "disable SSH" solution from #1421 doesn't work (the log doesn't seem to indicate a SSH issue). I've set up split tunneling on Windscribe and whitelisted barrier.exe, barrierc.exe, barrierd.exe, barriers.exe, and openssl.exe. I'm kinda at my wit's end here... Anyone else have this issue with their VPN?

Version

v2.3.4

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

Windows

What OS versions are you using?

Windows 10 on both machines

Relevant log output

[2022-05-29T20:33:30] NOTE: connecting to '': :::24800
[2022-05-29T20:33:30] DEBUG: Opening new socket: 07122710
[2022-05-29T20:33:30] DEBUG: Closing socket: 07122710
[2022-05-29T20:33:30] WARNING: failed to connect to server: The specified address is not available from the local machine
[2022-05-29T20:33:30] DEBUG: retry in 1 seconds
[2022-05-29T20:33:31] NOTE: connecting to '': :::24800
[2022-05-29T20:33:31] DEBUG: Opening new socket: 07122380
[2022-05-29T20:33:31] DEBUG: Closing socket: 07122380
[2022-05-29T20:33:31] WARNING: failed to connect to server: The specified address is not available from the local machine
[2022-05-29T20:33:31] DEBUG: retry in 1 seconds
[2022-05-29T20:33:32] NOTE: connecting to '': :::24800
[2022-05-29T20:33:32] DEBUG: Opening new socket: 07122650
[2022-05-29T20:33:32] DEBUG: Closing socket: 07122650
[2022-05-29T20:33:32] WARNING: failed to connect to server: The specified address is not available from the local machine
[2022-05-29T20:33:32] DEBUG: retry in 1 seconds
[2022-05-29T20:33:33] NOTE: connecting to '': :::24800
[2022-05-29T20:33:33] DEBUG: Opening new socket: 07122350
[2022-05-29T20:33:33] DEBUG: Closing socket: 07122350
[2022-05-29T20:33:33] WARNING: failed to connect to server: The specified address is not available from the local machine
[2022-05-29T20:33:33] DEBUG: retry in 1 seconds
[2022-05-29T20:33:34] NOTE: connecting to '': :::24800
[2022-05-29T20:33:34] DEBUG: Opening new socket: 071224A0
[2022-05-29T20:33:34] DEBUG: Closing socket: 071224A0
[2022-05-29T20:33:34] WARNING: failed to connect to server: The specified address is not available from the local machine

Any other information

No response

Originally created by @noveltomatillo8 on GitHub (May 30, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1680 ### What happened? I use Windscribe VPN on my W10 client with "ephemeral port forwarding" set up. When I connect to the VPN, Barrier hangs up on "Barrier Is Starting" with IPC Connection Error 7, and the log below. W10 server connects just fine with Windscribe (without port forwarding). As soon as I turn off the VPN on the client, Barrier starts with no problems whatsoever. I've browsed here to try to find a solution, but haven't found reference to Connection Error 7, and the "disable SSH" solution from #1421 doesn't work (the log doesn't seem to indicate a SSH issue). I've set up split tunneling on Windscribe and whitelisted barrier.exe, barrierc.exe, barrierd.exe, barriers.exe, and openssl.exe. I'm kinda at my wit's end here... Anyone else have this issue with their VPN? ### Version v2.3.4 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? Windows 10 on both machines ### Relevant log output ```shell [2022-05-29T20:33:30] NOTE: connecting to '': :::24800 [2022-05-29T20:33:30] DEBUG: Opening new socket: 07122710 [2022-05-29T20:33:30] DEBUG: Closing socket: 07122710 [2022-05-29T20:33:30] WARNING: failed to connect to server: The specified address is not available from the local machine [2022-05-29T20:33:30] DEBUG: retry in 1 seconds [2022-05-29T20:33:31] NOTE: connecting to '': :::24800 [2022-05-29T20:33:31] DEBUG: Opening new socket: 07122380 [2022-05-29T20:33:31] DEBUG: Closing socket: 07122380 [2022-05-29T20:33:31] WARNING: failed to connect to server: The specified address is not available from the local machine [2022-05-29T20:33:31] DEBUG: retry in 1 seconds [2022-05-29T20:33:32] NOTE: connecting to '': :::24800 [2022-05-29T20:33:32] DEBUG: Opening new socket: 07122650 [2022-05-29T20:33:32] DEBUG: Closing socket: 07122650 [2022-05-29T20:33:32] WARNING: failed to connect to server: The specified address is not available from the local machine [2022-05-29T20:33:32] DEBUG: retry in 1 seconds [2022-05-29T20:33:33] NOTE: connecting to '': :::24800 [2022-05-29T20:33:33] DEBUG: Opening new socket: 07122350 [2022-05-29T20:33:33] DEBUG: Closing socket: 07122350 [2022-05-29T20:33:33] WARNING: failed to connect to server: The specified address is not available from the local machine [2022-05-29T20:33:33] DEBUG: retry in 1 seconds [2022-05-29T20:33:34] NOTE: connecting to '': :::24800 [2022-05-29T20:33:34] DEBUG: Opening new socket: 071224A0 [2022-05-29T20:33:34] DEBUG: Closing socket: 071224A0 [2022-05-29T20:33:34] WARNING: failed to connect to server: The specified address is not available from the local machine ``` ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:38:53 -06:00

Author

Owner

@dondre commented on GitHub (Jun 4, 2022):

I'm having a similar issue although now it seems like some type of firewall block from the Mac server, Linux to Mac is working... frustrating.

Anyhow, try manually putting the server IP and unclicking auto-detect. From your logs it looks like its trying to connect to a server as localhost.

@dondre commented on GitHub (Jun 4, 2022): I'm having a similar issue although now it seems like some type of firewall block from the Mac server, Linux to Mac is working... frustrating. Anyhow, try manually putting the server IP and unclicking auto-detect. From your logs it looks like its trying to connect to a server as localhost.

gitea-mirror commented

2026-05-05 07:38:56 -06:00

Author

Owner

@JoeCodeswell commented on GitHub (Jun 7, 2022):

Me too.
Windows 10- server, Mac Catalina - client, Barrier 2.4.0 on both.
I start the server, then the client.
The client says "Barrier is starting", then seemingly, hangs. Just keeps on saying, "Barrier is starting".
Mouse is stopped at the server screen edge.
Love and peace,
Joe

@JoeCodeswell commented on GitHub (Jun 7, 2022): Me too. Windows 10- server, Mac Catalina - client, Barrier 2.4.0 on both. I start the server, then the client. The client says "Barrier is starting", then seemingly, hangs. Just keeps on saying, "Barrier is starting". Mouse is stopped at the server screen edge. Love and peace, Joe

gitea-mirror commented

2026-05-05 07:38:58 -06:00

Author

Owner

@piemanny commented on GitHub (Jun 30, 2022):

Hello I have something similar. So basically I am using barrier on OSX (its my server) and when it is on, barrier doesn't connect. I think that the VPN is tunneling all traffic. Is there a way for it to tunnel all traffic but barrier?

@piemanny commented on GitHub (Jun 30, 2022): Hello I have something similar. So basically I am using barrier on OSX (its my server) and when it is on, barrier doesn't connect. I think that the VPN is tunneling all traffic. Is there a way for it to tunnel all traffic but barrier?

gitea-mirror commented

2026-05-05 07:38:59 -06:00

Author

Owner

@ghowoo commented on GitHub (Sep 28, 2022):

I have the same issue. Barrier connects very well, but it loses the connection once my client computer connects to VPN.

@ghowoo commented on GitHub (Sep 28, 2022): I have the same issue. Barrier connects very well, but it loses the connection once my client computer connects to VPN.

gitea-mirror commented

2026-05-05 07:39:01 -06:00

Author

Owner

@noveltomatillo8 commented on GitHub (Oct 15, 2022):

This is still happening on 2.4.0 even without VPN enabled. Any update or suggestions, or are we just out of luck here?

@noveltomatillo8 commented on GitHub (Oct 15, 2022): This is still happening on 2.4.0 even without VPN enabled. Any update or suggestions, or are we just out of luck here?

gitea-mirror commented

2026-05-05 07:39:02 -06:00

Author

Owner

@octoshrimpy commented on GitHub (Oct 20, 2022):

@noveltomatillo8 check #1812 as it may have been firewall shenanigans

@octoshrimpy commented on GitHub (Oct 20, 2022): @noveltomatillo8 check #1812 as it may have been firewall shenanigans

gitea-mirror commented

2026-05-05 07:39:02 -06:00

Author

Owner

@pvskp commented on GitHub (Oct 11, 2023):

I've faced this same problem. In my case, while using the NordVPN, adding the Barrier port to the allowlist solved the problem

nordvpn allowlist add port 24800

Maybe for other providers it can be something similar.

@pvskp commented on GitHub (Oct 11, 2023): I've faced this same problem. In my case, while using the NordVPN, adding the Barrier port to the allowlist solved the problem ``` nordvpn allowlist add port 24800 ``` Maybe for other providers it can be something similar.

gitea-mirror commented

2026-05-05 07:39:03 -06:00

Author

Owner

@clicnetcom commented on GitHub (Oct 19, 2024):

@pvskp Great catch!
In my case I had to also run nordvpn set lan-discovery enabled

@clicnetcom commented on GitHub (Oct 19, 2024): @pvskp Great catch! In my case I had to also run `nordvpn set lan-discovery enabled`