Mac Server -> Windows 10 client : Impossible to connected

[KevinLetellier]

What happened?

I installed Barrier on my MacBook Pro and my W10 client.
The installation went fine, but when connecting my mac as Server et my Windows as client, i have this message :
WARNING: Failed to connect to server: Timed out

BUT

When i put my W10 as server, and the mac as a client, it works.

I tried to change the name of both screen and put the configuration server with the right name, and nothing changed.

Version

v2.4.0

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)

macOS

What OS versions are you using?

OSX 13.0.1 (22A400)
W10 22H2 64b

Relevant log output

Mac server Output : 
[2022-12-12T12:56:26] INFO: starting server
[2022-12-12T12:56:26] INFO: config file: /private/var/folders/9t/pv5dd9hs6c736s5h5vw0rx_m0000gn/T/Barrier.wNZAdp
[2022-12-12T12:56:26] INFO: log level: INFO
[2022-12-12T12:56:26] INFO: drag and drop enabled
started server (IPv4/IPv6), waiting for clients
2022-12-12 12:56:26.643128+0100 barriers[2326:55548] starting cocoa loop


W10 Client output : 
[2022-12-12T12:53:25] NOTE: connecting to '192.168.1.39': 192.168.1.39:24800
[2022-12-12T12:53:40] WARNING: failed to connect to server: Timed out

Any other information

No response

[oudajosefu]

I'm having the same issue now too even though it was just working yesterday.

[plouton24]

Did this on my Mac M1(13.1) W10(2H2):

Try to set the server to IP to manual on client(Windows) and then it will ask for you to ask the SSL fingerprint click "Yes". Then you can set it to auto config again.

FYI: When I upgraded from 13.0.1 to 13.1 I had remove and re-add Barrier.app from Accessibility in Security & Privacy to get it to start on MacOS

[Malachai7]

Turn off your firewall on the macbook. Then try running the software and see if that works. If it does then that means your firewall is blocking it.

[taufiqmaulana]

Just having the same issue, caused by SSL failure, follow this step, and works for me

#231 (comment)