github-starred/barrier

Fork 0

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

[GH-ISSUE #816] Cannot connect to Linux Server from Mac Client #646

New issue

Open

opened 2026-05-05 06:50:12 -06:00 by gitea-mirror · 12 comments

gitea-mirror commented

2026-05-05 06:50:12 -06:00

Owner

Originally created by @UpasanaSridhar on GitHub (Jul 27, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/816

Operating Systems

Server: Ubuntu 18.04

Client: mac OS 10.15.3

Barrier Version

2.3.3

Steps to reproduce bug

1.Check server on the linux machine, and client on the mac.

Reload.
Connection always times out.

Other info

I tried using different ports.
I can connect using Windows.
It seemed to work the first time I launched.
It works with mac as server and linux as client (using it right now)
It would be great to find a fix.
The versions are the same upto the 2.3.3, the linux has some string that begins with a g and the man version starts with 'release'. I don't know if this is the problem.

Thank you in advance!

Originally created by @UpasanaSridhar on GitHub (Jul 27, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/816 ### Operating Systems ### Server: Ubuntu 18.04 Client: mac OS 10.15.3 ### Barrier Version ### 2.3.3 ### Steps to reproduce bug ### 1.Check server on the linux machine, and client on the mac. 2. Reload. 3. Connection always times out. ### Other info ### I tried using different ports. I can connect using Windows. It seemed to work the first time I launched. It works with mac as server and linux as client (using it right now) It would be great to find a fix. The versions are the same upto the 2.3.3, the linux has some string that begins with a g and the man version starts with 'release'. I don't know if this is the problem. Thank you in advance!

gitea-mirror commented

2026-05-05 06:50:15 -06:00

Author

Owner

@martinmenchon commented on GitHub (Jul 27, 2020):

I have the same config and I had the same problems. Try to configure monitors in server machine with the corresponding system name of the client. Try to use a simple name, nothing too complex. Reload and that's all

@martinmenchon commented on GitHub (Jul 27, 2020): I have the same config and I had the same problems. Try to configure monitors in server machine with the corresponding system name of the client. Try to use a simple name, nothing too complex. Reload and that's all

gitea-mirror commented

2026-05-05 06:50:17 -06:00

Author

Owner

@UpasanaSridhar commented on GitHub (Jul 27, 2020):

I tried that, didn't work.
shorter name for the client, manual set up on the server, reloaded both.
Still timing out

@UpasanaSridhar commented on GitHub (Jul 27, 2020): I tried that, didn't work. shorter name for the client, manual set up on the server, reloaded both. Still timing out

gitea-mirror commented

2026-05-05 06:50:21 -06:00

Author

Owner

@shymega commented on GitHub (Jul 27, 2020):

What do you mean by this?

the linux has some string that begins with a g and the man version
starts with 'release'. I don't know if this is the problem.

The man page has nothing to do with your issue, but this, if it is a
mistake on my part, should be rectified..

Thanks.

On this date - Sun, Jul 26, 2020 at 08:38:30PM -0700, UpasanaSridhar wrote:

Operating Systems

Server: Ubuntu 18.04

Client: mac OS 10.15.3

Barrier Version

2.3.3

Steps to reproduce bug

1.Check server on the linux machine, and client on the mac.

Reload.

Connection always times out.

Other info

I tried using different ports.
I can connect using Windows.
It seemed to work the first time I launched.
It works with mac as server and linux as client (using it right now)
It would be great to find a fix.
The versions are the same upto the 2.3.3, the linux has some string that begins with a g and the man version starts with 'release'. I don't know if this is the problem.

Thank you in advance!

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/816

--
Kind regards,
Dom Rodriguez (shymega)

@shymega commented on GitHub (Jul 27, 2020): What do you mean by this? > the linux has some string that begins with a g and the man version > starts with 'release'. I don't know if this is the problem. The man page has nothing to do with your issue, but this, if it is a mistake on my part, should be rectified.. Thanks. On this date - Sun, Jul 26, 2020 at 08:38:30PM -0700, UpasanaSridhar wrote: > ### Operating Systems ### > > Server: Ubuntu 18.04 > > Client: mac OS 10.15.3 > > > ### Barrier Version ### > 2.3.3 > > > ### Steps to reproduce bug ### > > 1.Check server on the linux machine, and client on the mac. > > 2. Reload. > > 3. Connection always times out. > > > ### Other info ### > I tried using different ports. > I can connect using Windows. > It seemed to work the first time I launched. > It works with mac as server and linux as client (using it right now) > It would be great to find a fix. > The versions are the same upto the 2.3.3, the linux has some string that begins with a g and the man version starts with 'release'. I don't know if this is the problem. > > Thank you in advance! > > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/debauchee/barrier/issues/816 -- Kind regards, Dom Rodriguez (shymega)

gitea-mirror commented

2026-05-05 06:50:23 -06:00

Author

Owner

@UpasanaSridhar commented on GitHub (Jul 29, 2020):

That was a typo, my bad!
I meant the Mac version

@UpasanaSridhar commented on GitHub (Jul 29, 2020): That was a typo, my bad! I meant the Mac version

gitea-mirror commented

2026-05-05 06:50:25 -06:00

Author

Owner

@UpasanaSridhar commented on GitHub (Jul 29, 2020):

I still have the issue though

@UpasanaSridhar commented on GitHub (Jul 29, 2020): I still have the issue though

gitea-mirror commented

2026-05-05 06:50:28 -06:00

Author

Owner

@shymega commented on GitHub (Jul 29, 2020):

OK, but that doesn't really answer the question regarding the rest of your comment. What do you mean about the string that "begins with a g" (on Linux), and with the Mac string?

Your bug is still acknowledged, but this sounds like something I should fix too. Cheers.

@shymega commented on GitHub (Jul 29, 2020): OK, but that doesn't really answer the question regarding the _rest of_ your comment. What do you mean about the string that "begins with a g" (on Linux), and with the Mac string? Your bug is still acknowledged, but this sounds like something I should fix too. Cheers.

gitea-mirror commented

2026-05-05 06:50:29 -06:00

Author

Owner

@loopingz commented on GitHub (Jul 30, 2020):

I have similar issue and it seems to be caused by

[2020-07-30T16:44:23] ERROR: failed to accept secure socket
[2020-07-30T16:44:59] NOTE: new client disconnected
[2020-07-30T16:45:04] INFO: OpenSSL 1.1.1f  31 Mar 2020
[2020-07-30T16:45:04] ERROR: ssl error occurred (system call failure)
[2020-07-30T16:45:04] ERROR: failed to accept secure socket
[2020-07-30T16:45:04] INFO: client connection may not be secure

@loopingz commented on GitHub (Jul 30, 2020): I have similar issue and it seems to be caused by ``` [2020-07-30T16:44:23] ERROR: failed to accept secure socket [2020-07-30T16:44:59] NOTE: new client disconnected [2020-07-30T16:45:04] INFO: OpenSSL 1.1.1f 31 Mar 2020 [2020-07-30T16:45:04] ERROR: ssl error occurred (system call failure) [2020-07-30T16:45:04] ERROR: failed to accept secure socket [2020-07-30T16:45:04] INFO: client connection may not be secure ```

gitea-mirror commented

2026-05-05 06:50:32 -06:00

Author

Owner

@loopingz commented on GitHub (Jul 31, 2020):

It is now working without Auto config

@loopingz commented on GitHub (Jul 31, 2020): It is now working without Auto config

gitea-mirror commented

2026-05-05 06:50:35 -06:00

Author

Owner

@FrankelJb commented on GitHub (Jan 20, 2021):

I'm experiencing a similar issue since updating my Mac to Big Sur. Barrier was working before the update.

My configuration is Mac server and Solus client. This is the error I encounter:

[2021-01-20T14:32:19] ERROR: ssl error occurred (system call failure)
[2021-01-20T14:32:19] ERROR: failed to accept secure socket
[2021-01-20T14:32:19] INFO: client connection may not be secure
[2021-01-20T14:32:20] INFO: OpenSSL 1.1.1g 21 Apr 2020
[2021-01-20T14:32:20] INFO: OpenSSL 1.1.1g 21 Apr 2020

@FrankelJb commented on GitHub (Jan 20, 2021): I'm experiencing a similar issue since updating my Mac to Big Sur. Barrier was working before the update. My configuration is Mac server and Solus client. This is the error I encounter: [2021-01-20T14:32:19] ERROR: ssl error occurred (system call failure) [2021-01-20T14:32:19] ERROR: failed to accept secure socket [2021-01-20T14:32:19] INFO: client connection may not be secure [2021-01-20T14:32:20] INFO: OpenSSL 1.1.1g 21 Apr 2020 [2021-01-20T14:32:20] INFO: OpenSSL 1.1.1g 21 Apr 2020

gitea-mirror commented

2026-05-05 06:50:36 -06:00

Author

Owner

@cppmx commented on GitHub (Sep 10, 2021):

Has anyone found any solution to this?

I can configure Windows as server and Linux as client and it works fine, but if I put Linux as server and windows as client then they cannot connect.

In the server log it only says "Waiting for clients", and in the client's log the error is "NG: failed to connect to the server: Time out".

@cppmx commented on GitHub (Sep 10, 2021): Has anyone found any solution to this? I can configure Windows as server and Linux as client and it works fine, but if I put Linux as server and windows as client then they cannot connect. In the server log it only says "Waiting for clients", and in the client's log the error is "NG: failed to connect to the server: Time out".

gitea-mirror commented

2026-05-05 06:50:38 -06:00

Author

Owner

@m4rtt3 commented on GitHub (Oct 28, 2021):

Has anyone found any solution to this?

I can configure Windows as server and Linux as client and it works fine, but if I put Linux as server and windows as client then they cannot connect.

In the server log it only says "Waiting for clients", and in the client's log the error is "NG: failed to connect to the server: Time out".

@cppmx I'm having exactly the same issue. I am trying to use Barrier 2.3.3 (flatpak) on PopOs 21.04 as a server to connect to Windows 11 as a client. A week ago it was connecting fine, the only difference is that now I have been forced to use internet via USB using Android and that I have randomized my MAC address on both PopOS and Android. Also, I now use Portmaster, but it doesn't seem to be related to the issue. The connection works fine using W11 as the server.
PopOS as server returns waiting for clients, while W11 returns failed to connect to server: Attempt to connect timed out without establishing a connection.
When I ping from PopOS to W11 ip, it works just fine, but when I try to ping vice versa, I get timeout for this request.

@m4rtt3 commented on GitHub (Oct 28, 2021): > Has anyone found any solution to this? > > I can configure Windows as server and Linux as client and it works fine, but if I put Linux as server and windows as client then they cannot connect. > > In the server log it only says "Waiting for clients", and in the client's log the error is "NG: failed to connect to the server: Time out". @cppmx I'm having exactly the same issue. I am trying to use Barrier 2.3.3 (flatpak) on PopOs 21.04 as a server to connect to Windows 11 as a client. A week ago it was connecting fine, the only difference is that now I have been forced to use internet via USB using Android and that I have randomized my MAC address on both PopOS and Android. Also, I now use Portmaster, but it doesn't seem to be related to the issue. The connection works fine using W11 as the server. PopOS as server returns `waiting for clients`, while W11 returns `failed to connect to server: Attempt to connect timed out without establishing a connection`. When I ping from PopOS to W11 ip, it works just fine, but when I try to ping vice versa, I get `timeout for this request`.

gitea-mirror commented

2026-05-05 06:50:38 -06:00

Author

Owner

@Doublefire-Chen commented on GitHub (Jun 9, 2022):

the only difference is that now I have been forced to use internet via USB using Android and that I have randomized my MAC address on both PopOS and Android. Also, I now use Portmaster, but it doesn't seem to be related to the issue. The connection works fine using W11 as the server.
PopOS as server returns waiting for clie

same question I have

@Doublefire-Chen commented on GitHub (Jun 9, 2022): > the only difference is that now I have been forced to use internet via USB using Android and that I have randomized my MAC address on both PopOS and Android. Also, I now use Portmaster, but it doesn't seem to be related to the issue. The connection works fine using W11 as the server. > PopOS as server returns `waiting for clie` same question I have

No labels

Rows
Columns