github-starred/barrier

Fork 0

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

[GH-ISSUE #780] cannot get barrier to work (Linux/Linux) #614

New issue

Open

opened 2026-05-05 06:47:12 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 06:47:12 -06:00

Owner

Originally created by @Rosika2 on GitHub (Jul 5, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/780

Operating Systems

Server: Linux/Lubuntu 18.04.4 LTS, 64 bit

Client: Linux/Lubuntu 20.04 LTS, 64 bit

Barrier Version

2.3.2

When configuring the server "SSL Fingerprint" remains empty, the same with the client. The rest of the configuation went well. But on the client the "apply" button remains greyed out and is thus not functional.
So barrier doesn´t work.

When stating it from the server via terminal I get the messages:

QApplication: invalid style override passed, ignoring it.
*** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
("-f", "--no-tray", "--debug", "INFO", "--name", "rosika-Lenovo-H520e", "--enable-crypto", "-c", "/tmp/Barrier.J12160", "--address", ":24800")

The logs on the client say:

Failed to connect to server: Network is unreachable.

Other info

Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? Yes

Any help is much appreciated.
Tnx a lot.
Rosika

Originally created by @Rosika2 on GitHub (Jul 5, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/780 ### Operating Systems ### Server: Linux/Lubuntu 18.04.4 LTS, 64 bit Client: Linux/Lubuntu 20.04 LTS, 64 bit ### Barrier Version ### 2.3.2 When configuring the server "SSL Fingerprint" remains empty, the same with the client. The rest of the configuation went well. But on the client the "apply" button remains greyed out and is thus not functional. So barrier doesn´t work. When stating it from the **server** via terminal I get the messages: ``` QApplication: invalid style override passed, ignoring it. *** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html> ("-f", "--no-tray", "--debug", "INFO", "--name", "rosika-Lenovo-H520e", "--enable-crypto", "-c", "/tmp/Barrier.J12160", "--address", ":24800") ``` The logs on the **client** say: `Failed to connect to server: Network is unreachable. ` ### Other info ### * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes Any help is much appreciated. Tnx a lot. Rosika

gitea-mirror commented

2026-05-05 06:47:14 -06:00

Author

Owner

@verajosemanuel commented on GitHub (Jul 7, 2020):

same error here. Got stuck on "starting". Disabled any firewall to no avail. My message is same as yours:

`*** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.

*** WARNING *** Please fix your application to use the native API of Avahi!

*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html

("-f", "--no-tray", "--debug", "INFO", "--name", "joe-ThinkPad", "--enable-crypto", "--log", "/var/log/barrier.log", "-c", "/home/joe/barrier.conf", "--address", ":24800")`

@verajosemanuel commented on GitHub (Jul 7, 2020): same error here. Got stuck on "starting". Disabled any firewall to no avail. My message is same as yours: `*** WARNING *** The program 'barrier' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html> ("-f", "--no-tray", "--debug", "INFO", "--name", "joe-ThinkPad", "--enable-crypto", "--log", "/var/log/barrier.log", "-c", "/home/joe/barrier.conf", "--address", ":24800")`

gitea-mirror commented

2026-05-05 06:47:16 -06:00

Author

Owner

@theAkito commented on GitHub (Jul 7, 2020):

@verajosemanuel Which OS are you using, exactly?

@theAkito commented on GitHub (Jul 7, 2020): @verajosemanuel Which OS are you using, exactly?

gitea-mirror commented

2026-05-05 06:47:18 -06:00

Author

Owner

@verajosemanuel commented on GitHub (Jul 12, 2020):

Ubuntu focal fossa

@verajosemanuel commented on GitHub (Jul 12, 2020): Ubuntu focal fossa

gitea-mirror commented

2026-05-05 06:47:21 -06:00

Author

Owner

@perpi commented on GitHub (Aug 28, 2020):

I had same problem; I added 24800 as an allowed port by the command below
firewall-cmd --permanent --add-port=24800/tcp
After a ~~restart/logout~~ reload, the client probably gets running!

Client: Archlinux & Server: CentOS 8; Version: 2.3.3

@perpi commented on GitHub (Aug 28, 2020): I had same problem; I added 24800 as an allowed port by the command below `firewall-cmd --permanent --add-port=24800/tcp` After a ~restart/logout~ reload, the client probably gets running! Client: Archlinux & Server: CentOS 8; Version: 2.3.3

gitea-mirror commented

2026-05-05 06:47:23 -06:00

Author

Owner

@shymega commented on GitHub (Aug 28, 2020):

I use firewalld as well. As you made your rule permanent, you need to reload
firewalld to make the permanent rule take affect.

Alternatively, you can run the command again, and omit '--permanent',
which will make the rule take affect immediately.

On this date - Fri, Aug 28, 2020 at 03:36:26AM -0700, perpi wrote:

Same problem; Should we do something special with firewall on the server? While I added 24800 as an allowed port by the command below
firewall-cmd --permanent --add-port=24800/tcp
it still doesn't work until I stop firewalld on the server (via systemctl), then the client gets running!

Client: Archlinux & Server: CentOS 8; Version: 2.3.3

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/780#issuecomment-682454751

--
Kind regards,
Dom Rodriguez (shymega)

@shymega commented on GitHub (Aug 28, 2020): I use firewalld as well. As you made your rule permanent, you need to reload firewalld to make the permanent rule take affect. Alternatively, you can run the command again, and omit '--permanent', which will make the rule take affect immediately. On this date - Fri, Aug 28, 2020 at 03:36:26AM -0700, perpi wrote: > ![image](https://user-images.githubusercontent.com/7093244/91548837-4351d480-e93b-11ea-8a8c-8f0e224e1f06.png) > > Same problem; Should we do something special with firewall on the server? While I added 24800 as an allowed port by the command below > `firewall-cmd --permanent --add-port=24800/tcp` > it still doesn't work until I stop firewalld on the server (via systemctl), then the client gets running! > > Client: Archlinux & Server: CentOS 8; Version: 2.3.3 > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/debauchee/barrier/issues/780#issuecomment-682454751 -- Kind regards, Dom Rodriguez (shymega)

gitea-mirror commented

2026-05-05 06:47:25 -06:00

Author

Owner

@Tropicananass commented on GitHub (Mar 22, 2021):

Using Fedora with firewalld enbaled by default. I have created a firewalld service /etc/firewalld/services/barrier.xml

<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>Barrier Server</short>
  <description>Barrier is software that allow you to use a single keyboard and mouse to control multiple computers</description>
  <port port="24800" protocol="tcp"/>
</service>

and use this command (as root) to enable it : firewall-cmd --permanent --zone=public --add-service=barrier
It could be useful to include it in the fedora build but I have no idea on how to do this.

@Tropicananass commented on GitHub (Mar 22, 2021): Using Fedora with firewalld enbaled by default. I have created a firewalld service `/etc/firewalld/services/barrier.xml` ~~~xml <?xml version="1.0" encoding="utf-8"?> <service> <short>Barrier Server</short> <description>Barrier is software that allow you to use a single keyboard and mouse to control multiple computers</description> <port port="24800" protocol="tcp"/> </service> ~~~ and use this command (as root) to enable it : `firewall-cmd --permanent --zone=public --add-service=barrier` It could be useful to include it in the fedora build but I have no idea on how to do this.

gitea-mirror commented

2026-05-05 06:47:27 -06:00

Author

Owner

@shymega commented on GitHub (Mar 22, 2021):

Service LGTM.

The only thing I'd like is for the barrier.xml file to be targeted in the /usr/lib/firewalld/services directory, instead of /etc/firewalld/services.

In terms of packaging, generally, RPMs are built by the package maintainers of distros - in your case, Fedora. I would put this service in /res/ from the Git repository root for now. Could you make a PR with these parameters?

Thanks for your contribution!

@shymega commented on GitHub (Mar 22, 2021): Service LGTM. The only thing I'd like is for the `barrier.xml` file to be targeted in the `/usr/lib/firewalld/services` directory, instead of `/etc/firewalld/services`. In terms of packaging, generally, RPMs are built by the package maintainers of distros - in your case, Fedora. I would put this service in `/res/` from the Git repository root for now. Could you make a PR with these parameters? Thanks for your contribution!

gitea-mirror commented

2026-05-05 06:47:28 -06:00

Author

Owner

@metal3d commented on GitHub (Nov 3, 2022):

There is already a Synergy file to allow access:

cat /usr/lib/firewalld/services/synergy.xml 
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>Synergy</short>
  <description>Synergy lets you easily share your mouse and keyboard between multiple computers, where each computer has its 
own display. No special hardware is required, all you need is a local area network. Synergy is supported on Windows, Mac OS X
 and Linux. Redirecting the mouse and keyboard is as simple as moving the mouse off the edge of your screen.</description>
  <port protocol="tcp" port="24800"/>
</service>

So, allowing this in default zone should work, it doesn't. I need to stop firewalld, connection barrier, and then restart the firewall (so the established connections are not stopped)

I really don't undestand why it refuse to connect even when the port is allowed (permanently or for the session)

@metal3d commented on GitHub (Nov 3, 2022): There is already a Synergy file to allow access: ``` cat /usr/lib/firewalld/services/synergy.xml <?xml version="1.0" encoding="utf-8"?> <service> <short>Synergy</short> <description>Synergy lets you easily share your mouse and keyboard between multiple computers, where each computer has its own display. No special hardware is required, all you need is a local area network. Synergy is supported on Windows, Mac OS X and Linux. Redirecting the mouse and keyboard is as simple as moving the mouse off the edge of your screen.</description> <port protocol="tcp" port="24800"/> </service> ``` So, allowing this in default zone **should** work, it doesn't. I need to stop firewalld, connection barrier, and then restart the firewall (so the established connections are not stopped) I really don't undestand why it refuse to connect even when the port is allowed (permanently or for the session)

gitea-mirror commented

2026-05-05 06:47:32 -06:00

Author

Owner

@shymega commented on GitHub (Nov 26, 2022):

OK, thanks for letting us know about the Synergy service. I've added this to Input Leap's distribution-specific directory in a branch, which will be PR reviewed and merged soon. I don't work on Barrier anymore, but knowing there's a service for firewalld is useful!

@shymega commented on GitHub (Nov 26, 2022): OK, thanks for letting us know about the Synergy service. I've added this to Input Leap's distribution-specific directory in a branch, which will be PR reviewed and merged soon. I don't work on Barrier anymore, but knowing there's a service for `firewalld` is useful!

No labels

Rows
Columns