github-starred/barrier

Fork 0

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

[GH-ISSUE #245] barrierc usage #196

New issue

Closed

opened 2026-05-05 05:39:36 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:39:36 -06:00

Owner

Originally created by @marcelinomalmeidan on GitHub (Jan 31, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/245

Operating Systems

Server: Ubuntu 16.04 LTS (name: saramago, IP: 192.168.1.200)
Client: Ubuntu 16.04 LTS (name: tegra-ubuntu, IP: 192.168.1.2)

Barrier version: origin/master

Question

I just can't make barrierc work. It seems obvious based on the documentation, but I have tried many things without success.
I can make barrier work by using the GUI. On the server side, I start the server, on the client side I start a client choosing the server's IP: 192.168.1.200
However, when it comes to running barrierc, nothing happens. The terminal gets blocked (I can't type anything in it), and it just freezes there.
Commands that I have tried on the client side:

./barrierc 192.168.1.200
./barrierc [192.168.1.200]
./barrierc [192.168.1.200][:24800]
./barrierc [192.168.1.200]:24800
./barrierc 192.168.1.200:24800
./barrierc --name saramago 192.168.1.200:24800
./barrierc --name saramago [192.168.1.200][:24800]

Is any of those commands supposed to work?

I have also tried switching the client with the server (making the client on 192.168.1.200 and the server on 192.168.1.2) with no success either.

Originally created by @marcelinomalmeidan on GitHub (Jan 31, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/245 ### Operating Systems ### Server: Ubuntu 16.04 LTS (name: saramago, IP: 192.168.1.200) Client: Ubuntu 16.04 LTS (name: tegra-ubuntu, IP: 192.168.1.2) Barrier version: origin/master ### Question ### I just can't make barrierc work. It seems obvious based on the documentation, but I have tried many things without success. I can make barrier work by using the GUI. On the server side, I start the server, on the client side I start a client choosing the server's IP: 192.168.1.200 However, when it comes to running barrierc, nothing happens. The terminal gets blocked (I can't type anything in it), and it just freezes there. Commands that I have tried on the client side: ``` ./barrierc 192.168.1.200 ./barrierc [192.168.1.200] ./barrierc [192.168.1.200][:24800] ./barrierc [192.168.1.200]:24800 ./barrierc 192.168.1.200:24800 ./barrierc --name saramago 192.168.1.200:24800 ./barrierc --name saramago [192.168.1.200][:24800] ``` Is any of those commands supposed to work? I have also tried switching the client with the server (making the client on 192.168.1.200 and the server on 192.168.1.2) with no success either.

gitea-mirror closed this issue

2026-05-05 05:39:38 -06:00

gitea-mirror commented

2026-05-05 05:39:41 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jan 31, 2019):

Are you using SSL?

@AdrianKoshka commented on GitHub (Jan 31, 2019): Are you using SSL?

gitea-mirror commented

2026-05-05 05:39:43 -06:00

Author

Owner

@marcelinomalmeidan commented on GitHub (Jan 31, 2019):

Looks like you've nailed it. I didn't know the server would automatically use SSL by default, so I never chose the --enable-crypto option.

Solution (for future confused people - exchange the IP for your own):

./barrierc -f --enable-crypto 192.168.1.200

@marcelinomalmeidan commented on GitHub (Jan 31, 2019): Looks like you've nailed it. I didn't know the server would automatically use SSL by default, so I never chose the --enable-crypto option. Solution (for future confused people - exchange the IP for your own): ``` ./barrierc -f --enable-crypto 192.168.1.200 ```

gitea-mirror commented

2026-05-05 05:39:45 -06:00

Author

Owner

@superbole commented on GitHub (Oct 21, 2019):

This lead me to my solution too. However, when I ran the exact command as below I received a "bash: ./barrier: No such file or directory" I changed that to:

barrier.barrierc -f --enable-crypto 192.168.1.200

I was also able to add the line above to "Startup Applications" in order to get Barrier to work without a keyboard and mouce on my Ubuntu machine (which is what I have been trying to do off and on for the past week!).

Solution (for future confused people - exchange the IP for your own):
./barrierc -f --enable-crypto 192.168.1.200

@superbole commented on GitHub (Oct 21, 2019): This lead me to my solution too. However, when I ran the exact command as below I received a "bash: ./barrier: No such file or directory" I changed that to: ``` barrier.barrierc -f --enable-crypto 192.168.1.200 ``` I was also able to add the line above to "Startup Applications" in order to get Barrier to work without a keyboard and mouce on my Ubuntu machine (which is what I have been trying to do off and on for the past week!). > Solution (for future confused people - exchange the IP for your own): > > ``` > ./barrierc -f --enable-crypto 192.168.1.200 > ```

No labels

Rows
Columns