[GH-ISSUE #1569] Connection between Windows and MacOS, but not working

gitea-mirror commented

2026-05-05 07:33:35 -06:00

Owner

Originally created by @nbourre on GitHub (Feb 15, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1569

What happened?

I have managed to connect my MacOS server with a Windows 10 client. I see that they get connected but the mouse does not travel to the Windows monitor.

I have tried the reverse, but MacOS as a client kept being in the "Barrier is starting" state.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Downloaded from GitHub

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

Windows, macOS

What OS versions are you using?

Windows 10 Pro 21H2 (Build 19044.1526)
MacOS Monterey (Version 12.0.1)

Relevant log output

[2022-02-15T14:34:42] INFO: starting server
[2022-02-15T14:34:42] INFO: config file: /private/var/folders/lb/hq1157px7h73_45gyzmw2kch0000gn/T/Barrier.fRspaz
[2022-02-15T14:34:42] INFO: log level: INFO
[2022-02-15T14:34:42] INFO: drag and drop enabled
started server (IPv4/IPv6), waiting for clients
2022-02-15 14:34:42.715953-0500 barriers[92551:1656750] starting cocoa loop
[2022-02-15T14:34:42] INFO: OpenSSL 3.0.0 7 sep 2021
[2022-02-15T14:34:42] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem
[2022-02-15T14:34:48] INFO: OpenSSL 3.0.0 7 sep 2021
[2022-02-15T14:34:48] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem
[2022-02-15T14:34:58] INFO: zeroconf client detected: INFO-PORT03
[2022-02-15T14:34:59] INFO: OpenSSL 3.0.0 7 sep 2021
[2022-02-15T14:34:59] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem
[2022-02-15T14:35:02] INFO: OpenSSL 3.0.0 7 sep 2021
[2022-02-15T14:35:02] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem
[2022-02-15T14:35:18] INFO: OpenSSL 3.0.0 7 sep 2021
[2022-02-15T14:35:18] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem
[2022-02-15T14:35:34] INFO: OpenSSL 3.0.0 7 sep 2021
[2022-02-15T14:35:34] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem

Any other information

No response

Originally created by @nbourre on GitHub (Feb 15, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1569 ### What happened? I have managed to connect my MacOS server with a Windows 10 client. I see that they get connected but the mouse does not travel to the Windows monitor. I have tried the reverse, but MacOS as a client kept being in the "Barrier is starting" state. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Downloaded from GitHub ### What OSes are you seeing the problem on? (Check all that apply) Windows, macOS ### What OS versions are you using? Windows 10 Pro 21H2 (Build 19044.1526) MacOS Monterey (Version 12.0.1) ### Relevant log output ```shell [2022-02-15T14:34:42] INFO: starting server [2022-02-15T14:34:42] INFO: config file: /private/var/folders/lb/hq1157px7h73_45gyzmw2kch0000gn/T/Barrier.fRspaz [2022-02-15T14:34:42] INFO: log level: INFO [2022-02-15T14:34:42] INFO: drag and drop enabled started server (IPv4/IPv6), waiting for clients 2022-02-15 14:34:42.715953-0500 barriers[92551:1656750] starting cocoa loop [2022-02-15T14:34:42] INFO: OpenSSL 3.0.0 7 sep 2021 [2022-02-15T14:34:42] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem [2022-02-15T14:34:48] INFO: OpenSSL 3.0.0 7 sep 2021 [2022-02-15T14:34:48] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem [2022-02-15T14:34:58] INFO: zeroconf client detected: INFO-PORT03 [2022-02-15T14:34:59] INFO: OpenSSL 3.0.0 7 sep 2021 [2022-02-15T14:34:59] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem [2022-02-15T14:35:02] INFO: OpenSSL 3.0.0 7 sep 2021 [2022-02-15T14:35:02] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem [2022-02-15T14:35:18] INFO: OpenSSL 3.0.0 7 sep 2021 [2022-02-15T14:35:18] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem [2022-02-15T14:35:34] INFO: OpenSSL 3.0.0 7 sep 2021 [2022-02-15T14:35:34] ERROR: ssl certificate doesn't exist: /Users/nbourre/Library/Application Support/barrier/SSL/Barrier.pem ``` ### Any other information _No response_

gitea-mirror commented

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

Author

Owner

@jasonmccallister commented on GitHub (Feb 16, 2022):

I'm also seeing the same thing, using macOS as the server and a linux desktop as the client. The macOS is throwing the error about the certificate:

ERROR: ssl certificate doesn't exist: /Users/<username>/Library/Application Support/barrier/SSL/Barrier.pem

I installed Barrier on macOS through brew, trying a manual install now to see if that resolves it.

@jasonmccallister commented on GitHub (Feb 16, 2022): I'm also seeing the same thing, using macOS as the server and a linux desktop as the client. The macOS is throwing the error about the certificate: ``` ERROR: ssl certificate doesn't exist: /Users/<username>/Library/Application Support/barrier/SSL/Barrier.pem ``` I installed Barrier on macOS through brew, trying a manual install now to see if that resolves it.

gitea-mirror commented

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

Author

Owner

@kaunix commented on GitHub (Feb 16, 2022):

Dogpyle same thing. newest version of macOS as a server and linux mint as a client.

@kaunix commented on GitHub (Feb 16, 2022): Dogpyle same thing. newest version of macOS as a server and linux mint as a client.

gitea-mirror commented

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

Author

Owner

@pzoltowski commented on GitHub (Feb 16, 2022):

doesn't work for me either. Using between MacOS Big Sur and Windows 10 (surface go). Can connect interactively but mouse sharing doesn't work no matter if macos or windows is the server

@pzoltowski commented on GitHub (Feb 16, 2022): doesn't work for me either. Using between MacOS Big Sur and Windows 10 (surface go). Can connect interactively but mouse sharing doesn't work no matter if macos or windows is the server

gitea-mirror commented

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

Author

Owner

@kaunix commented on GitHub (Feb 16, 2022):

in my case it turned out to be a screen alignment issue.
I have two monitors (a 50inch 4k tv and an imac)
if I don't align the imac so that it's just a little farther to the right than the tv the tv will be the only screen I can switch computers from.

@kaunix commented on GitHub (Feb 16, 2022): in my case it turned out to be a screen alignment issue. I have two monitors (a 50inch 4k tv and an imac) if I don't align the imac so that it's just a little farther to the right than the tv the tv will be the only screen I can switch computers from.

gitea-mirror commented

2026-05-05 07:33:45 -06:00

Author

Owner

@mrnarayanan commented on GitHub (Feb 17, 2022):

I'm getting the same error regarding the ssl certificate. I installed through github. Windows 10 (desktop) as server and MacBook Pro (2020 M1) as client.

@mrnarayanan commented on GitHub (Feb 17, 2022): I'm getting the same error regarding the ssl certificate. I installed through github. Windows 10 (desktop) as server and MacBook Pro (2020 M1) as client.

gitea-mirror commented

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

Author

Owner

@8fdafs2 commented on GitHub (Feb 24, 2022):

Same here. Windows 10 21H2 as the server and macOS Monterey 12.2 as the client, no matter SSL is on or off, the cursor disappears on both desktops.

@8fdafs2 commented on GitHub (Feb 24, 2022): Same here. Windows 10 21H2 as the server and macOS Monterey 12.2 as the client, no matter SSL is on or off, the cursor disappears on both desktops.

gitea-mirror commented

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

Author

Owner

@marshall commented on GitHub (Mar 2, 2022):

I was able to fix this by generating the Barrier.pem and fingerprint manually on my windows server using WSL2 (thanks to https://github.com/debauchee/barrier/issues/1563 for the suggestion):

$ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/
$ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
$ mkdir Fingerprints
$ openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt

@marshall commented on GitHub (Mar 2, 2022): I was able to fix this by generating the `Barrier.pem` and fingerprint manually on my windows server using WSL2 (thanks to https://github.com/debauchee/barrier/issues/1563 for the suggestion): ```shell $ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/ $ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem $ mkdir Fingerprints $ openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt ```

gitea-mirror commented

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

Author

Owner

@mrnarayanan commented on GitHub (Mar 2, 2022):

I'm getting the same error regarding the ssl certificate. I installed through github. Windows 10 (desktop) as server and MacBook Pro (2020 M1) as client.

It was an ssl issue for me. I went back to version 2.3.4 and it worked properly. I believe disabling ssl on 2.4 would also work.

@mrnarayanan commented on GitHub (Mar 2, 2022): > I'm getting the same error regarding the ssl certificate. I installed through github. Windows 10 (desktop) as server and MacBook Pro (2020 M1) as client. It was an ssl issue for me. I went back to version 2.3.4 and it worked properly. I believe disabling ssl on 2.4 would also work.

gitea-mirror commented

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

Author

Owner

@8fdafs2 commented on GitHub (Mar 3, 2022):

@marshall @mrnarayanan
The problem here seems to be related to the DPI scaling of Windows (I use 200% for a 4k display) and finally gets solved just now by following instructions of https://github.com/debauchee/barrier/issues/42#issuecomment-396000618, but on barriers.exe instead of barrier.exe.

It's probably not an SSL credential issue in my case.

@8fdafs2 commented on GitHub (Mar 3, 2022): @marshall @mrnarayanan The problem here seems to be related to the DPI scaling of Windows (I use 200% for a 4k display) and finally gets solved just now by following instructions of https://github.com/debauchee/barrier/issues/42#issuecomment-396000618, but on barriers.exe instead of barrier.exe. It's probably not an SSL credential issue in my case.

gitea-mirror commented

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

Author

Owner

@mdjahidhasan009 commented on GitHub (Mar 29, 2022):

Thanks @marshall its works

@mdjahidhasan009 commented on GitHub (Mar 29, 2022): Thanks @marshall its works

gitea-mirror commented

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

Author

Owner

@kennyhyun commented on GitHub (Apr 4, 2022):

$ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/
$ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
$ mkdir Fingerprints
$ openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt

Thanks @marshall
It was working for my Mac host.
Started with cd /Users/<user>/Library/Application Support/barrier/SSL/

@kennyhyun commented on GitHub (Apr 4, 2022): > ```shell > $ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/ > $ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem > $ mkdir Fingerprints > $ openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt > ``` Thanks @marshall It was working for my Mac host. Started with `cd /Users/<user>/Library/Application Support/barrier/SSL/`

gitea-mirror commented

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

Author

Owner

@nbourre commented on GitHub (Apr 25, 2022):

Using this solution from Marshall

In Windows, for those having a problem with the incorrect name related to name expected to be in format... use //CN=Barrier

For those who don't have WSL2 configured, you can also use Git Bash.

@nbourre commented on GitHub (Apr 25, 2022): Using this solution from [Marshall](https://github.com/debauchee/barrier/issues/1569#issuecomment-1057341877) In Windows, for those having a problem with the incorrect name related to `name expected to be in format...` use `//CN=Barrier` For those who don't have WSL2 configured, you can also use Git Bash.

gitea-mirror commented

2026-05-05 07:33:54 -06:00

Author

Owner

@hueyyeng commented on GitHub (May 29, 2022):

$ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/
$ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

Thanks @marshall and also @OmarShawky1 for the commands. Although my situation is slightly different where after generating the Barrier.pem file, the Barrier client prompted a dialog to trust the fingerprint and after accepting it, it works. I didn't need to run the command to output the Fingerprints/Local.txt.

My setup is Windows 10 (Build 19044) being the Barrier Server and the MBP 2021 model running macOS Monterey (12.3.1) as the Barrier Client. Both using Barrier v2.4.0.

@hueyyeng commented on GitHub (May 29, 2022): > ```shell > $ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/ > $ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem > ``` Thanks @marshall and also @OmarShawky1 for the commands. Although my situation is slightly different where after generating the `Barrier.pem` file, the Barrier client prompted a dialog to trust the fingerprint and after accepting it, it works. I didn't need to run the command to output the `Fingerprints/Local.txt`. My setup is Windows 10 (Build 19044) being the Barrier Server and the MBP 2021 model running macOS Monterey (12.3.1) as the Barrier Client. Both using Barrier v2.4.0.

gitea-mirror commented

2026-05-05 07:33:55 -06:00

Author

Owner

@kaunix commented on GitHub (May 29, 2022):

Do you have a terminal window open on the Mac? If so close it

On May 28, 2022, at 22:51, Huey Yeng @.***> wrote:

$ cd /mnt/c/Users//AppData/Local/Barrier/SSL/
$ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
Thanks @marshall and also @OmarShawky1 for the commands. Although my situation is slightly different where after generating the Barrier.pem file, the Barrier client prompted a dialog to trust the fingerprint and after accepting it, it works. I didn't need to run the command to output the Fingerprints/Local.txt.

My setup is Windows 10 (Build 19044) being the Barrier Server and the MBP 2021 model running macOS Monterey (12.3.1) as the Barrier Client. Both using Barrier v2.4.0.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

@kaunix commented on GitHub (May 29, 2022): Do you have a terminal window open on the Mac? If so close it > On May 28, 2022, at 22:51, Huey Yeng ***@***.***> wrote: > > > $ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/ > $ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem > Thanks @marshall and also @OmarShawky1 for the commands. Although my situation is slightly different where after generating the Barrier.pem file, the Barrier client prompted a dialog to trust the fingerprint and after accepting it, it works. I didn't need to run the command to output the Fingerprints/Local.txt. > > My setup is Windows 10 (Build 19044) being the Barrier Server and the MBP 2021 model running macOS Monterey (12.3.1) as the Barrier Client. Both using Barrier v2.4.0. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you commented.

gitea-mirror commented

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

Author

Owner

@hueyyeng commented on GitHub (May 29, 2022):

@kaunix I did have iTerm2 running but after generating the pem file, Barrier works without any issue.

@hueyyeng commented on GitHub (May 29, 2022): @kaunix I did have iTerm2 running but after generating the pem file, Barrier works without any issue.

gitea-mirror commented

2026-05-05 07:33:57 -06:00

Author

Owner

@kaunix commented on GitHub (May 29, 2022):

Yeah for some reason imterm2 works but the native terminal blocks the keyboard

On May 29, 2022, at 02:09, Huey Yeng @.***> wrote:

@kaunix I did have iTerm2 running but after generating the pem file, Barrier works without any issue.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

@kaunix commented on GitHub (May 29, 2022): Yeah for some reason imterm2 works but the native terminal blocks the keyboard > On May 29, 2022, at 02:09, Huey Yeng ***@***.***> wrote: > > > @kaunix I did have iTerm2 running but after generating the pem file, Barrier works without any issue. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you were mentioned.

gitea-mirror commented

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

Author

Owner

@Quadstronaut commented on GitHub (Jul 25, 2022):

Yeah for some reason imterm2 works but the native terminal blocks the keyboard
…
On May 29, 2022, at 02:09, Huey Yeng @.***> wrote: @kaunix I did have iTerm2 running but after generating the pem file, Barrier works without any issue. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

I am not having that issue. I have Terminal open right now and keyboard working fine on both server and client. Latest Barrier, MacOS 11.6.8 (20G730).

@Quadstronaut commented on GitHub (Jul 25, 2022): > Yeah for some reason imterm2 works but the native terminal blocks the keyboard > […](#) > On May 29, 2022, at 02:09, Huey Yeng ***@***.***> wrote: @kaunix I did have iTerm2 running but after generating the pem file, Barrier works without any issue. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. I am not having that issue. I have Terminal open right now and keyboard working fine on both server and client. Latest Barrier, MacOS 11.6.8 (20G730).

gitea-mirror commented

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

Author

Owner

@grtmaddy00 commented on GitHub (May 7, 2023):

For those who are struggling between mac and windows, I found a hack.
Environment: Win 10 (server) Mac Monterey (client)

Earlier I tried the default steps mentioned in the github description but always got connection timed out error. Tried all the approaches for multiple threads but nothing worked.
Then I switched the server to Mac and client to Windows. With this I was able to mac keyboard and trackpad for Windows but I wanted vice versa. Now here again I switched the client and server to the original desired configuration and it started working.

Not sure if this will work for you or not, but worth giving a shot

@grtmaddy00 commented on GitHub (May 7, 2023): For those who are struggling between mac and windows, I found a hack. Environment: Win 10 (server) Mac Monterey (client) Earlier I tried the default steps mentioned in the github description but always got connection timed out error. Tried all the approaches for multiple threads but nothing worked. Then I switched the server to Mac and client to Windows. With this I was able to mac keyboard and trackpad for Windows but I wanted vice versa. Now here again I switched the client and server to the original desired configuration and it started working. Not sure if this will work for you or not, but worth giving a shot

gitea-mirror commented

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

Author

Owner

@grtmaddy00 commented on GitHub (May 8, 2023):

Unfortunately this hack stopped working after restarting Windows. Still looking for a solution here

@grtmaddy00 commented on GitHub (May 8, 2023): Unfortunately this hack stopped working after restarting Windows. Still looking for a solution here

gitea-mirror commented

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

Author

Owner

@aswathselvam commented on GitHub (Nov 9, 2023):

$ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/
$ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
$ mkdir Fingerprints
$ openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt

Thanks @marshall It was working for my Mac host. Started with cd /Users/<user>/Library/Application Support/barrier/SSL/

@aswathselvam commented on GitHub (Nov 9, 2023): > > ```shell > > $ cd /mnt/c/Users/<user>/AppData/Local/Barrier/SSL/ > > $ openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem > > $ mkdir Fingerprints > > $ openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt > > ``` > > Thanks @marshall It was working for my Mac host. Started with `cd /Users/<user>/Library/Application Support/barrier/SSL/`

gitea-mirror commented

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

Author

Owner

@Quadstronaut commented on GitHub (Nov 24, 2023):

Just touching this issue - I encounter the same error on latest at the time of writing, and have disabled ssl to ensure connectivity. Fortunately my network is entirely private to me.

@Quadstronaut commented on GitHub (Nov 24, 2023): Just touching this issue - I encounter the same error on latest at the time of writing, and have disabled ssl to ensure connectivity. Fortunately my network is entirely private to me.

Rows
Columns

[GH-ISSUE #1569] Connection between Windows and MacOS, but not working #1178

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