github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #166] MacOS Mojave support #134

New issue

Open

opened 2026-05-05 05:21:07 -06:00 by gitea-mirror · 14 comments

gitea-mirror commented

2026-05-05 05:21:07 -06:00

Owner

Originally created by @enineerr on GitHub (Oct 25, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/166

Operating Systems

Server: MacOS Mojave

Client: Windows 10 Pro

Barrier Version

2.1.0

Steps to reproduce bug

Start app and connect each other.
Look at log and notice no comments coming through even though there is no configuration done

Other info

When did the problem start to occur? When I started using it.
Is there a way to work around it? No, you can't use it on MacOS Mojave
Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

I am only asking for support. I really think that it is important to support this kind of thing. I know MacOS Mojave has only been out for a month or two, and I understand that this is not just one person looking at all the issues and writing code to fix them, but I really love what your doing here. I tried it on my mothers older macbook, (running 10.13) and it works better that synergy from when I demoed it in an apple store. If you can't find a work-a-round at the moment, it would be nice if updates could be posted on this thread.

Originally created by @enineerr on GitHub (Oct 25, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/166 ### Operating Systems ### Server: MacOS Mojave Client: Windows 10 Pro ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### 1) Start app and connect each other. 2) Look at log and notice no comments coming through even though there is no configuration done ### Other info ### * When did the problem start to occur? When I started using it. * Is there a way to work around it? No, you can't use it on MacOS Mojave * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here. I am only asking for support. I really think that it is important to support this kind of thing. I know MacOS Mojave has only been out for a month or two, and I understand that this is not just one person looking at all the issues and writing code to fix them, but I really love what your doing here. I tried it on my mothers older macbook, (running 10.13) and it works better that synergy from when I demoed it in an apple store. If you can't find a work-a-round at the moment, it would be nice if updates could be posted on this thread.

gitea-mirror added the

macOS

label 2026-05-05 05:21:07 -06:00

gitea-mirror commented

2026-05-05 05:21:12 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Oct 25, 2018):

Do you have a firewall rule on windows to allow the port barrier uses through? Currently with barrier 2.1.0 we don't open the firewall port on windows. This is something that will be fixed in barrier 2.2 though.

@AdrianKoshka commented on GitHub (Oct 25, 2018): Do you have a firewall rule on windows to allow the port barrier uses through? Currently with barrier 2.1.0 we don't open the firewall port on windows. This is something that will be fixed in barrier 2.2 though.

gitea-mirror commented

2026-05-05 05:21:13 -06:00

Author

Owner

@enineerr commented on GitHub (Oct 26, 2018):

Yes, when I first opened the app it asked for my consent and created one. I have just checked so, I do, sorry! I think that it is incompatibilities, as when I ran it on my high-sierra mac, it worked fine after configuration, but after reading that it only says 10.9-10.13 I think it is definitely incompatibilities. More proof, when testing with secondary MacBook, I used the same windows 10 client and it worked! But I need my iMac not, a MacBook. Again I am asking for support and updates on the support. Thanks though!

@enineerr commented on GitHub (Oct 26, 2018): Yes, when I first opened the app it asked for my consent and created one. I have just checked so, I do, sorry! I think that it is incompatibilities, as when I ran it on my high-sierra mac, it worked fine after configuration, but after reading that it only says 10.9-10.13 I think it is definitely incompatibilities. More proof, when testing with secondary MacBook, I used the same windows 10 client and it worked! But I need my iMac not, a MacBook. Again I am asking for support and updates on the support. Thanks though!

gitea-mirror commented

2026-05-05 05:21:15 -06:00

Author

Owner

@p12tic commented on GitHub (Oct 26, 2018):

I think Barrier client works on 10.14, I've tested that several days ago. Not sure about the server though.

@p12tic commented on GitHub (Oct 26, 2018): I think Barrier client works on 10.14, I've tested that several days ago. Not sure about the server though.

gitea-mirror commented

2026-05-05 05:21:18 -06:00

Author

Owner

@enineerr commented on GitHub (Oct 28, 2018):

Sorry, I need it as a server!

@enineerr commented on GitHub (Oct 28, 2018): Sorry, I need it as a server!

gitea-mirror commented

2026-05-05 05:21:22 -06:00

Author

Owner

@danchann commented on GitHub (Nov 1, 2018):

Barrier 2.1.0 client does not work on 10.14, the cursor doesn't show but right click works.
Need to stop the client to get the cursor back on the server.
Just tested on my MacBook Pro (Client), Windows 10 (Server).

@danchann commented on GitHub (Nov 1, 2018): Barrier 2.1.0 client does not work on 10.14, the cursor doesn't show but right click works. Need to stop the client to get the cursor back on the server. Just tested on my MacBook Pro (Client), Windows 10 (Server).

gitea-mirror commented

2026-05-05 05:21:24 -06:00

Author

Owner

@Uricorn commented on GitHub (Nov 14, 2018):

Have Macbook client and Windows 10 server.

Was using Synergy till now with an old version, and after updating to Mojave that stopped working, and I found this. I suppose it's the same issue.

10.14 doesn't seem to have a release that can be used without building though so can't test.

@Uricorn commented on GitHub (Nov 14, 2018): Have Macbook client and Windows 10 server. Was using Synergy till now with an old version, and after updating to Mojave that stopped working, and I found this. I suppose it's the same issue. 10.14 doesn't seem to have a release that can be used without building though so can't test.

gitea-mirror commented

2026-05-05 05:21:25 -06:00

Author

Owner

@dayne commented on GitHub (Nov 15, 2018):

Noticed this issue thread and wanted to let folks know that Barrier can work fine in Mojave as a server (not tested as a client).

I'm using barrier as a server on MacOS Mojave (10.14.1) with the provide 2.1.0 package built by this team. I installed barrier via homebrew: brew cask install barrier

This system acts as a server for a Linux (Ubuntu 18.04) system using latest barrier built from source (a week ago).

I don't recall having to do anything special during the setup process to make this all come together gracefully.

@dayne commented on GitHub (Nov 15, 2018): Noticed this issue thread and wanted to let folks know that Barrier can work fine in Mojave as a server (not tested as a client). I'm using barrier as a server on MacOS Mojave (10.14.1) with the provide 2.1.0 package built by this team. I installed barrier via homebrew: `brew cask install barrier` This system acts as a server for a Linux (Ubuntu 18.04) system using latest barrier built from source (a week ago). I don't recall having to do anything special during the setup process to make this all come together gracefully.

gitea-mirror commented

2026-05-05 05:21:27 -06:00

Author

Owner

@Uricorn commented on GitHub (Nov 18, 2018):

I tried via brew now, and server runs just fine. @dayne

However running it as client gives an error of unknown protocol in OpenSSL.

ERROR: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

Edit: 5 hours later and it randomly started working. It may or may not continue to work after restart. (It doesn't)

@Uricorn commented on GitHub (Nov 18, 2018): I tried via brew now, and server runs just fine. @dayne However running it as client gives an error of unknown protocol in OpenSSL. `ERROR: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol` Edit: 5 hours later and it randomly started working. It may or may not continue to work after restart. (It doesn't)

gitea-mirror commented

2026-05-05 05:21:29 -06:00

Author

Owner

@a7hybnj2 commented on GitHub (Dec 2, 2018):

I just tested barrier installed with brew on my mbp running 10.14 as both client and server and couldn't find any issues. Everything was working as I expected it to.

@a7hybnj2 commented on GitHub (Dec 2, 2018): I just tested barrier installed with brew on my mbp running 10.14 as both client and server and couldn't find any issues. Everything was working as I expected it to.

gitea-mirror commented

2026-05-05 05:21:31 -06:00

Author

Owner

@troxor commented on GitHub (Jan 21, 2019):

Same here, with 10.14 client to an Archlinux server are both working fine.

@troxor commented on GitHub (Jan 21, 2019): Same here, with 10.14 client to an Archlinux server are both working fine.

gitea-mirror commented

2026-05-05 05:21:33 -06:00

Author

Owner

@jtara commented on GitHub (Mar 22, 2019):

HUGE memory leak! I have to restart the server several times a day.

@jtara commented on GitHub (Mar 22, 2019): HUGE memory leak! I have to restart the server several times a day.

gitea-mirror commented

2026-05-05 05:21:34 -06:00

Author

Owner

@a7hybnj2 commented on GitHub (Mar 31, 2019):

@jtara I haven't tried to diagnose if I have a memory leak or not but I certainly don't have to restart barrier...ever...

@a7hybnj2 commented on GitHub (Mar 31, 2019): @jtara I haven't tried to diagnose if I have a memory leak or not but I certainly don't have to restart barrier...ever...

gitea-mirror commented

2026-05-05 05:21:36 -06:00

Author

Owner

@wkunker commented on GitHub (May 1, 2019):

Barrier 2.1.0 working as a server on Mojave with Barrier 2.2.0 Windows 10 Pro client. I did not use auto-config, not sure if that makes a difference.

@wkunker commented on GitHub (May 1, 2019): Barrier 2.1.0 working as a server on Mojave with Barrier 2.2.0 Windows 10 Pro client. I did not use auto-config, not sure if that makes a difference.

gitea-mirror commented

2026-05-05 05:21:38 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jun 28, 2019):

I'm going to link this: https://github.com/debauchee/barrier/releases/tag/v2.3.0, new macOS build.

@AdrianKoshka commented on GitHub (Jun 28, 2019): I'm going to link this: https://github.com/debauchee/barrier/releases/tag/v2.3.0, new macOS build.

gitea-mirror referenced this issue

2026-05-05 05:24:07 -06:00

[GH-ISSUE #186] Problems with Neo2 layout #149