[GH-ISSUE #1983] Barrier ERROR: error:0A00010B:SSL routines::wrong version number #1451

Open
opened 2026-05-05 07:51:04 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @mmoyer16 on GitHub (Oct 8, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1983

Barrier connecting and disconnecting repeatedly

I've been struggling to get my barrier client to connect to my server. I'm on version 2.4.0 and I am using a windows PC as the server and a mac as the client. The server runs fine but the client is stuck on "barrier is starting". I have the logs of both below...

Server:
[2023-10-07T20:40:09] INFO: log level: INFO [2023-10-07T20:40:09] INFO: service command updated [2023-10-07T20:40:10] INFO: starting new process as privileged user [2023-10-07T20:40:10] INFO: drag and drop enabled started server (IPv4/IPv6), waiting for clients server status: active [2023-10-07T20:40:10] NOTE: accepted client connection [2023-10-07T20:40:10] NOTE: new client disconnected [2023-10-07T20:40:11] NOTE: accepted client connection [2023-10-07T20:40:11] WARNING: unrecognised client name "Matthews-Air", check server config [2023-10-07T20:40:11] NOTE: disconnecting client "Matthews-Air" [2023-10-07T20:40:11] NOTE: client "Matthews-Air" has disconnected [2023-10-07T20:40:12] NOTE: accepted client connection [2023-10-07T20:40:12] WARNING: unrecognised client name "Matthews-Air", check server config [2023-10-07T20:40:12] NOTE: disconnecting client "Matthews-Air" [2023-10-07T20:40:12] NOTE: client "Matthews-Air" has disconnected [2023-10-07T20:40:13] INFO: service command updated [2023-10-07T20:40:13] NOTE: accepted client connection [2023-10-07T20:40:13] WARNING: unrecognised client name "Matthews-Air", check server config [2023-10-07T20:40:13] NOTE: disconnecting client "Matthews-Air" [2023-10-07T20:40:13] NOTE: client "Matthews-Air" has disconnected [2023-10-07T20:40:13] INFO: process started but command is empty, shutting down [2023-10-07T20:40:13] INFO: got ipc shutdown message [2023-10-07T20:40:13] NOTE: stopped server [2023-10-07T20:40:14] INFO: process 4180 was shutdown gracefully

Client:
[2023-10-07T20:40:08] INFO: starting client [2023-10-07T20:40:08] INFO: config file: /private/var/folders/8r/x78nrmfx2t3_fc97x9jl7ssc0000gn/T/Barrier.PEOBIE [2023-10-07T20:40:08] INFO: log level: INFO [2023-10-07T20:40:08] INFO: drag and drop enabled [2023-10-07T20:40:08] NOTE: started client [2023-10-07T20:40:08] NOTE: connecting to '192.168.**.***': 192.168.**.***:24800 [2023-10-07T20:40:08] INFO: OpenSSL 3.0.0 7 sep 2021 [2023-10-07T20:40:08] WARNING: failed to connect to server: Connection refused 2023-10-07 20:40:08.797 barrierc[3104:47136] starting cocoa loop [2023-10-07T20:40:09] NOTE: connecting to '192.168.**.***': 192.168.**.***:24800 [2023-10-07T20:40:09] INFO: OpenSSL 3.0.0 7 sep 2021 [2023-10-07T20:40:09] ERROR: ssl error occurred (generic failure) [2023-10-07T20:40:09] ERROR: error:0A00010B:SSL routines::wrong version number [2023-10-07T20:40:09] ERROR: failed to connect secure socket [2023-10-07T20:40:12] INFO: stopping barrier desktop process [2023-10-07T20:40:17] ERROR: process exited with error code: 9

When I try to have them switch roles with the PC as the client and the Mac as the server, it works fine. I have no clue what could be causing this. Any advice?

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

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

Windows, macOS

What OS versions are you using?

Client: MacOS Ventura 13.4.1
Server: Windows 11

Relevant log output

No response

Any other information

No response

Originally created by @mmoyer16 on GitHub (Oct 8, 2023). Original GitHub issue: https://github.com/debauchee/barrier/issues/1983 ### Barrier connecting and disconnecting repeatedly I've been struggling to get my barrier client to connect to my server. I'm on version 2.4.0 and I am using a windows PC as the server and a mac as the client. The server runs fine but the client is stuck on "barrier is starting". I have the logs of both below... Server: `[2023-10-07T20:40:09] INFO: log level: INFO [2023-10-07T20:40:09] INFO: service command updated [2023-10-07T20:40:10] INFO: starting new process as privileged user [2023-10-07T20:40:10] INFO: drag and drop enabled started server (IPv4/IPv6), waiting for clients server status: active [2023-10-07T20:40:10] NOTE: accepted client connection [2023-10-07T20:40:10] NOTE: new client disconnected [2023-10-07T20:40:11] NOTE: accepted client connection [2023-10-07T20:40:11] WARNING: unrecognised client name "Matthews-Air", check server config [2023-10-07T20:40:11] NOTE: disconnecting client "Matthews-Air" [2023-10-07T20:40:11] NOTE: client "Matthews-Air" has disconnected [2023-10-07T20:40:12] NOTE: accepted client connection [2023-10-07T20:40:12] WARNING: unrecognised client name "Matthews-Air", check server config [2023-10-07T20:40:12] NOTE: disconnecting client "Matthews-Air" [2023-10-07T20:40:12] NOTE: client "Matthews-Air" has disconnected [2023-10-07T20:40:13] INFO: service command updated [2023-10-07T20:40:13] NOTE: accepted client connection [2023-10-07T20:40:13] WARNING: unrecognised client name "Matthews-Air", check server config [2023-10-07T20:40:13] NOTE: disconnecting client "Matthews-Air" [2023-10-07T20:40:13] NOTE: client "Matthews-Air" has disconnected [2023-10-07T20:40:13] INFO: process started but command is empty, shutting down [2023-10-07T20:40:13] INFO: got ipc shutdown message [2023-10-07T20:40:13] NOTE: stopped server [2023-10-07T20:40:14] INFO: process 4180 was shutdown gracefully` Client: `[2023-10-07T20:40:08] INFO: starting client [2023-10-07T20:40:08] INFO: config file: /private/var/folders/8r/x78nrmfx2t3_fc97x9jl7ssc0000gn/T/Barrier.PEOBIE [2023-10-07T20:40:08] INFO: log level: INFO [2023-10-07T20:40:08] INFO: drag and drop enabled [2023-10-07T20:40:08] NOTE: started client [2023-10-07T20:40:08] NOTE: connecting to '192.168.**.***': 192.168.**.***:24800 [2023-10-07T20:40:08] INFO: OpenSSL 3.0.0 7 sep 2021 [2023-10-07T20:40:08] WARNING: failed to connect to server: Connection refused 2023-10-07 20:40:08.797 barrierc[3104:47136] starting cocoa loop [2023-10-07T20:40:09] NOTE: connecting to '192.168.**.***': 192.168.**.***:24800 [2023-10-07T20:40:09] INFO: OpenSSL 3.0.0 7 sep 2021 [2023-10-07T20:40:09] ERROR: ssl error occurred (generic failure) [2023-10-07T20:40:09] ERROR: error:0A00010B:SSL routines::wrong version number [2023-10-07T20:40:09] ERROR: failed to connect secure socket [2023-10-07T20:40:12] INFO: stopping barrier desktop process [2023-10-07T20:40:17] ERROR: process exited with error code: 9 ` When I try to have them switch roles with the PC as the client and the Mac as the server, it works fine. I have no clue what could be causing this. Any advice? ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Windows, macOS ### What OS versions are you using? Client: MacOS Ventura 13.4.1 Server: Windows 11 ### Relevant log output _No response_ ### Any other information _No response_
Author
Owner

@techgamer730 commented on GitHub (Jan 2, 2024):

Try turning off ssl in barrier settings on both devices, it worked for me

<!-- gh-comment-id:1874244860 --> @techgamer730 commented on GitHub (Jan 2, 2024): Try turning off ssl in barrier settings on both devices, it worked for me
Author
Owner

@everdred commented on GitHub (Jan 4, 2024):

I've been having the same issue with a Mac client, Linux server. @techgamer730 I tried disabling SSL like you suggested and while I think the client reconnects a little more quickly with SSL disabled, I'm still getting the disconnects. And like @Sapphire9344 said, reversing the client/server roles of the two machines fixes the issue.

<!-- gh-comment-id:1877366115 --> @everdred commented on GitHub (Jan 4, 2024): I've been having the same issue with a Mac client, Linux server. @techgamer730 I tried disabling SSL like you suggested and while I think the client reconnects a little more quickly with SSL disabled, I'm still getting the disconnects. And like @Sapphire9344 said, reversing the client/server roles of the two machines fixes the issue.
Author
Owner

@everdred commented on GitHub (Jan 4, 2024):

Just want to add that on #1755 I saw someone suggest that maintaining some other constant network activity on the client mitigates the issue. They did it by running a speedtest, but I'm finding that pinging another host on my LAN every second also works, keeps the disconnects from happening.

<!-- gh-comment-id:1877393013 --> @everdred commented on GitHub (Jan 4, 2024): Just want to add that on #1755 I saw someone suggest that maintaining some other constant network activity on the client mitigates the issue. They did it by running a speedtest, but I'm finding that pinging another host on my LAN every second also works, keeps the disconnects from happening.
Author
Owner

@zyune commented on GitHub (Feb 4, 2024):

I am facing the same problem on my mac as a server and arch linux as a client

<!-- gh-comment-id:1925580698 --> @zyune commented on GitHub (Feb 4, 2024): I am facing the same problem on my mac as a server and arch linux as a client
Author
Owner

@kwisatz commented on GitHub (Mar 1, 2024):

Same here with two linux clients, both Debian 12.5

I would recommend to @Sapphire9344 to retitle this ticket "ERROR: error:0A00010B:SSL routines::wrong version number" which is the underlying problem.

Disabling SSL, as suggested by @techgamer730 and in other posts is not a long-term solution, hardly a work-around in case it's really urgent and blocking that barrier doesn't work.

What we need is to supply the devs with more information under which circumstances this is happening.

In my case, the software versions on both server and client are

  • Debian 12.5
  • barrier: 2.4.0+dfsg-3
  • openssl and libssl3: 3.0.11-1~deb12u2

I have another client that can connect which still uses libssl1.1… I am following up with the possibility that the libssl version is the crux of the problem…

Detailed logs (--debug DEBUG2) from the client that cannot connect with SSL enabled:

[2024-03-01T11:27:35] NOTE: connecting to 'thufir': 10.24.1.141:24800
[2024-03-01T11:27:35] DEBUG: Opening new socket: 43226800
[2024-03-01T11:27:35] INFO: OpenSSL 3.0.11 19 Sep 2023
[2024-03-01T11:27:35] DEBUG1: openSSL : compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -fzero-call-used-regs=used-gpr -DOPENSSL_TLS_SECURITY_LEVEL=2 -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/reproducible-path/openssl-3.0.11=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
[2024-03-01T11:27:35] DEBUG1: openSSL : built on: Mon Oct 23 17:52:22 2023 UTC
[2024-03-01T11:27:35] DEBUG1: openSSL : platform: debian-amd64
[2024-03-01T11:27:35] DEBUG1: OPENSSLDIR: "/usr/lib/ssl"
[2024-03-01T11:27:35] DEBUG1: connecting to server
[2024-03-01T11:27:35] DEBUG2: connecting secure socket
[2024-03-01T11:27:35] ERROR: ssl error occurred (generic failure)
[2024-03-01T11:27:35] ERROR: error:0A00010B:SSL routines::wrong version number
[2024-03-01T11:27:35] ERROR: failed to connect secure socket
[2024-03-01T11:27:50] DEBUG: Closing socket: 43226800
[2024-03-01T11:27:50] DEBUG1: connection timed out
[2024-03-01T11:27:50] WARNING: failed to connect to server: Timed out
[2024-03-01T11:27:50] DEBUG: retry in 1 seconds
<!-- gh-comment-id:1972930576 --> @kwisatz commented on GitHub (Mar 1, 2024): Same here with two linux clients, both Debian 12.5 I would recommend to @Sapphire9344 to retitle this ticket "ERROR: error:0A00010B:SSL routines::wrong version number" which is the underlying problem. Disabling SSL, as suggested by @techgamer730 and in other posts is not a long-term solution, hardly a work-around in case it's really urgent and blocking that barrier doesn't work. What we need is to supply the devs with more information under which circumstances this is happening. In my case, the software versions on both server and client are - Debian `12.5` - barrier: `2.4.0+dfsg-3` - openssl and libssl3: `3.0.11-1~deb12u2` I have another client that can connect which still uses `libssl1.1`… I am following up with the possibility that the libssl version is the crux of the problem… Detailed logs (`--debug DEBUG2`) from the client that cannot connect with SSL enabled: ``` [2024-03-01T11:27:35] NOTE: connecting to 'thufir': 10.24.1.141:24800 [2024-03-01T11:27:35] DEBUG: Opening new socket: 43226800 [2024-03-01T11:27:35] INFO: OpenSSL 3.0.11 19 Sep 2023 [2024-03-01T11:27:35] DEBUG1: openSSL : compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -fzero-call-used-regs=used-gpr -DOPENSSL_TLS_SECURITY_LEVEL=2 -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/reproducible-path/openssl-3.0.11=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 [2024-03-01T11:27:35] DEBUG1: openSSL : built on: Mon Oct 23 17:52:22 2023 UTC [2024-03-01T11:27:35] DEBUG1: openSSL : platform: debian-amd64 [2024-03-01T11:27:35] DEBUG1: OPENSSLDIR: "/usr/lib/ssl" [2024-03-01T11:27:35] DEBUG1: connecting to server [2024-03-01T11:27:35] DEBUG2: connecting secure socket [2024-03-01T11:27:35] ERROR: ssl error occurred (generic failure) [2024-03-01T11:27:35] ERROR: error:0A00010B:SSL routines::wrong version number [2024-03-01T11:27:35] ERROR: failed to connect secure socket [2024-03-01T11:27:50] DEBUG: Closing socket: 43226800 [2024-03-01T11:27:50] DEBUG1: connection timed out [2024-03-01T11:27:50] WARNING: failed to connect to server: Timed out [2024-03-01T11:27:50] DEBUG: retry in 1 seconds ```
Author
Owner

@sandrock commented on GitHub (Jun 3, 2025):

Same here.

OpenSSL 3.0.2; Pop!OS 22.04 LTS; barrier 2.4.0+dfsg-2

<!-- gh-comment-id:2934243016 --> @sandrock commented on GitHub (Jun 3, 2025): Same here. OpenSSL 3.0.2; Pop!OS 22.04 LTS; barrier 2.4.0+dfsg-2
Author
Owner

@nbolton commented on GitHub (Jun 3, 2025):

Please try Deskflow or Input Leap as Barrier is no longer in development.

https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap

Both are compatible with Barrier client/server so you can try on one of your computers.

If this is still an issue in those projects, we would appreciate a cross-post of this issue.

Not sure which to use? The 'Insights' tab of each project may help you decide.

<!-- gh-comment-id:2936681029 --> @nbolton commented on GitHub (Jun 3, 2025): Please try Deskflow or Input Leap as Barrier is no longer in development. https://github.com/deskflow/deskflow https://github.com/input-leap/input-leap Both are compatible with Barrier client/server so you can try on one of your computers. If this is still an issue in those projects, we would appreciate a cross-post of this issue. Not sure which to use? The 'Insights' tab of each project may help you decide.
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#1451
No description provided.