"Barrier Is Starting" on client, doesn't connect. VPN to blame?

noveltomatillo8 commented 2 years ago

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

dondre commented 2 years ago

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.

JoeCodeswell commented 2 years ago

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

piemanny commented 2 years ago

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?

ghowoo commented 2 years ago

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

noveltomatillo8 commented 2 years ago

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

octoshrimpy commented 2 years ago

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

pvskp commented 1 year ago

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.

clicnetcom commented 1 month ago

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

debauchee / barrier