github-starred/barrier

Fork 0

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

[GH-ISSUE #272] Help setting up? Limited documentation. #219

New issue

Closed

opened 2026-05-05 05:42:32 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:42:32 -06:00

Owner

Originally created by @chriselrod on GitHub (Mar 25, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/272

Operating Systems

Server: Antergos (Linux x86_64)

Client: Clear Linux

Barrier Version

On both Client and Server:
flatpak, 2.2.0-snapshot-53ebc47a
Build date: Saturday, January 12, 2019

Steps to reproduce bug

Install barrier on server using flatpak.
Install barier on client using flatpak.
Launch barrier on server. Use default configuration settings.
Launch barrier on client. Enter local ip address of server, (re)check Auto config.
Start server, then start client.
See a bunch of ssl errors in log. Disable ssl on server and client. Apply/restart both.
See a bunch of connection refused messages in log.

With Enable SSL:

[2019-03-25T02:06:37] INFO: starting client
[2019-03-25T02:06:37] INFO: config file: /tmp/Barrier.LrWjVV
[2019-03-25T02:06:37] INFO: log level: INFO
[2019-03-25T02:06:37] NOTE: started client
[2019-03-25T02:06:37] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800
[2019-03-25T02:06:37] INFO: OpenSSL 1.1.1a  20 Nov 2018
[2019-03-25T02:06:37] ERROR: ssl error occurred (generic failure)
[2019-03-25T02:06:37] ERROR: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
[2019-03-25T02:06:37] ERROR: failed to connect secure socket
[2019-03-25T02:06:52] WARNING: failed to connect to server: Timed out
[2019-03-25T02:06:53] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800
[2019-03-25T02:06:53] INFO: OpenSSL 1.1.1a  20 Nov 2018
[2019-03-25T02:06:53] ERROR: ssl error occurred (system call failure)
[2019-03-25T02:06:53] ERROR: failed to connect secure socket

Without Enable SSL:

[2019-03-25T02:13:08] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800
[2019-03-25T02:13:08] ERROR: server refused client with name "clr-7b12d38c3bf247448c96becf747df83f"
[2019-03-25T02:13:08] WARNING: failed to connect to server: server refused client with our name
[2019-03-25T02:13:09] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800
[2019-03-25T02:13:09] ERROR: server refused client with name "clr-7b12d38c3bf247448c96becf747df83f"
[2019-03-25T02:13:09] WARNING: failed to connect to server: server refused client with our name

Other info

I do not know how to work around this. I do not know much about networking, beyond simple things like openssh server.
Therefore, this prevents me from using Barrier entirely.

Am I supposed to configure some things, like making the server listen on port 24800? How is the server supposed to recognize the client's name?

Originally created by @chriselrod on GitHub (Mar 25, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/272 ### Operating Systems ### Server: Antergos (Linux x86_64) Client: Clear Linux ### Barrier Version ### On both Client and Server: flatpak, 2.2.0-snapshot-53ebc47a Build date: Saturday, January 12, 2019 ### Steps to reproduce bug ### 1. Install barrier on server using flatpak. 2. Install barier on client using flatpak. 3. Launch barrier on server. Use default configuration settings. 4. Launch barrier on client. Enter local ip address of server, (re)check Auto config. 5. Start server, then start client. 6. See a bunch of ssl errors in log. Disable ssl on server and client. Apply/restart both. 7. See a bunch of connection refused messages in log. With Enable SSL: ``` [2019-03-25T02:06:37] INFO: starting client [2019-03-25T02:06:37] INFO: config file: /tmp/Barrier.LrWjVV [2019-03-25T02:06:37] INFO: log level: INFO [2019-03-25T02:06:37] NOTE: started client [2019-03-25T02:06:37] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800 [2019-03-25T02:06:37] INFO: OpenSSL 1.1.1a 20 Nov 2018 [2019-03-25T02:06:37] ERROR: ssl error occurred (generic failure) [2019-03-25T02:06:37] ERROR: error:1408F10B:SSL routines:ssl3_get_record:wrong version number [2019-03-25T02:06:37] ERROR: failed to connect secure socket [2019-03-25T02:06:52] WARNING: failed to connect to server: Timed out [2019-03-25T02:06:53] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800 [2019-03-25T02:06:53] INFO: OpenSSL 1.1.1a 20 Nov 2018 [2019-03-25T02:06:53] ERROR: ssl error occurred (system call failure) [2019-03-25T02:06:53] ERROR: failed to connect secure socket ``` Without Enable SSL: ``` [2019-03-25T02:13:08] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800 [2019-03-25T02:13:08] ERROR: server refused client with name "clr-7b12d38c3bf247448c96becf747df83f" [2019-03-25T02:13:08] WARNING: failed to connect to server: server refused client with our name [2019-03-25T02:13:09] NOTE: connecting to '192.168.0.5': 192.168.0.5:24800 [2019-03-25T02:13:09] ERROR: server refused client with name "clr-7b12d38c3bf247448c96becf747df83f" [2019-03-25T02:13:09] WARNING: failed to connect to server: server refused client with our name ``` ### Other info ### I do not know how to work around this. I do not know much about networking, beyond simple things like openssh server. Therefore, this prevents me from using Barrier entirely. Am I supposed to configure some things, like making the server listen on port 24800? How is the server supposed to recognize the client's name?

gitea-mirror closed this issue

2026-05-05 05:42:33 -06:00

gitea-mirror commented

2026-05-05 05:42:36 -06:00

Author

Owner

@chriselrod commented on GitHub (Mar 25, 2019):

I am writing this comment with the host keyboard on the client computer. :)

How to fix my problem:

On the server, click the Configure Server... option, and add another screen. Give that screen the client's name.
I am not sure if this is still an issue: https://symless.com/forums/topic/2550-server-refused-client-with-our-name/ but I gave my client a name more sensible than "clr-7b12d38c3bf247448c96becf747df83f" anyway.

That is all it took!

I'm closing this issue so as to not distract from other unresolved issues. Even though just how easy it was to actually get things working reinforces the idea that adding a little more documentation/to the wiki may help a lot.
Or maybe I'm just a little slow to figure things out on my own, ha ha.

Initial impressions are: seems awesome!

@chriselrod commented on GitHub (Mar 25, 2019): I am writing this comment with the host keyboard on the client computer. :) How to fix my problem: 1. On the server, click the Configure Server... option, and add another screen. Give that screen the client's name. 2. I am not sure if this is still an issue: https://symless.com/forums/topic/2550-server-refused-client-with-our-name/ but I gave my client a name more sensible than "clr-7b12d38c3bf247448c96becf747df83f" anyway. That is all it took! I'm closing this issue so as to not distract from other unresolved issues. Even though just how easy it was to actually get things working reinforces the idea that adding a little more documentation/to the wiki may help a lot. Or maybe I'm just a little slow to figure things out on my own, ha ha. Initial impressions are: seems awesome!

gitea-mirror commented

2026-05-05 05:42:39 -06:00

Author

Owner

@anohren commented on GitHub (Nov 20, 2019):

1. add another screen. Give that screen the client's name

When I tried that it only started refusing the connection on the basis that the server already had a client with that name

@anohren commented on GitHub (Nov 20, 2019): > 1. add another screen. Give that screen the client's name When I tried that it only started refusing the connection on the basis that the server already had a client with that name

gitea-mirror commented

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

Author

Owner

@tmaiaroto commented on GitHub (Feb 5, 2020):

This is a really important note! I was just going from two Windows machines and thought this was a firewall issue or something. So glad I found this, thanks!

@tmaiaroto commented on GitHub (Feb 5, 2020): This is a really important note! I was just going from two Windows machines and thought this was a firewall issue or something. So glad I found this, thanks!

gitea-mirror commented

2026-05-05 05:42:43 -06:00

Author

Owner

@hhstore commented on GitHub (Aug 8, 2020):

hey guys.
following my tutorial, can fix this issue.
https://github.com/hhstore/blog/issues/199#issuecomment-670969228

@hhstore commented on GitHub (Aug 8, 2020): - hey guys. - [x] following my tutorial, can fix this issue. - https://github.com/hhstore/blog/issues/199#issuecomment-670969228

gitea-mirror commented

2026-05-05 05:42:45 -06:00

Author

Owner

@anohren commented on GitHub (Aug 8, 2020):

following my tutorial

You haven't written in English.

@anohren commented on GitHub (Aug 8, 2020): > * following my tutorial You haven't written in English.

gitea-mirror commented

2026-05-05 05:42:46 -06:00

Author

Owner

@hhstore commented on GitHub (Aug 9, 2020):

following my tutorial

You haven't written in English.

@anohren sorry for that. it's now written in English.

https://github.com/hhstore/blog/issues/199#issuecomment-670969228

@hhstore commented on GitHub (Aug 9, 2020): > > * following my tutorial > > You haven't written in English. @anohren sorry for that. it's now written in English. https://github.com/hhstore/blog/issues/199#issuecomment-670969228

No labels

Rows
Columns