search

debauchee / barrier

Open-source KVM software
Other
27.33k stars 1.51k forks source link

Don't work with mac OS ventura 13.4 #1945

Open Imran4424 opened 1 year ago

Imran4424 commented 1 year ago

What happened?

I use macbook pro m1 pro

Barrier worked perfectly till Mac OS Ventura 13.0

After upgrading it to MacOS Ventura 13.4

It stopped working

Since Barrier is Intel Kind It run with rosetta 2

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?

Ventura 13.4

Relevant log output

No response

Any other information

No response

MicahBird commented 1 year ago

At first I was also unable to get Barrier (v2.4.0) to connect to a server/function as a server on macOS Ventura 13.3. However, after checking the logs, it was an SSL related issue that prevented any connection. When I first opened Barrier it didn't prompt me to generate any SSL keys (I installed it via Homebrew) and so it would get stuck on the "Barrier is staring" phase. I was able to fix it by disabling SSL (on both the server and client), Menu Bar -> Barrier -> Change Settings -> Uncheck Enable SSL. Please use this option with care, as disabling SSL means your Barrier connections will not be secure.

dbeecham commented 1 year ago 
[2023-06-27T13:13:06] ERROR: ssl certificate doesn't exist: /Users/me/Library/Application Support/barrier/SSL/Barrier.pem
[2023-06-27T13:13:06] ERROR: could not load client certificates
[2023-06-27T13:13:06] ERROR: ssl certificate doesn't exist: /Users/me/Library/Application Support/barrier/SSL/Barrier.pem
[2023-06-27T13:13:06] ERROR: could not load client certificates

Same here.

zhuoqun-chen commented 1 year ago

What happened?

I use macbook pro m1 pro

Barrier worked perfectly till Mac OS Ventura 13.0

After upgrading it to MacOS Ventura 13.4

It stopped working

Since Barrier is Intel Kind It run with rosetta 2

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?

Ventura 13.4

Relevant log output

No response

Any other information

No response

I had exactly the same problem. after upgrading my Macbook Pro M1 to Ventura 13.4, the pop-up window kept showing me:

image

Even though I already granted barrier the permission:

image

zhuoqun-chen commented 1 year ago

I just found that the solution was already posted in #1856 :

Click the barrier item under Privacy & Security -- Accessibility and scroll down to the bottom of the menu, then remove it by clicking the minus sign and relaunch barrier and grant it with the permission again then barrier will work as usual.

image

rghose commented 1 year ago

This did not work for me. I was trying to use a Windows host as a server and the Mac as a client. Reversing this worked, i.e., Making the Mac as server and the windows a client.

loood commented 1 year ago

Didn't work for me with ubuntu as the server and macos as the client.

drownzz commented 1 year ago

I have the same problem as @rghose Windows as Server and Mac as Client is not working The other way around it is.

gbicann commented 1 year ago

I had this issue today and fixed it by generating my own key.

Run Terminal and then type these commands:

cd "~/Library/Application Support/barrier/SSL"
openssl req -new -newkey rsa:2048 -days 3650 -noenc -x509 -keyout Barrier.pem -out Barrier.pem

If you restart the server it will find the new key and offer it to clients. Clients will display the public key digest for you to validate.

hexamagus commented 1 year ago

thanks for the openssl command. However, on macOS 13.2.1 and openssl version == LibreSSL 3.3.6 I had to replace the -noenc flag with -nodes:

openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 -keyout Barrier.pem -out Barrier.pem

I entered dummy data for all the fields when prompted to define the Distinguished Name. I tried leaving some or all blank and would get an error about

error, no objects specified in config file
problems making Certificate Request
paulcwarren commented 11 months ago

Thanks for the workaround. This worked for me also on my Ventura mac also.

evan-kolberg commented 11 months ago

Got it working on Sonoma. Same steps, nothing different. My mac is the client and my windows is the server.

  1. On mac, cd to the "~/Library/Application Support/barrier/SSL" location in terminal.
  2. Paste openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 -keyout Barrier.pem -out Barrier.pem and click enter.
  3. There should be a bunch of fields to fill out. Put whatever, it doesn't matter.
  4. Restart Barrier on macOS. There should now be a SSL fingerprint menu. Make sure you see your key when you click on the dropdown.
  5. Copy that Barrier.pem file to the ~\AppData\Local\Barrier\SSL location on your windows machine. The .pem file needs to be the same on both the client and server.
  6. Restart Barrier on Windows.

Not related, but some other useful tips:

  1. If using a VPN or something that can interfere with the auto-config, on the client, manually put in the server's local IP.
  2. Make sure that your configure the server with the actual screen name. MacBookPro.local for example.

Edit: I can only get the mouse traveling to work when macOS is the server. When I need the mouse to go back using my windows, it can't. Really wish the server on windows would work. Anyone know why?

Edit 2: Nevermind, the autoconfig just picked the wrong location and tried to connect to myself or my router for some reason. Set the IP manually and it works 👍😜

m-graf commented 11 months ago

At first I was also unable to get Barrier (v2.4.0) to connect to a server/function as a server on macOS Ventura 13.3. However, after checking the logs, it was an SSL related issue that prevented any connection. When I first opened Barrier it didn't prompt me to generate any SSL keys (I installed it via Homebrew) and so it would get stuck on the "Barrier is staring" phase. I was able to fix it by disabling SSL (on both the server and client), Menu Bar -> Barrier -> Change Settings -> Uncheck Enable SSL. Please use this option with care, as disabling SSL means your Barrier connections will not be secure.

This is the answer that worked for me. Thank you!

ethan-phu commented 8 months ago

it works

huanlirui commented 8 months ago

Got it working on Sonoma. Same steps, nothing different. My mac is the client and my windows is the server.

  1. On mac, cd to the "~/Library/Application Support/barrier/SSL" location in terminal.
  2. Paste openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 -keyout Barrier.pem -out Barrier.pem and click enter.
  3. There should be a bunch of fields to fill out. Put whatever, it doesn't matter.
  4. Restart Barrier on macOS. There should now be a SSL fingerprint menu. Make sure you see your key when you click on the dropdown.
  5. Copy that Barrier.pem file to the ~\AppData\Local\Barrier\SSL location on your windows machine. The .pem file needs to be the same on both the client and server.
  6. Restart Barrier on Windows.

Not related, but some other useful tips:

  1. If using a VPN or something that can interfere with the auto-config, on the client, manually put in the server's local IP.
  2. Make sure that your configure the server with the actual screen name. MacBookPro.local for example.

Edit: I can only get the mouse traveling to work when macOS is the server. When I need the mouse to go back using my windows, it can't. Really wish the server on windows would work. Anyone know why?

Edit 2: Nevermind, the autoconfig just picked the wrong location and tried to connect to myself or my router for some reason. Set the IP manually and it works 👍😜

thanks ! it works