github-starred/barrier

Fork 0

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

[GH-ISSUE #620] Getting Started Guide? #487

New issue

Open

opened 2026-05-05 06:31:41 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:31:41 -06:00

Owner

Originally created by @pdhixenbaugh on GitHub (Apr 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/620

Operating Systems

Server: Windows 10, Version 1809, Build 17763.1098
Client: Ubuntu 20.04 (beta)

Barrier Version

Server: 2.3.2-snapshot-210c2b70
Client: 2.3.2-Release, Protocol version 1.6

Issue

Not a bug report -- but an attempt to help with documentation.

Context:
I had used free synaptic years and years ago, and remembered it being as easy as typing in IP addresses and being off to the races. However when I tried again,

it wasn't obvious where to input the Client IP into the host configuration
it wasn't obvious that you had to input the client IP, based on the "auto-config" language on the client side
the Auto-Config on the client side half-worked: first the client timed out without connecting, After restarting, it asked to accept the fingerprint, and stalled out at "Barrier is starting". In the logs, it said "server refused client with our name."

Here are just my jotting down how to get started after getting support in #barrier. If this is useful I can properly flesh it out and test it.

Barrier getting started guide

On the Server Machine:
Open Barrier, stop it if it is running
Menus>Barrier>Change Settings, put in a screen name
From the main screen:
"Configure Server"
Drag the client machine next to the server on whichever side you want it, and rename it with its intended screen name.
Menus>Barrier>Save Configuration
From the main screen: "use existing configuration..." and choose the file you made
Start
NOTE: It can also be useful to increase the debug level in settings, and look at the logs via Menu>Barrier>Show Log
On the Client Machine
Open Barrier, stop it if it is running
Menus>Barrier>Change Settings, put in the screen name you used in the server configuration
From the main screen:
"Client (use another computer's mouse and keyboard)"
It is ok to use auto config
Start
NOTE: Check notification areas on both machines to make sure you only have one running on each machine.

Other info

When did the problem start to occur? When I tried to setup Barrier for the first time
Is there a way to work around it? Yes, if you have prior knowledge of how to set up
Does this bug prevent you from using Barrier entirely? Not a bug

Originally created by @pdhixenbaugh on GitHub (Apr 12, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/620 ### Operating Systems ### Server: Windows 10, Version 1809, Build 17763.1098 Client: Ubuntu 20.04 (beta) ### Barrier Version ### Server: 2.3.2-snapshot-210c2b70 Client: 2.3.2-Release, Protocol version 1.6 ### Issue ### Not a bug report -- but an attempt to help with documentation. Context: I had used free synaptic years and years ago, and remembered it being as easy as typing in IP addresses and being off to the races. However when I tried again, * it wasn't obvious where to input the Client IP into the host configuration * it wasn't obvious that you *had* to input the client IP, based on the "auto-config" language on the client side * the Auto-Config on the client side half-worked: first the client timed out without connecting, After restarting, it asked to accept the fingerprint, and stalled out at "Barrier is starting". In the logs, it said "server refused client with our name." Here are just my jotting down how to get started after getting support in #barrier. If this is useful I can properly flesh it out and test it. ## Barrier getting started guide ## 1. On the Server Machine: Open Barrier, stop it if it is running Menus>Barrier>Change Settings, put in a screen name From the main screen: "Configure Server" Drag the client machine next to the server on whichever side you want it, and rename it with its intended screen name. Menus>Barrier>Save Configuration From the main screen: "use existing configuration..." and choose the file you made Start NOTE: It can also be useful to increase the debug level in settings, and look at the logs via Menu>Barrier>Show Log 2. On the Client Machine Open Barrier, stop it if it is running Menus>Barrier>Change Settings, put in the screen name you used in the server configuration From the main screen: "Client (use another computer's mouse and keyboard)" It is ok to use auto config Start NOTE: Check notification areas on both machines to make sure you only have one running on each machine. ### Other info ### * When did the problem start to occur? When I tried to setup Barrier for the first time * Is there a way to work around it? Yes, if you have prior knowledge of how to set up * Does this bug prevent you from using Barrier entirely? Not a bug

gitea-mirror commented

2026-05-05 06:31:45 -06:00

Author

Owner

@ttfreeman commented on GitHub (Apr 27, 2020):

It also needs a getting-started guide for setting up via cli and config files etc.

@ttfreeman commented on GitHub (Apr 27, 2020): It also needs a getting-started guide for setting up via cli and config files etc.

gitea-mirror commented

2026-05-05 06:31:47 -06:00

Author

Owner

@abienz commented on GitHub (Apr 30, 2020):

Thank you for this @pdhixenbaugh I almost gave up thinking it wasn't working, until I found your instructions.

If this information is available in the readme it needs to be highlighted much more, it is unclear how to get started with Barrier.

@abienz commented on GitHub (Apr 30, 2020): Thank you for this @pdhixenbaugh I almost gave up thinking it wasn't working, until I found your instructions. If this information is available in the readme it needs to be highlighted much more, it is unclear how to get started with Barrier.

gitea-mirror commented

2026-05-05 06:31:50 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 24, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 24, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:31:53 -06:00

Author

Owner

@ghost commented on GitHub (Nov 8, 2022):

Following the OP's instructions, I was not able to get it working at first. Then I checked the log and found error messages about the SSL certificate, so I just wanted to chime in with going to "Change Settings" then unchecking the box for "Enable SSL" on both machines was they key for me. Now it is working perfectly! Thanks!

@ghost commented on GitHub (Nov 8, 2022): Following the OP's instructions, I was not able to get it working at first. Then I checked the log and found error messages about the SSL certificate, so I just wanted to chime in with going to "Change Settings" then unchecking the box for "Enable SSL" on both machines was they key for me. Now it is working perfectly! Thanks!

gitea-mirror commented

2026-05-05 06:31:56 -06:00

Author

Owner

@sajidahamed-git commented on GitHub (Jan 3, 2023):

Following the OP's instructions, I was not able to get it working at first. Then I checked the log and found error messages about the SSL certificate, so I just wanted to chime in with going to "Change Settings" then unchecking the box for "Enable SSL" on both machines was they key for me. Now it is working perfectly! Thanks!

thank you! worked for me after seeing your comment. But were you able to use it with SSL enabled?

@sajidahamed-git commented on GitHub (Jan 3, 2023): > Following the OP's instructions, I was not able to get it working at first. Then I checked the log and found error messages about the SSL certificate, so I just wanted to chime in with going to "Change Settings" then unchecking the box for "Enable SSL" on both machines was they key for me. Now it is working perfectly! Thanks! thank you! worked for me after seeing your comment. But were you able to use it with SSL enabled?

gitea-mirror commented

2026-05-05 06:31:58 -06:00

Author

Owner

@eruber commented on GitHub (Jan 13, 2023):

It is also worth mentioning that depending on how the system's firewall is configured, you may have to allow port access. I had to open port 24800 on Zorin OS (Ubuntu) in order to get the Barrier server to accept a Barrier client connection.

@eruber commented on GitHub (Jan 13, 2023): It is also worth mentioning that depending on how the system's firewall is configured, you may have to allow port access. I had to open port 24800 on Zorin OS (Ubuntu) in order to get the Barrier server to accept a Barrier client connection.