mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #625] unrecognised client name "etc" check server config #495
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#495
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@dichromatic commented on GitHub (Apr 16, 2020):
apparently it works if my windows is the client and my arch is the server... weird
@dichromatic commented on GitHub (Apr 16, 2020):
nevermind, it worked for a few seconds and dropped off its connection and could never reconnect
@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?
@Gloumi commented on GitHub (Jul 30, 2020):
Same problem here on macOS server/client. Any idea ?
@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.
@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.
@jonathan-mothership commented on GitHub (Aug 11, 2020):
Same issue on my side, wholly new set up, Win10 server, OSX client.
@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).
@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.
@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).
@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?
@itayB commented on GitHub (Dec 23, 2020):
found it! I had to drag another computer icon into the black area and add the client screen name!
@zivc commented on GitHub (Apr 28, 2023):
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
@MadLittleMods commented on GitHub (May 8, 2023):
Also see this duplicate issue: https://github.com/debauchee/barrier/issues/339