github-starred/barrier

Fork 0

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

[GH-ISSUE #752] GUI works, commandline times out #588

New issue

Closed

opened 2026-05-05 06:43:36 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:43:36 -06:00

Owner

Originally created by @BlueHippoGithub on GitHub (Jun 15, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/752

Operating Systems

Server: Windows

Client: Ubuntu 20.04 on Raspberry Pi4

Barrier Version

Server: 2.3.2-snapshot-210c2b70
Client: 2.3.2-Release-00000000

Steps to reproduce bug

Install server on windows 10
Install client on ubuntu
Use commandline to connect using "barrierc -f 192.168.87.194"
Bug occurs - "WARNING: failed to connect to server: Timed out"

Other info

Is there a way to work around it? Partially in that it works in the gui
Does this bug prevent you from using Barrier entirely? No

Barrier connects properly when using the GUI (Although autoconfig doens't work so I have to type in the IP). As a workaround I added the barrier GUI as a startup application but barrier starts up unconfigured, meaning I have to use a keyboard and mouse to type in the IP and start the barrier client.

If the commandline worked I could get around this issue by specifying the IP of the server in the command.

I have already checked the windows firewall, and used nc to verify the connection works. But of course it does, since it works as intended with the GUI.

Another way for me to work around it is if I could get the GUI to startup with the IP already entered and without having to press "Start" every time.

Originally created by @BlueHippoGithub on GitHub (Jun 15, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/752 ### Operating Systems ### Server: Windows Client: Ubuntu 20.04 on Raspberry Pi4 ### Barrier Version ### Server: 2.3.2-snapshot-210c2b70 Client: 2.3.2-Release-00000000 ### Steps to reproduce bug ### 1. Install server on windows 10 2. Install client on ubuntu 3. Use commandline to connect using "barrierc -f 192.168.87.194" 4. Bug occurs - "WARNING: failed to connect to server: Timed out" ### Other info ### * Is there a way to work around it? Partially in that it works in the gui * Does this bug prevent you from using Barrier entirely? No Barrier connects properly when using the GUI (Although autoconfig doens't work so I have to type in the IP). As a workaround I added the barrier GUI as a startup application but barrier starts up unconfigured, meaning I have to use a keyboard and mouse to type in the IP and start the barrier client. If the commandline worked I could get around this issue by specifying the IP of the server in the command. I have already checked the windows firewall, and used nc to verify the connection works. But of course it does, since it works as intended with the GUI. Another way for me to work around it is if I could get the GUI to startup with the IP already entered and without having to press "Start" every time.

gitea-mirror closed this issue

2026-05-05 06:43:38 -06:00

gitea-mirror commented

2026-05-05 06:43:40 -06:00

Author

Owner

@BlueHippoGithub commented on GitHub (Jun 15, 2020):

Btw the reason for the "f" flag in the command is because otherwise the terminal becomes invisible as mentioned in other issues. With the flag I can see text regarding the connection.

@BlueHippoGithub commented on GitHub (Jun 15, 2020): Btw the reason for the "f" flag in the command is because otherwise the terminal becomes invisible as mentioned in other issues. With the flag I can see text regarding the connection.

gitea-mirror commented

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

Author

Owner

@BlueHippoGithub commented on GitHub (Jun 15, 2020):

Wow I just found a fix....
Looking at the "Creating a systemd service (Linux)" part of the commandline documentation I realized that my command looked a bit different that the one they specified. So I thought why the heck not.

Using this command it works properly!
I just tested it using startup applications in Ubuntu.

barrierc --enable-crypto --display :0 --debug INFO -f 192.168.87.194

Hope it helps out some other folks who are as terrible as me at reading documentation! :D

@BlueHippoGithub commented on GitHub (Jun 15, 2020): Wow I just found a fix.... Looking at the "**Creating a systemd service (Linux)**" part of the commandline documentation I realized that my command looked a bit different that the one they specified. So I thought why the heck not. Using this command it works properly! I just tested it using startup applications in Ubuntu. `barrierc --enable-crypto --display :0 --debug INFO -f 192.168.87.194` Hope it helps out some other folks who are as terrible as me at reading documentation! :D

No labels

Rows
Columns