[GH-ISSUE #1530] New macOS client isn't working with previously working macOS server

gitea-mirror commented

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

Owner

Originally created by @jmahone on GitHub (Jan 21, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1530

What happened?

So the old configuration was:

macOS server (Mojave): Venonat.local
IP address: 192.168.86.26

macOS client: whatever - sorry not so helpful, but just know that it worked and didn't have special characters in the name
IP address: whatever - different than the server, obviously, but irrelevant otherwise

This old configuration worked, other than the magic trackpad2 resolution/granularity not super smooth on the client

Today, I have a new configuration, using the same server as above.
The NEW macOS client (Monterey): myname-mbp.lan
IP address: 192.168.86.38

A couple of notes. The macOS server is running 10.14.6 Mojave, and the Barrier app is 2.3.3.
The macOS client is running 12.1 Monterey, and the Barrier app is 2.4.0.

Things I ran into along the way. The client-side seemed to need me to generate SSL keys output to the Barrier.pem file. That made an SSL error go away. I also had issues (I believe) with the "." in my client screen name (which takes it from the hostname). I set an alias for that, and now the server doesn't seem to reject based on unknown name.

Currently, the client doesn't connect to the server, and here are the logs.

The macOS server log shows:
FATAL: failed to start server: cannot bind address: Can't assign requested address
ERROR: process exited with error code: 1
INTO: detected process not running, auto restarting

This repeats, and I can see the Barrier app appearing and disappearing from the dock, and the activity monitor shows the Barrier app running (really, starting) and multiple instances of barriers appearing and disappearing.

Meanwhile, on the macOS client, the log shows:

NOTE: connecting to '192.168.86.26': 192.168.86.26:24800
INFO: OpenSSL 3.0.0 7 sep 2021
WARNING: failed to connect to server: Connection refused

The client app also repeatedly attempts to connect, leaving multiple (up to three) barrier app icons in the tray and multiple instances in the activity monitor.

So, after getting the SSL and client name issues seemingly squared away, the client connection is being refused.

Are there issues with running different versions of Barrier? (2.3.3 vs 2.4.0)
Are there issues running Barrier on two different macOS platforms? (Mojave vs Monterey)

TIA!

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

brew cask

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

macOS

What OS versions are you using?

server: Mojave 10.14.6
client: Monterey 12.1

Relevant log output

The macOS server log shows:
FATAL: failed to start server: cannot bind address: Can't assign requested address
ERROR: process exited with error code: 1
INTO: detected process not running, auto restarting

Meanwhile, on the macOS client, the log shows:

NOTE: connecting to '192.168.86.26': 192.168.86.26:24800
INFO: OpenSSL 3.0.0 7 sep 2021
WARNING: failed to connect to server: Connection refused

Any other information

No response

Originally created by @jmahone on GitHub (Jan 21, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1530 ### What happened? So the old configuration was: macOS server (Mojave): Venonat.local IP address: 192.168.86.26 macOS client: whatever - sorry not so helpful, but just know that it worked and didn't have special characters in the name IP address: whatever - different than the server, obviously, but irrelevant otherwise This old configuration worked, other than the magic trackpad2 resolution/granularity not super smooth on the client Today, I have a new configuration, using the same server as above. The NEW macOS client (Monterey): myname-mbp.lan IP address: 192.168.86.38 A couple of notes. The macOS server is running 10.14.6 Mojave, and the Barrier app is 2.3.3. The macOS client is running 12.1 Monterey, and the Barrier app is 2.4.0. Things I ran into along the way. The client-side seemed to need me to generate SSL keys output to the Barrier.pem file. That made an SSL error go away. I also had issues (I believe) with the "." in my client screen name (which takes it from the hostname). I set an alias for that, and now the server doesn't seem to reject based on unknown name. Currently, the client doesn't connect to the server, and here are the logs. The macOS server log shows: FATAL: failed to start server: cannot bind address: Can't assign requested address ERROR: process exited with error code: 1 INTO: detected process not running, auto restarting This repeats, and I can see the Barrier app appearing and disappearing from the dock, and the activity monitor shows the Barrier app running (really, starting) and multiple instances of barriers appearing and disappearing. Meanwhile, on the macOS client, the log shows: NOTE: connecting to '192.168.86.26': 192.168.86.26:24800 INFO: OpenSSL 3.0.0 7 sep 2021 WARNING: failed to connect to server: Connection refused The client app also repeatedly attempts to connect, leaving multiple (up to three) barrier app icons in the tray and multiple instances in the activity monitor. So, after getting the SSL and client name issues seemingly squared away, the client connection is being refused. Are there issues with running different versions of Barrier? (2.3.3 vs 2.4.0) Are there issues running Barrier on two different macOS platforms? (Mojave vs Monterey) TIA! ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? brew cask ### What OSes are you seeing the problem on? (Check all that apply) macOS ### What OS versions are you using? server: Mojave 10.14.6 client: Monterey 12.1 ### Relevant log output ```shell The macOS server log shows: FATAL: failed to start server: cannot bind address: Can't assign requested address ERROR: process exited with error code: 1 INTO: detected process not running, auto restarting Meanwhile, on the macOS client, the log shows: NOTE: connecting to '192.168.86.26': 192.168.86.26:24800 INFO: OpenSSL 3.0.0 7 sep 2021 WARNING: failed to connect to server: Connection refused ``` ### Any other information _No response_

gitea-mirror commented

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

Author

Owner

@jmahone commented on GitHub (Jan 21, 2022):

I'm glad to either roll back the client's Barrier app version to 2.3.3 or bump up the server's Barrier app version to 2.4.0 if that is deemed necessary. I guess I would prefer to roll back the 2.4.0 to 2.3.3 just because I had previously had success with 2.3.3 working on the client.

@jmahone commented on GitHub (Jan 21, 2022): I'm glad to either roll back the client's Barrier app version to 2.3.3 or bump up the server's Barrier app version to 2.4.0 if that is deemed necessary. I guess I would prefer to roll back the 2.4.0 to 2.3.3 just because I had previously had success with 2.3.3 working on the client.

gitea-mirror commented

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

Author

Owner

@soundnvision commented on GitHub (Jan 24, 2022):

I'm also trying to get barrier to work on a Mac with (Edit: Mojave) 10.4.6, a Mac with Monterey 12.1 and a win10 PC. Running Barrier 2.4.0 on all of them. Have tried enabling/disablingSSL, changing names, deleting and recreating computer icons in the configure server section - got it to work with limited success between the two Mac's but then it went away. Made each computer the server and the other two the clients - in each instance, no computer behaved better as a client than a server - they all can see one another, but they're just not connecting.

I'm also getting the
[2022-01-23T13:48:11] WARNING: failed to connect to server: Connection refused
[2022-01-23T13:48:12] INFO: stopping barrier desktop process
[2022-01-23T13:48:12] NOTE: connecting to '192.168.x.xxx': 192.168.x.xx:24800
[2022-01-23T13:48:13] ERROR: process exited with error code: 11

Isn't there a guide somewhere on how to install this and a list of what to check when its being configured?

@soundnvision commented on GitHub (Jan 24, 2022): I'm also trying to get barrier to work on a Mac with (Edit: Mojave) 10.4.6, a Mac with Monterey 12.1 and a win10 PC. Running Barrier 2.4.0 on all of them. Have tried enabling/disablingSSL, changing names, deleting and recreating computer icons in the configure server section - got it to work with limited success between the two Mac's but then it went away. Made each computer the server and the other two the clients - in each instance, no computer behaved better as a client than a server - they all can see one another, but they're just not connecting. I'm also getting the [2022-01-23T13:48:11] WARNING: failed to connect to server: Connection refused [2022-01-23T13:48:12] INFO: stopping barrier desktop process [2022-01-23T13:48:12] NOTE: connecting to '192.168.x.xxx': 192.168.x.xx:24800 [2022-01-23T13:48:13] ERROR: process exited with error code: 11 Isn't there a guide somewhere on how to install this and a list of what to check when its being configured?

gitea-mirror commented

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

Author

Owner

@gardncol commented on GitHub (Jan 24, 2022):

I just tried using Barrier on Mac OS Big Sur (11.6.1) as the server and Win 10 as the client. Both were on 2.4.0. I was getting the connection refused error as @soundnvision was seeing.

I solve the issue by moving the Mac to 2.3.4. Once I stared up the server it worked quickly and easily. The only difference that I saw in the GUIs were in 2.3.4 there was an SSL fingerprint where in 2.4.0 there wasn't.

@gardncol commented on GitHub (Jan 24, 2022): I just tried using Barrier on Mac OS Big Sur (11.6.1) as the server and Win 10 as the client. Both were on 2.4.0. I was getting the connection refused error as @soundnvision was seeing. I solve the issue by moving the Mac to 2.3.4. Once I stared up the server it worked quickly and easily. The only difference that I saw in the GUIs were in 2.3.4 there was an SSL fingerprint where in 2.4.0 there wasn't.

gitea-mirror commented

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

Author

Owner

@soundnvision commented on GitHub (Jan 25, 2022):

I took the advice of @gardncol and downgraded to barrier 2.3.4 on all machines, restarted and relaunched and I got the same general results as when I was working with 2.4.0

@soundnvision commented on GitHub (Jan 25, 2022): I took the advice of @gardncol and downgraded to barrier 2.3.4 on all machines, restarted and relaunched and I got the same general results as when I was working with 2.4.0

gitea-mirror commented

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

Author

Owner

@ghost commented on GitHub (Jan 25, 2022):

I found that may Mac (Big Sur) and Windows (11) only connect on 2.4 if I turn off SSL. I can have require client certificate on and it works fine, just SSL causing the issue.

@ghost commented on GitHub (Jan 25, 2022): I found that may Mac (Big Sur) and Windows (11) only connect on 2.4 if I turn off SSL. I can have require client certificate on and it works fine, just SSL causing the issue.

gitea-mirror commented

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

Author

Owner

@soundnvision commented on GitHub (Jan 25, 2022):

I tried just the M1 running Monterey and the PC running Win10, PC as server, M1 as client, SSL enabled on both, Barrier 2.3.4

[2022-01-25T17:24:52] INFO: starting server
[2022-01-25T17:24:52] INFO: config file: C:/Users/mikef/AppData/Local/Temp/Barrier.AoiHfH
[2022-01-25T17:24:52] INFO: log level: INFO
[2022-01-25T17:24:52] INFO: service command updated
[2022-01-25T17:24:52] INFO: starting new process as privileged user
[2022-01-25T17:24:52] INFO: drag and drop enabled
[2022-01-25T17:24:52] ERROR: failed to get desktop path, no drop target available, error=2 started server (IPv4/IPv6), waiting for clients server status: active

🤷🏻‍♂️

@soundnvision commented on GitHub (Jan 25, 2022): I tried just the M1 running Monterey and the PC running Win10, PC as server, M1 as client, SSL enabled on both, Barrier 2.3.4 [2022-01-25T17:24:52] INFO: starting server [2022-01-25T17:24:52] INFO: config file: C:/Users/mikef/AppData/Local/Temp/Barrier.AoiHfH [2022-01-25T17:24:52] INFO: log level: INFO [2022-01-25T17:24:52] INFO: service command updated [2022-01-25T17:24:52] INFO: starting new process as privileged user [2022-01-25T17:24:52] INFO: drag and drop enabled [2022-01-25T17:24:52] ERROR: failed to get desktop path, no drop target available, error=2 started server (IPv4/IPv6), waiting for clients server status: active 🤷🏻‍♂️

gitea-mirror commented

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

Author

Owner

@jmahone commented on GitHub (Feb 14, 2022):

Okay, I'm coming back to this issue. I've uninstalled the v2.4.0 cask from my client machine. I did this because I definitely had my server machine working with v2.3.3. I want to try and install, through brew, v2.3.3 on my new client machine. I thought I had ideas on how to do this by working back to the v2.3.3 in the github repo. Unfortunately, I'm not quite there yet. I get a non-checksumed download error when I tried to do it this way, and I wanted to pause and simply ask this:

How does one get a previous version of barrier via homebrew?
Is there a set of instructions someone can provide where I can locate and successfully brew install that previous version?

I'm pretty sure that the v2.3.3 on my client machine will work with the v2.3.3 on my server machine, since that's the setup I had previously (my client machine is a different macOS and instance as noted above). I just need to get the v2.3.3 version on my client machine.

Many thanks for the brew and barrier newbie questions.

@jmahone commented on GitHub (Feb 14, 2022): Okay, I'm coming back to this issue. I've uninstalled the v2.4.0 cask from my client machine. I did this because I definitely had my server machine working with v2.3.3. I want to try and install, through brew, v2.3.3 on my new client machine. I thought I had ideas on how to do this by working back to the v2.3.3 in the github repo. Unfortunately, I'm not quite there yet. I get a non-checksumed download error when I tried to do it this way, and I wanted to pause and simply ask this: 1) How does one get a previous version of barrier via homebrew? 2) Is there a set of instructions someone can provide where I can locate and *successfully* brew install that previous version? I'm pretty sure that the v2.3.3 on my client machine will work with the v2.3.3 on my server machine, since that's the setup I had previously (my client machine is a different macOS and instance as noted above). I just need to get the v2.3.3 version on my client machine. Many thanks for the brew and barrier newbie questions.

gitea-mirror commented

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

Author

Owner

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

Possible workarround for the SSL error on Mac with 2.4.0(I can't check at the moment because I'm just working away, only with my mac. But I've no more the SSL error in my logs, that appeared bevor the connection was established!)

Install with Terminal openssl if missed: brew install openssl
Navigate to the correct directory where you'll need the SSL Certificate: cd /Users/<username>/Library/Application\ Support/barrier/SSL/
install with the following commands the missed certificate
openssl genrsa -out Barrier.key 2048
openssl req -new -key Barrier.key -out Barrier.csr
openssl req -x509 -days 1825 -key Barrier.key -in Barrier.csr -out Barrier.crt
cat Barrier.crt Barrier.key > Barrier.pem
Restart your Barrier app.

I hope it works and will be happy if someone can confirm this.

@kitesurf commented on GitHub (Feb 16, 2022): Possible workarround for the SSL error on Mac with 2.4.0(I can't check at the moment because I'm just working away, only with my mac. But I've no more the SSL error in my logs, that appeared bevor the connection was established!) 1. Install with Terminal openssl if missed: `brew install openssl` 2. Navigate to the correct directory where you'll need the SSL Certificate: `cd /Users/<username>/Library/Application\ Support/barrier/SSL/` 3. install with the following commands the missed certificate `openssl genrsa -out Barrier.key 2048` `openssl req -new -key Barrier.key -out Barrier.csr` `openssl req -x509 -days 1825 -key Barrier.key -in Barrier.csr -out Barrier.crt` `cat Barrier.crt Barrier.key > Barrier.pem` 4. Restart your Barrier app. I hope it works and will be happy if someone can confirm this.

gitea-mirror commented

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

Author

Owner

@e-dard commented on GitHub (Feb 18, 2022):

Hey @kitesurf I just decided to try out Barrier 2.4 on two Macs (server running Big Sur, and client running Catalina).

I immediately hit the SSL certificate issue in the logs. I followed your instructions above ☝️ and they worked perfectly. Thanks!

@e-dard commented on GitHub (Feb 18, 2022): Hey @kitesurf I just decided to try out Barrier 2.4 on two Macs (server running Big Sur, and client running Catalina). I immediately hit the SSL certificate issue in the logs. I followed your instructions above ☝️ and they worked perfectly. Thanks!

gitea-mirror commented

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

Author

Owner

@zt5 commented on GitHub (Feb 21, 2022):

Possible workarround for the SSL error on Mac with 2.4.0(I can't check at the moment because I'm just working away, only with my mac. But I've no more the SSL error in my logs, that appeared bevor the connection was established!)

Install with Terminal openssl if missed: brew install openssl

Navigate to the correct directory where you'll need the SSL Certificate: cd /Users/<username>/Library/Application\ Support/barrier/SSL/

install with the following commands the missed certificate
openssl genrsa -out Barrier.key 2048
openssl req -new -key Barrier.key -out Barrier.csr
openssl req -x509 -days 1825 -key Barrier.key -in Barrier.csr -out Barrier.crt
cat Barrier.crt Barrier.key > Barrier.pem

Restart your Barrier app.

I hope it works and will be happy if someone can confirm this.

Great, it's working fine

@zt5 commented on GitHub (Feb 21, 2022): > Possible workarround for the SSL error on Mac with 2.4.0(I can't check at the moment because I'm just working away, only with my mac. But I've no more the SSL error in my logs, that appeared bevor the connection was established!) > > 1. Install with Terminal openssl if missed: `brew install openssl` > 2. Navigate to the correct directory where you'll need the SSL Certificate: `cd /Users/<username>/Library/Application\ Support/barrier/SSL/` > 3. install with the following commands the missed certificate > `openssl genrsa -out Barrier.key 2048` > `openssl req -new -key Barrier.key -out Barrier.csr` > `openssl req -x509 -days 1825 -key Barrier.key -in Barrier.csr -out Barrier.crt` > `cat Barrier.crt Barrier.key > Barrier.pem` > 4. Restart your Barrier app. > > I hope it works and will be happy if someone can confirm this. Great, it's working fine

gitea-mirror commented

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

Author

Owner

@iBanJavascript commented on GitHub (Feb 22, 2022):

I've never had any success on my Mac getting Barrier (or Synergy) to work as they should. I'd purchased Synergy early last year, but returned it for a refund b/c a process that should be so simple in theory turned out to be an hours-long headache with no positive resolution.

Even with the above suggestion re: brew install openssl & the commands for the certificate, my error messages upon starting the Barrier server (I have 3 Macs I'm trying to share screen/mouse with [Monterey as Server, Monterey & BigSur as clients]), the log error message is always the same:

started server (IPv4/IPv6), waiting for clients Assertion failed: ([NSThread isMainThread]), function _NSPersistentUIApplicationExplicitlySupportsSecureCoding, file NSPersistentUI.m, line 269. [2022-02-21T16:12:50] ERROR: process exited with error code: 6 [2022-02-21T16:12:50] INFO: detected process not running, auto restarting

The server goes into an endless loop, with the Barrier menu bar icon blinking ad infinitum. I have no idea of how (or if) to proceed. My system is basically stock OS, although I have SIP + Gatekeeper disabled.

@iBanJavascript commented on GitHub (Feb 22, 2022): I've never had any success on my Mac getting Barrier (or Synergy) to work as they should. I'd purchased Synergy early last year, but returned it for a refund b/c a process that should be so simple in theory turned out to be an hours-long headache with no positive resolution. Even with the above suggestion re: `brew install openssl` & the commands for the certificate, my error messages upon starting the Barrier server (I have 3 Macs I'm trying to share screen/mouse with [Monterey as Server, Monterey & BigSur as clients]), the log error message is always the same: `started server (IPv4/IPv6), waiting for clients Assertion failed: ([NSThread isMainThread]), function _NSPersistentUIApplicationExplicitlySupportsSecureCoding, file NSPersistentUI.m, line 269. [2022-02-21T16:12:50] ERROR: process exited with error code: 6 [2022-02-21T16:12:50] INFO: detected process not running, auto restarting` The server goes into an endless loop, with the Barrier menu bar icon blinking ad infinitum. I have no idea of how (or if) to proceed. My system is basically stock OS, although I have SIP + Gatekeeper disabled.

gitea-mirror commented

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

Author

Owner

@jmahone commented on GitHub (Mar 1, 2022):

Okay, so I successfully (not through brew) installed the v2.3.3 dmg directly from the repo.

So, I'm running v2.3.3 on both my original server (macOS 10.14.6 Mojave, which worked fine when I had a different macOS client than the one I now have). My server starts fine and says it is available for client connections.

When I start the v2.3.3 client (macOS v12.1 Monterey), it tells me it is starting, but never gets to the running state. Meanwhile, the server logs show:

[2022-03-01T12:41:39] NOTE: accepted client connection
[2022-03-01T12:41:39] WARNING: a client with name "my-mbp" is already connected
[2022-03-01T12:41:39] NOTE: disconnecting client "my-mbp"
[2022-03-01T12:41:39] NOTE: client "my-mbp" has disconnected

and this cycles endlessly.

So, it appears the server is accepting client connections, the client attempts to connect, but the server thinks it has already connected.

Has anyone seen this previously?

TIA,
Jerry

@jmahone commented on GitHub (Mar 1, 2022): Okay, so I successfully (not through brew) installed the v2.3.3 dmg directly from the repo. So, I'm running v2.3.3 on both my original server (macOS 10.14.6 Mojave, which worked fine when I had a different macOS client than the one I now have). My server starts fine and says it is available for client connections. When I start the v2.3.3 client (macOS v12.1 Monterey), it tells me it is starting, but never gets to the running state. Meanwhile, the server logs show: [2022-03-01T12:41:39] NOTE: accepted client connection [2022-03-01T12:41:39] WARNING: a client with name "my-mbp" is already connected [2022-03-01T12:41:39] NOTE: disconnecting client "my-mbp" [2022-03-01T12:41:39] NOTE: client "my-mbp" has disconnected and this cycles endlessly. So, it appears the server is accepting client connections, the client attempts to connect, but the server thinks it has already connected. Has anyone seen this previously? TIA, Jerry

gitea-mirror commented

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

Author

Owner

@jmahone commented on GitHub (Apr 5, 2022):

Okay, I'm returning back to this problem. I have the following updated configuration:

Currently, on the server (MBP 15” mid-2015, 10.14.6 Mojave, 2.8GHz Intel Core i7), I get this message:

[2022-04-04T11:01:07] NOTE: accepted client connection
[2022-04-04T11:01:07] WARNING: a client with name "my-mbp" is already connected
[2022-04-04T11:01:07] NOTE: disconnecting client "my-mbp"
[2022-04-04T11:01:07] NOTE: client "my-mbp" has disconnected

Currently, on the client (MBP 16” 2021, 12.1 Monterey, Apple M1 Pro), I get this message:

T11:00:44] NOTE: connecting to '192.168.xx.yy': 192.168.xx.xxx:24800
[2022-04-04T11:00:44] ERROR: server already has a connected client with name "my-mbp"
[2022-04-04T11:00:44] WARNING: failed to connect to server: server already has a connected client with our name

I have SSL turned off on both server and client. I did this because I ran into SSL issues, though I eventually was able to generate the pem files and get it squared away, but that was when the client was running 2.4.0 and the server still on 2.3.3. I tried to simply by turning off SSL, and then also by rolling the client back to 2.3.3. Under another client machine, I had all of this working (no SSL and both running 2.3.3). So, because of that, I tried to duplicate those conditions (no SSL, both 2.3.3).

The difference between my previously working configuration and now is that the client is a new machine. It used to be 2018-ish MacBook pro running Monterey, and now my client is noted above: a 2021 mbp running Monterey.

Any suggestions on what steps I can take at this point? It looks like the server is running and awaiting connections, but my client machine never gets past the "Barrier is running" stage.

I appreciate any help anyone can offer in terms of troubleshooting or "hey, I had that problem and here's how I fixed it" advice.

Many thanks,
Jerry

@jmahone commented on GitHub (Apr 5, 2022): Okay, I'm returning back to this problem. I have the following updated configuration: Currently, on the **server** (MBP 15” mid-2015, 10.14.6 Mojave, 2.8GHz Intel Core i7), I get this message: [2022-04-04T11:01:07] NOTE: accepted client connection [2022-04-04T11:01:07] WARNING: a client with name "my-mbp" is already connected [2022-04-04T11:01:07] NOTE: disconnecting client "my-mbp" [2022-04-04T11:01:07] NOTE: client "my-mbp" has disconnected ------------------------------- Currently, on the **client** (MBP 16” 2021, 12.1 Monterey, Apple M1 Pro), I get this message: T11:00:44] NOTE: connecting to '192.168.xx.yy': 192.168.xx.xxx:24800 [2022-04-04T11:00:44] ERROR: server already has a connected client with name "my-mbp" [2022-04-04T11:00:44] WARNING: failed to connect to server: server already has a connected client with our name I have SSL turned off on both server and client. I did this because I ran into SSL issues, though I eventually was able to generate the pem files and get it squared away, but that was when the client was running 2.4.0 and the server still on 2.3.3. I tried to simply by turning off SSL, and then also by rolling the client back to 2.3.3. Under *another client machine*, I had all of this working (no SSL and both running 2.3.3). So, because of that, I tried to duplicate those conditions (no SSL, both 2.3.3). The difference between my previously working configuration and now is that the client is a new machine. It used to be 2018-ish MacBook pro running Monterey, and now my client is noted above: a 2021 mbp running Monterey. Any suggestions on what steps I can take at this point? It looks like the server is running and awaiting connections, but my client machine never gets past the "Barrier is running" stage. I appreciate any help anyone can offer in terms of troubleshooting or "hey, I had that problem and here's how I fixed it" advice. Many thanks, Jerry

gitea-mirror commented

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

Author

Owner

@jmahone commented on GitHub (Apr 11, 2022):

I have (I think) evolved in this troubleshooting procedure to the point where I'm still getting the repeating message noted in my most recent post on this issue:

10:51] INFO: starting server
[2022-04-10T23:10:51] INFO: config file: /private/var/folders/7j/6d3md4151cl3ws9bhyz4kf75v0psl6/T/Barrier.YabilW
[2022-04-10T23:10:51] INFO: log level: INFO
[2022-04-10T23:10:52] INFO: drag and drop enabled
started server (IPv4), waiting for clients
[2022-04-10T23:10:54] NOTE: accepted client connection
[2022-04-10T23:10:54] WARNING: a client with name "jmahonesmbp" is already connected
[2022-04-10T23:10:54] NOTE: disconnecting client "jmahonesmbp"

[2022-04-10T23:10:54] NOTE: client "j-mahones-mbp" has disconnected
[2022-04-10T23:10:55] NOTE: accepted client connection
[2022-04-10T23:10:55] WARNING: a client with name "jmahonesmbp" is already connected
[2022-04-10T23:10:55] NOTE: disconnecting client "jmahonesmbp"
[2022-04-10T23:10:55] NOTE: client "j-mahones-mbp" has disconnected

etc.

On the client I get the same message as noted in the previous message:

T11:00:44] NOTE: connecting to '192.168.xx.yy': 192.168.xx.xxx:24800
[2022-04-04T11:00:44] ERROR: server already has a connected client with name "my-mbp"
[2022-04-04T11:00:44] WARNING: failed to connect to server: server already has a connected client with our name

Is there anyone out there who might have seen this before? The server seems happy and ready to accept client requests. Once I start barrier on my client machine, the server acknowledges it, so it seems the networking is happy. But then it also indicates the connection already exists. I don't understand this, and I can see that once I kill the client barrier app, that no barrier instances are running on the client machine and no connections are made between the client and the server. The server acknowledges this by going back to awaiting client connection with no further mention of my client in the logs.

It's as if when I run the barrier app on my client, it is sending multiple connection requests even after it looks like it connects, but then the server severs the connection(s). I can never move my mouse from the server over to the client.

I used to have this working with a previous client machine (but same server machine). The new client is an M1 mbp. I have turned off SSL on both barrier apps (though I had previously gotten that issue resolved) just to simplify things since my previous configuration didn't have SSL turned on for barrier and all was well.

Any ideas?

@jmahone commented on GitHub (Apr 11, 2022): I have (I think) evolved in this troubleshooting procedure to the point where I'm still getting the repeating message noted in my most recent post on this issue: 10:51] INFO: starting server [2022-04-10T23:10:51] INFO: config file: /private/var/folders/7j/6d3md4151cl3ws9bhyz4kf75v0psl6/T/Barrier.YabilW [2022-04-10T23:10:51] INFO: log level: INFO [2022-04-10T23:10:52] INFO: drag and drop enabled started server (IPv4), waiting for clients [2022-04-10T23:10:54] NOTE: accepted client connection [2022-04-10T23:10:54] WARNING: a client with name "jmahonesmbp" is already connected [2022-04-10T23:10:54] NOTE: disconnecting client "jmahonesmbp" [2022-04-10T23:10:54] NOTE: client "j-mahones-mbp" has disconnected [2022-04-10T23:10:55] NOTE: accepted client connection [2022-04-10T23:10:55] WARNING: a client with name "jmahonesmbp" is already connected [2022-04-10T23:10:55] NOTE: disconnecting client "jmahonesmbp" [2022-04-10T23:10:55] NOTE: client "j-mahones-mbp" has disconnected etc. On the client I get the same message as noted in the previous message: T11:00:44] NOTE: connecting to '192.168.xx.yy': 192.168.xx.xxx:24800 [2022-04-04T11:00:44] ERROR: server already has a connected client with name "my-mbp" [2022-04-04T11:00:44] WARNING: failed to connect to server: server already has a connected client with our name Is there anyone out there who might have seen this before? The server seems happy and ready to accept client requests. Once I start barrier on my client machine, the server acknowledges it, so it seems the networking is happy. But then it also indicates the connection already exists. I don't understand this, and I can see that once I kill the client barrier app, that no barrier instances are running on the client machine and no connections are made between the client and the server. The server acknowledges this by going back to awaiting client connection with no further mention of my client in the logs. It's as if when I run the barrier app on my client, it is sending multiple connection requests even after it looks like it connects, but then the server severs the connection(s). I can never move my mouse from the server over to the client. I used to have this working with a previous client machine (but same server machine). The new client is an M1 mbp. I have turned off SSL on both barrier apps (though I had previously gotten that issue resolved) just to simplify things since my previous configuration didn't have SSL turned on for barrier and all was well. Any ideas?

gitea-mirror commented

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

Author

Owner

@ignitz commented on GitHub (Jul 10, 2022):

Possible workarround for the SSL error on Mac with 2.4.0(I can't check at the moment because I'm just working away, only with my mac. But I've no more the SSL error in my logs, that appeared bevor the connection was established!)

Install with Terminal openssl if missed: brew install openssl

Navigate to the correct directory where you'll need the SSL Certificate: cd /Users/<username>/Library/Application\ Support/barrier/SSL/

install with the following commands the missed certificate
openssl genrsa -out Barrier.key 2048
openssl req -new -key Barrier.key -out Barrier.csr
openssl req -x509 -days 1825 -key Barrier.key -in Barrier.csr -out Barrier.crt
cat Barrier.crt Barrier.key > Barrier.pem

Restart your Barrier app.

I hope it works and will be happy if someone can confirm this.

Thanks, Bro. This work!

@ignitz commented on GitHub (Jul 10, 2022): > Possible workarround for the SSL error on Mac with 2.4.0(I can't check at the moment because I'm just working away, only with my mac. But I've no more the SSL error in my logs, that appeared bevor the connection was established!) > > 1. Install with Terminal openssl if missed: `brew install openssl` > 2. Navigate to the correct directory where you'll need the SSL Certificate: `cd /Users/<username>/Library/Application\ Support/barrier/SSL/` > 3. install with the following commands the missed certificate > `openssl genrsa -out Barrier.key 2048` > `openssl req -new -key Barrier.key -out Barrier.csr` > `openssl req -x509 -days 1825 -key Barrier.key -in Barrier.csr -out Barrier.crt` > `cat Barrier.crt Barrier.key > Barrier.pem` > 4. Restart your Barrier app. > > I hope it works and will be happy if someone can confirm this. Thanks, Bro. This work!

gitea-mirror commented

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

Author

Owner

@Ben-Down commented on GitHub (Mar 21, 2023):

Hi I’m hoping that some kind person can help me .

Ive recently bought my first Mac computer ( Mac Mini ) running Mojave 10.14.6 and installed
Barrier Version 2.4.0 release 3e0d758b / Build Date …. 1 November 2021 and its set to … Client ( use another computers’s mouse and keyboard )

I have turned off the Little Snitch ( firewall ) on my Mac Mini .

Then I installed the same exact version of Barrier on my laptop running Linux Mint Version 21.1 ( Vera ) . and set it to be the server ( share this computer’s mouse and keyboard ) . I have turned off the Linux Mint Firewall .

Both my Mac Mini and my Linux Mint laptop are connected to the same network using ethernet cables via my Wifi Router .

I have made sure that both Barrier applications on the Mac and Linux Mint have the same IP addresses and port number ( 24799 )

I have made sure that in the Linux Mint Barrier server configuration control panel , both the Blue screens have their correct names.

On my Linux Mint Barrier in the log window it keeps saying ……...

ERROR ssl certificate doesn't exist

On my Mac Mini running Mojave 10.14.6 log window it keeps saying …..

NOTE: connecting to '192.168.1.15': 192.168.1.15:24799
NOTE: disconnected from server

I’m really stuck to know whats going on and hopefully find out here how to fix this ongoing issue .

Thank You

@Ben-Down commented on GitHub (Mar 21, 2023): Hi I’m hoping that some kind person can help me . Ive recently bought my first Mac computer ( Mac Mini ) running Mojave 10.14.6 and installed Barrier Version 2.4.0 release 3e0d758b / Build Date …. 1 November 2021 and its set to … Client ( use another computers’s mouse and keyboard ) I have turned off the Little Snitch ( firewall ) on my Mac Mini . Then I installed the same exact version of Barrier on my laptop running Linux Mint Version 21.1 ( Vera ) . and set it to be the server ( share this computer’s mouse and keyboard ) . I have turned off the Linux Mint Firewall . Both my Mac Mini and my Linux Mint laptop are connected to the same network using ethernet cables via my Wifi Router . I have made sure that both Barrier applications on the Mac and Linux Mint have the same IP addresses and port number ( 24799 ) I have made sure that in the Linux Mint Barrier server configuration control panel , both the Blue screens have their correct names. On my Linux Mint Barrier in the log window it keeps saying ……... ERROR ssl certificate doesn't exist On my Mac Mini running Mojave 10.14.6 log window it keeps saying ….. NOTE: connecting to '192.168.1.15': 192.168.1.15:24799 NOTE: disconnected from server I’m really stuck to know whats going on and hopefully find out here how to fix this ongoing issue . Thank You