[GH-ISSUE #1945] Don't work with mac OS ventura 13.4

gitea-mirror commented

2026-05-05 07:49:32 -06:00

Owner

Originally created by @Imran4424 on GitHub (Jun 17, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1945

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

Originally created by @Imran4424 on GitHub (Jun 17, 2023). Original GitHub issue: https://github.com/debauchee/barrier/issues/1945 ### 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_

gitea-mirror commented

2026-05-05 07:49:34 -06:00

Author

Owner

@MicahBird commented on GitHub (Jun 19, 2023):

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.

@MicahBird commented on GitHub (Jun 19, 2023): 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.

gitea-mirror commented

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

Author

Owner

@dbeecham commented on GitHub (Jun 27, 2023):

[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.

@dbeecham commented on GitHub (Jun 27, 2023): ``` [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.

gitea-mirror commented

2026-05-05 07:49:40 -06:00

Author

Owner

@zhuoqun-chen commented on GitHub (Jul 6, 2023):

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:

Even though I already granted barrier the permission:

@zhuoqun-chen commented on GitHub (Jul 6, 2023): > ### 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](https://github.com/debauchee/barrier/assets/73287160/e354b8bf-ae5d-420e-b34e-a66bbbfe66ee) Even though I already granted `barrier` the permission: ![image](https://github.com/debauchee/barrier/assets/73287160/178f86e9-8a4c-4905-91f0-4a13202ef9dc)

gitea-mirror commented

2026-05-05 07:49:42 -06:00

Author

Owner

@zhuoqun-chen commented on GitHub (Jul 6, 2023):

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.

@zhuoqun-chen commented on GitHub (Jul 6, 2023): 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](https://github.com/debauchee/barrier/assets/73287160/ae86ff5b-34a9-4dbc-9cd4-5c4bd8fedcf8)

gitea-mirror commented

2026-05-05 07:49:43 -06:00

Author

Owner

@rghose commented on GitHub (Jul 28, 2023):

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.

@rghose commented on GitHub (Jul 28, 2023): 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.

gitea-mirror commented

2026-05-05 07:49:44 -06:00

Author

Owner

@loood commented on GitHub (Jul 28, 2023):

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

@loood commented on GitHub (Jul 28, 2023): Didn't work for me with ubuntu as the server and macos as the client.

gitea-mirror commented

2026-05-05 07:49:46 -06:00

Author

Owner

@drownzz commented on GitHub (Aug 18, 2023):

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

@drownzz commented on GitHub (Aug 18, 2023): I have the same problem as @rghose Windows as Server and Mac as Client is not working The other way around it is.

gitea-mirror commented

2026-05-05 07:49:47 -06:00

Author

Owner

@gbicann commented on GitHub (Sep 6, 2023):

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.

@gbicann commented on GitHub (Sep 6, 2023): 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.

gitea-mirror commented

2026-05-05 07:49:48 -06:00

Author

Owner

@hexamagus commented on GitHub (Sep 30, 2023):

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

@hexamagus commented on GitHub (Sep 30, 2023): 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`: ```bash 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 ```bash error, no objects specified in config file problems making Certificate Request ```

gitea-mirror commented

2026-05-05 07:49:48 -06:00

Author

Owner

@paulcwarren commented on GitHub (Oct 17, 2023):

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

@paulcwarren commented on GitHub (Oct 17, 2023): Thanks for the workaround. This worked for me also on my Ventura mac also.

gitea-mirror commented

2026-05-05 07:49:50 -06:00

Author

Owner

@evan-kolberg commented on GitHub (Oct 21, 2023):

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

On mac, cd to the "~/Library/Application Support/barrier/SSL" location in terminal.
Paste openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 -keyout Barrier.pem -out Barrier.pem and click enter.
There should be a bunch of fields to fill out. Put whatever, it doesn't matter.
Restart Barrier on macOS. There should now be a SSL fingerprint menu. Make sure you see your key when you click on the dropdown.
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.
Restart Barrier on Windows.

Not related, but some other useful tips:

If using a VPN or something that can interfere with the auto-config, on the client, manually put in the server's local IP.
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 👍😜

@evan-kolberg commented on GitHub (Oct 21, 2023): 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 👍😜

gitea-mirror commented

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

Author

Owner

@m-graf commented on GitHub (Nov 3, 2023):

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!

@m-graf commented on GitHub (Nov 3, 2023): > 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!

gitea-mirror commented

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

Author

Owner

@ethan-phu commented on GitHub (Jan 12, 2024):

it works

@ethan-phu commented on GitHub (Jan 12, 2024): it works

gitea-mirror commented

2026-05-05 07:49:52 -06:00

Author

Owner

@huanlirui commented on GitHub (Jan 16, 2024):

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

On mac, cd to the "~/Library/Application Support/barrier/SSL" location in terminal.

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

There should be a bunch of fields to fill out. Put whatever, it doesn't matter.

Restart Barrier on macOS. There should now be a SSL fingerprint menu. Make sure you see your key when you click on the dropdown.

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.

Restart Barrier on Windows.

Not related, but some other useful tips:

If using a VPN or something that can interfere with the auto-config, on the client, manually put in the server's local IP.

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

@huanlirui commented on GitHub (Jan 16, 2024): > 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

Rows
Columns

[GH-ISSUE #1945] Don't work with mac OS ventura 13.4 #1421

What happened?

Version

Git commit hash (if applicable)

If applicable, where did you install Barrier from?

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

What OS versions are you using?

Relevant log output

Any other information

What happened?

Version

Git commit hash (if applicable)

If applicable, where did you install Barrier from?

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

What OS versions are you using?

Relevant log output

Any other information