[GH-ISSUE #625] unrecognised client name "etc" check server config #495

Open
opened 2026-05-05 06:32:10 -06:00 by gitea-mirror · 14 comments
Owner

Originally created by @dichromatic on GitHub (Apr 15, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/625

Server: Windows 10

Client: Arch Linux

Barrier Version 2.3.2

server logs:
[2020-04-16T04:07:17] INFO: process started but command is empty, shutting down
[2020-04-16T04:07:17] INFO: OpenSSL 1.0.2l 25 May 2017
[2020-04-16T04:07:17] INFO: accepted secure socket
[2020-04-16T04:07:17] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD
[2020-04-16T04:07:17] NOTE: accepted client connection
[2020-04-16T04:07:17] WARNING: unrecognised client name "a", check server config
[2020-04-16T04:07:17] NOTE: disconnecting client "a"
[2020-04-16T04:07:17] NOTE: client "a" has disconnected
[2020-04-16T04:07:18] INFO: OpenSSL 1.0.2l 25 May 2017
[2020-04-16T04:07:18] ERROR: ssl error occurred (system call failure)
[2020-04-16T04:07:18] ERROR: eof violates ssl protocol
[2020-04-16T04:07:18] ERROR: failed to accept secure socket
[2020-04-16T04:07:18] INFO: client connection may not be secure

ive done the normal steps of adding the client with the exact name in the configuration, but this error still comes up. i have also tried to do it with an alias which did not work. i am not able to connect to the server at all, just stuck on "barrier is starting". i have also saved and loaded from a configuration, and changed firewall settings serverside.

Originally created by @dichromatic on GitHub (Apr 15, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/625 Server: Windows 10 Client: Arch Linux Barrier Version 2.3.2 server logs: [2020-04-16T04:07:17] INFO: process started but command is empty, shutting down [2020-04-16T04:07:17] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-04-16T04:07:17] INFO: accepted secure socket [2020-04-16T04:07:17] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2020-04-16T04:07:17] NOTE: accepted client connection [2020-04-16T04:07:17] WARNING: unrecognised client name "a", check server config [2020-04-16T04:07:17] NOTE: disconnecting client "a" [2020-04-16T04:07:17] NOTE: client "a" has disconnected [2020-04-16T04:07:18] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-04-16T04:07:18] ERROR: ssl error occurred (system call failure) [2020-04-16T04:07:18] ERROR: eof violates ssl protocol [2020-04-16T04:07:18] ERROR: failed to accept secure socket [2020-04-16T04:07:18] INFO: client connection may not be secure ive done the normal steps of adding the client with the exact name in the configuration, but this error still comes up. i have also tried to do it with an alias which did not work. i am not able to connect to the server at all, just stuck on "barrier is starting". i have also saved and loaded from a configuration, and changed firewall settings serverside.
gitea-mirror added the
macOS
bug
windows
linux
from release
labels 2026-05-05 06:32:10 -06:00
Author
Owner

@dichromatic commented on GitHub (Apr 16, 2020):

apparently it works if my windows is the client and my arch is the server... weird

<!-- gh-comment-id:614382544 --> @dichromatic commented on GitHub (Apr 16, 2020): apparently it works if my windows is the client and my arch is the server... weird
Author
Owner

@dichromatic commented on GitHub (Apr 16, 2020):

apparently it works if my windows is the client and my arch is the server... weird

nevermind, it worked for a few seconds and dropped off its connection and could never reconnect

<!-- gh-comment-id:614382925 --> @dichromatic commented on GitHub (Apr 16, 2020): > apparently it works if my windows is the client and my arch is the server... weird nevermind, it worked for a few seconds and dropped off its connection and could never reconnect
Author
Owner

@andrew-linck commented on GitHub (Apr 18, 2020):

I need help on this too. I'm getting the same error @shigerumi have you figured it out?

<!-- gh-comment-id:615972276 --> @andrew-linck commented on GitHub (Apr 18, 2020): I need help on this too. I'm getting the same error @shigerumi have you figured it out?
Author
Owner

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

Same problem here on macOS server/client. Any idea ?

<!-- gh-comment-id:666263373 --> @Gloumi commented on GitHub (Jul 30, 2020): Same problem here on macOS server/client. Any idea ?
Author
Owner

@dichromatic commented on GitHub (Aug 2, 2020):

I have long stopped using barrier, but after this problem i left it and restarted barrier the next day and it started working again. I have no clue what brought it up.

<!-- gh-comment-id:667665399 --> @dichromatic commented on GitHub (Aug 2, 2020): I have long stopped using barrier, but after this problem i left it and restarted barrier the next day and it started working again. I have no clue what brought it up.
Author
Owner

@shymega commented on GitHub (Aug 4, 2020):

Ugh.. this is a really weird bug. At a quick look, I could say OpenSSL is not reading correctly formed messages, which could be corruption, but as it happens for a fair few people, its difficult to tell.

<!-- gh-comment-id:668687472 --> @shymega commented on GitHub (Aug 4, 2020): Ugh.. this is a really weird bug. At a quick look, I could say OpenSSL is not reading correctly formed messages, which could be corruption, but as it happens for a fair few people, its difficult to tell.
Author
Owner

@jonathan-mothership commented on GitHub (Aug 11, 2020):

Same issue on my side, wholly new set up, Win10 server, OSX client.

<!-- gh-comment-id:672260188 --> @jonathan-mothership commented on GitHub (Aug 11, 2020): Same issue on my side, wholly new set up, Win10 server, OSX client.
Author
Owner

@jonathan-mothership commented on GitHub (Aug 11, 2020):

More info might help: in my setup the client is reaching the server across a NAT due to my configuration (Google Mesh Wifi doesn't support bridge mode when using multiple devices in mesh).

<!-- gh-comment-id:672263987 --> @jonathan-mothership commented on GitHub (Aug 11, 2020): More info might help: in my setup the client is reaching the server across a NAT due to my configuration (Google Mesh Wifi doesn't support bridge mode when using multiple devices in mesh).
Author
Owner

@dlamblin commented on GitHub (Dec 23, 2020):

Same problem of client on Mac 10.14.6 Mojave and server on Windows 10 Pro with Barrier 2.3.3.
Using IP and/or Autoconfig is the same.
Seems like I should manually set something up.
zScaler is installed on the Mac, but direct connections to the server locally seem to work with other software, and logs repeat every 1s with disconnected.

[2020-12-22T19:49:15] INFO: OpenSSL 1.0.2l  25 May 2017
[2020-12-22T19:49:15] INFO: accepted secure socket
[2020-12-22T19:49:15] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2020-12-22T19:49:15] NOTE: accepted client connection
[2020-12-22T19:49:15] WARNING: unrecognised client name "TheMac", check server config
[2020-12-22T19:49:15] NOTE: disconnecting client "TheMac"
[2020-12-22T19:49:15] NOTE: client "TheMac" has disconnected
[2020-12-22T19:49:16] INFO: OpenSSL 1.0.2l  25 May 2017
[2020-12-22T19:49:16] INFO: accepted secure socket
[2020-12-22T19:49:16] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2020-12-22T19:49:16] NOTE: accepted client connection
[2020-12-22T19:49:16] WARNING: unrecognised client name "TheMac", check server config
[2020-12-22T19:49:16] NOTE: disconnecting client "TheMac"
[2020-12-22T19:49:17] NOTE: client "TheMac" has disconnected
<!-- gh-comment-id:749914280 --> @dlamblin commented on GitHub (Dec 23, 2020): Same problem of client on Mac 10.14.6 Mojave and server on Windows 10 Pro with Barrier 2.3.3. Using IP and/or Autoconfig is the same. Seems like I should manually set something up. zScaler is installed on the Mac, but direct connections to the server locally seem to work with other software, and logs repeat every 1s with disconnected. ```[2020-12-22T19:49:14] NOTE: client "TheMac" has disconnected [2020-12-22T19:49:15] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-12-22T19:49:15] INFO: accepted secure socket [2020-12-22T19:49:15] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2020-12-22T19:49:15] NOTE: accepted client connection [2020-12-22T19:49:15] WARNING: unrecognised client name "TheMac", check server config [2020-12-22T19:49:15] NOTE: disconnecting client "TheMac" [2020-12-22T19:49:15] NOTE: client "TheMac" has disconnected [2020-12-22T19:49:16] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-12-22T19:49:16] INFO: accepted secure socket [2020-12-22T19:49:16] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2020-12-22T19:49:16] NOTE: accepted client connection [2020-12-22T19:49:16] WARNING: unrecognised client name "TheMac", check server config [2020-12-22T19:49:16] NOTE: disconnecting client "TheMac" [2020-12-22T19:49:17] NOTE: client "TheMac" has disconnected ```
Author
Owner

@dlamblin commented on GitHub (Dec 23, 2020):

It appears because the configuration wasn't saved (The temporary configuration file required to start barrier can not be written) I had to save one to a user directory and also make sure a screen matching the client name was added ("TheMac" in my case).

<!-- gh-comment-id:749918423 --> @dlamblin commented on GitHub (Dec 23, 2020): It appears because the configuration wasn't saved (The temporary configuration file required to start barrier can not be written) I had to save one to a user directory *and also* make sure a screen matching the client name was added ("TheMac" in my case).
Author
Owner

@itayB commented on GitHub (Dec 23, 2020):

@dlamblin where did you add the client name? I didn't find a place to add it in the server configuration. Can you please guid or add a screenshot?

<!-- gh-comment-id:750042160 --> @itayB commented on GitHub (Dec 23, 2020): @dlamblin where did you add the client name? I didn't find a place to add it in the server configuration. Can you please guid or add a screenshot?
Author
Owner

@itayB commented on GitHub (Dec 23, 2020):

image
found it! I had to drag another computer icon into the black area and add the client screen name!

<!-- gh-comment-id:750044773 --> @itayB commented on GitHub (Dec 23, 2020): ![image](https://user-images.githubusercontent.com/457191/102983279-7fc1c580-4514-11eb-83a5-9cc0470ccca8.png) found it! I had to drag another computer icon into the black area and add the client screen name!
Author
Owner

@zivc commented on GitHub (Apr 28, 2023):

It appears because the configuration wasn't saved (The temporary configuration file required to start barrier can not be written) I had to save one to a user directory and also make sure a screen matching the client name was added ("TheMac" in my case).

This worked for me:
Server - personal laptop macOS Ventura (2018 i7)
Client - work laptop macOS Ventura (M1 Max)

I added the client to the server config using the GUI and then saved the config. Reloaded barrier using the exported config.

Also had to make a PEM on the server and enable SSL both sides

cd /Users/<USER>/Library/Application\ Support/barrier/SSL
openssl req -new -x509 -sha256 -days 999 -nodes -out Barrier.pem -keyout Barrier.pem
<!-- gh-comment-id:1527418374 --> @zivc commented on GitHub (Apr 28, 2023): > It appears because the configuration wasn't saved (The temporary configuration file required to start barrier can not be written) I had to save one to a user directory _and also_ make sure a screen matching the client name was added ("TheMac" in my case). This worked for me: Server - personal laptop macOS Ventura (2018 i7) Client - work laptop macOS Ventura (M1 Max) I added the client to the server config using the GUI and then saved the config. Reloaded barrier using the exported config. Also had to make a PEM on the server and enable SSL both sides ``` cd /Users/<USER>/Library/Application\ Support/barrier/SSL openssl req -new -x509 -sha256 -days 999 -nodes -out Barrier.pem -keyout Barrier.pem ```
Author
Owner

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

Also see this duplicate issue: https://github.com/debauchee/barrier/issues/339

<!-- gh-comment-id:1538770288 --> @MadLittleMods commented on GitHub (May 8, 2023): Also see this duplicate issue: https://github.com/debauchee/barrier/issues/339
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#495
No description provided.