github-starred/barrier

Fork 0

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

[GH-ISSUE #987] ERROR: server refused client with name "..." #787

New issue

Closed

opened 2026-05-05 07:07:34 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

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

Owner

Originally created by @bjohas on GitHub (Dec 11, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/987

Describe the bug

When starting barrier, I get:

Qt: Session management error: Could not open network socket
*** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
("-f", "--no-tray", "--debug", "INFO", "--name", "ubuntu", "--enable-crypto", "-c", "/tmp/Barrier.TJ4490", "--address", ":24800")

It seems that clients cannot connect (?)

To Reproduce

I am running barrier server on Ubuntu 20.04/Gnome (installed via snap) and barrier client on MacOS X Catalina.

Steps to reproduce the behavior:

Install barrier on Ubuntu 20.04 via snap
Install barrier on Mac OS X Catalina via homebrew
Run barrier on both machines
I am getting 'barrier is starting' on both machines.
When I enter the IP address of the server into the client, I do get the confirmation of the SSL fingerprint. However, the client screen never appears in the server config.

Expected behavior

Expecting the client to connect to the server :)

I did not install via apt, because that gives version 2.3.2., which seems to suffer a bad memory leak. However, 2.3.2. did start up and was confirmed that barrier is running. However, clients still could not connect. It's possible that there are issues on both sides, but not sure.

I wasn't sure how to install barrier 2.3.3. from the tar.gz, but can try that if somebody gives me a tip.

Originally created by @bjohas on GitHub (Dec 11, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/987 **Describe the bug** When starting barrier, I get: ``` Qt: Session management error: Could not open network socket *** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html> ("-f", "--no-tray", "--debug", "INFO", "--name", "ubuntu", "--enable-crypto", "-c", "/tmp/Barrier.TJ4490", "--address", ":24800") ``` It seems that clients cannot connect (?) **To Reproduce** I am running barrier server on Ubuntu 20.04/Gnome (installed via snap) and barrier client on MacOS X Catalina. Steps to reproduce the behavior: 1. Install barrier on Ubuntu 20.04 via snap 2. Install barrier on Mac OS X Catalina via homebrew 3. Run barrier on both machines 4. I am getting 'barrier is starting' on both machines. 5. When I enter the IP address of the server into the client, I do get the confirmation of the SSL fingerprint. However, the client screen never appears in the server config. **Expected behavior** Expecting the client to connect to the server :) **PS** I did not install via apt, because that gives version 2.3.2., which seems to suffer a bad memory leak. However, 2.3.2. did start up and was confirmed that barrier is running. However, clients still could not connect. It's possible that there are issues on both sides, but not sure. I wasn't sure how to install barrier 2.3.3. from the tar.gz, but can try that if somebody gives me a tip.

gitea-mirror closed this issue

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

gitea-mirror commented

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

Author

Owner

@bjohas commented on GitHub (Dec 11, 2020):

This was an issue with the port being in use - as the logs showed. Incrementing the port by one solved the problem on the server side. However, the client is still unable to connect - I've edited the title of the bug accordingly.

When I inspect the logs on the client, I see

[2020-12-11T00:59:28] NOTE: connecting to '192.168.1.94': 192.168.1.94:24801
[2020-12-11T00:59:28] INFO: OpenSSL 1.1.1g  21 Apr 2020
[2020-12-11T00:59:28] NOTE: server fingerprint: D9:5F:26:78:5B:71:FC:A1:9F:80:DE:C4:46:D1:30:1B:C9:01:87:D9
[2020-12-11T00:59:28] NOTE: trustedServersFilename: /Users/XXX/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt
[2020-12-11T00:59:28] NOTE: Opened trustedServersFilename: /Users/XXX/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt
[2020-12-11T00:59:28] NOTE: Fingerprint matches trusted fingerprint
[2020-12-11T00:59:28] INFO: connected to secure socket
[2020-12-11T00:59:28] INFO: server ssl certificate info: /CN=Barrier
[2020-12-11T00:59:28] INFO: TLS_AES_256_GCM_SHA384  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(256) Mac=AEAD
[2020-12-11T00:59:28] ERROR: server refused client with name "macmini.broadband"
[2020-12-11T00:59:28] WARNING: failed to connect to server: server refused client with our name

@bjohas commented on GitHub (Dec 11, 2020): This was an issue with the port being in use - as the logs showed. Incrementing the port by one solved the problem on the server side. However, the client is still unable to connect - I've edited the title of the bug accordingly. When I inspect the logs on the client, I see ``` [2020-12-11T00:59:28] NOTE: connecting to '192.168.1.94': 192.168.1.94:24801 [2020-12-11T00:59:28] INFO: OpenSSL 1.1.1g 21 Apr 2020 [2020-12-11T00:59:28] NOTE: server fingerprint: D9:5F:26:78:5B:71:FC:A1:9F:80:DE:C4:46:D1:30:1B:C9:01:87:D9 [2020-12-11T00:59:28] NOTE: trustedServersFilename: /Users/XXX/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt [2020-12-11T00:59:28] NOTE: Opened trustedServersFilename: /Users/XXX/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt [2020-12-11T00:59:28] NOTE: Fingerprint matches trusted fingerprint [2020-12-11T00:59:28] INFO: connected to secure socket [2020-12-11T00:59:28] INFO: server ssl certificate info: /CN=Barrier [2020-12-11T00:59:28] INFO: TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD [2020-12-11T00:59:28] ERROR: server refused client with name "macmini.broadband" [2020-12-11T00:59:28] WARNING: failed to connect to server: server refused client with our name ```

gitea-mirror commented

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

Author

Owner

@bjohas commented on GitHub (Dec 11, 2020):

OK, right - so I basically did not know how to use this app :) My apologies.

I had to add the client name into the server config, and then reload the server - then it worked.

This app is just so very cool - thank you to the devs and maintainers!!

@bjohas commented on GitHub (Dec 11, 2020): OK, right - so I basically did not know how to use this app :) My apologies. I had to add the client name into the server config, and then reload the server - then it worked. This app is just so very cool - thank you to the devs and maintainers!!

gitea-mirror commented

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

Author

Owner

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

OK, right - so I basically did not know how to use this app :) My apologies.

I had to add the client name into the server config, and then reload the server - then it worked.

This app is just so very cool - thank you to the devs and maintainers!!

Thank you, followed by your tips, I fixed my issue. Great job!

@Doublefire-Chen commented on GitHub (Jun 9, 2022): > OK, right - so I basically did not know how to use this app :) My apologies. > > I had to add the client name into the server config, and then reload the server - then it worked. > > This app is just so very cool - thank you to the devs and maintainers!! Thank you, followed by your tips, I fixed my issue. Great job!

No labels

Rows
Columns