[GH-ISSUE #1922] Stuck on "Barrier is starting"

gitea-mirror commented

2026-05-05 07:48:24 -06:00

Owner

Originally created by @gephenzie on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1922

What happened?

New install on two workstations. Both are Ubuntu 22.04.2 LTS. XFCE desktop. "Server" on wired connection, client on WiFi.
Install works well and app fires up. I enter the parameters for the server and (at first) it runs fine.

Initially on the server, when START pressed, it started. On the client, I setup "auto config" and on click of 'start' it hung at "Barrier is starting" and never went further. On server side, client is nowhere to be found.

Next on both I unchecked "Enable SSL", restarted, and still didn't work. On the server, I connected to the wifi and got an IP on it. I restarted it now the server sticks at "Barrier is starting"

Firewall (ufw) on both is disabled (was initially and still is).

I set logging onto debug and when I followed journalctl I get no messages from starting it. I changed it to log to a file and the file never gets created.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Ubuntu package installer apt; package "barrier"

What OSes are you seeing the problem on? (Check all that apply)

Linux

What OS versions are you using?

Ubuntu 22.04.2 LTS with XFCE desktop environment (same on both client and server)

Relevant log output

No response

Any other information

No response

Originally created by @gephenzie on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/debauchee/barrier/issues/1922 ### What happened? New install on two workstations. Both are Ubuntu 22.04.2 LTS. XFCE desktop. "Server" on wired connection, client on WiFi. Install works well and app fires up. I enter the parameters for the server and (at first) it runs fine. Initially on the server, when START pressed, it started. On the client, I setup "auto config" and on click of 'start' it hung at "Barrier is starting" and never went further. On server side, client is nowhere to be found. Next on both I unchecked "Enable SSL", restarted, and still didn't work. On the server, I connected to the wifi and got an IP on it. I restarted it now the server sticks at "Barrier is starting" Firewall (ufw) on both is disabled (was initially and still is). I set logging onto debug and when I followed journalctl I get no messages from starting it. I changed it to log to a file and the file never gets created. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Ubuntu package installer apt; package "barrier" ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? Ubuntu 22.04.2 LTS with XFCE desktop environment (same on both client and server) ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:48:27 -06:00

Author

Owner

@JiffB commented on GitHub (Apr 1, 2023):

On the client, I setup "auto config"

Don't do that, AFAIK it never worked - just check the other possibility and fill the server IP address, it should work at once.

Oh, and make the first connection with at leas a mouse hooked into the client, 'cos it'll ask you if you accept the incoming certificate from the server, click OK and you're done.

@JiffB commented on GitHub (Apr 1, 2023): ```On the client, I setup "auto config"``` Don't do that, AFAIK it never worked - just check the other possibility and fill the server IP address, it should work at once. Oh, and make the first connection with at leas a mouse hooked into the client, 'cos it'll ask you if you accept the incoming certificate from the server, click OK and you're done.

gitea-mirror commented

2026-05-05 07:48:28 -06:00

Author

Owner

@gephenzie commented on GitHub (Apr 3, 2023):

Don't do that, AFAIK it never worked - just check the other possibility and fill the server IP address, it should work at once.

Unfortunately changing this has no effect. I tried both the server's IP addresses and it netted the same result - it sits there at "Barrier is starting" and does not register on the server.

@gephenzie commented on GitHub (Apr 3, 2023): > Don't do that, AFAIK it never worked - just check the other possibility and fill the server IP address, it should work at once. Unfortunately changing this has no effect. I tried both the server's IP addresses and it netted the same result - it sits there at "Barrier is starting" and does not register on the server.

gitea-mirror commented

2026-05-05 07:48:29 -06:00

Author

Owner

@JiffB commented on GitHub (Apr 3, 2023):

On Mon, 03 Apr 2023 08:28:11 -0700
Jeff Henze @.***> wrote:

Don't do that, AFAIK it never worked - just check the other
possibility and fill the server IP address, it should work at once.

Unfortunately changing this has no effect. I tried both the server's
IP addresses and it netted the same result - it sits there at
"Barrier is starting" and does not register on the server.

Hi Jeff,

I just modified the original text as I forgot 2 important steps :

on the client, launch manually barrier and accept the server
certificate,
still on the client but as root, make a copy of the certificate
acceptance:
cp -r /home//.local/share/barrier /root/.local/share/ which
will also accept the server certificate for root.

If these steps aren't done, you're gonna wait forever.

Jean-Yves

@JiffB commented on GitHub (Apr 3, 2023): On Mon, 03 Apr 2023 08:28:11 -0700 Jeff Henze ***@***.***> wrote: > > Don't do that, AFAIK it never worked - just check the other > > possibility and fill the server IP address, it should work at once. > > Unfortunately changing this has no effect. I tried both the server's > IP addresses and it netted the same result - it sits there at > "Barrier is starting" and does not register on the server. > Hi Jeff, I just modified the original text as I forgot 2 important steps : * on the client, launch manually barrier _and_ accept the server certificate, * still on the client but as root, make a copy of the certificate acceptance: cp -r /home/<username>/.local/share/barrier /root/.local/share/ which will also accept the server certificate for root. If these steps aren't done, you're gonna wait forever. Jean-Yves

gitea-mirror commented

2026-05-05 07:48:31 -06:00

Author

Owner

@gephenzie commented on GitHub (Apr 3, 2023):

on the client, launch manually barrier and accept the server
certificate,

I'm unable to get a prompt on the client to accept the (server) certificate. Also, prior I was testing with "Enable SSL" unchecked, which would imply no certificate. So I checked it on both client and server, and still getting the same thing: client sits there at "Barrier is starting", no prompts. When I look in ~/.local/share/ barrier/SSL it's empty.
I also quit Barrier on the client side, restarted it, and same thing. Never a prompt, only "Barrier is starting".

Since you mentioned root and 'manually', I quit on both machines then ran from terminal as root. Same results.

I've got to be missing something

@gephenzie commented on GitHub (Apr 3, 2023): > * on the client, launch manually barrier _and_ accept the server > certificate, I'm unable to get a prompt on the client to accept the (server) certificate. Also, prior I was testing with "Enable SSL" unchecked, which would imply no certificate. So I checked it on both client and server, and still getting the same thing: client sits there at "Barrier is starting", no prompts. When I look in ~/.local/share/ barrier/SSL it's empty. I also quit Barrier on the client side, restarted it, and same thing. Never a prompt, only "Barrier is starting". Since you mentioned root and 'manually', I quit on both machines then ran from terminal as root. Same results. I've got to be missing something

gitea-mirror commented

2026-05-05 07:48:32 -06:00

Author

Owner

@JiffB commented on GitHub (Apr 3, 2023):

On Mon, 03 Apr 2023 11:32:25 -0700
Jeff Henze @.***> wrote:

on the client, launch manually barrier and accept the server
certificate,

I'm unable to get a prompt on the client to accept the (server)
certificate. Also, prior I was testing with "Enable SSL" unchecked,
which would imply no certificate. So I checked it on both client and
server, and still getting the same thing: client sits there at
"Barrier is starting", no prompts.

Do you do that from into the graphic interface (you MUST do so), also,
launch barrier (the full program), not barriec !

When I look in ~/.local/share/
barrier/SSL it's empty.

Looks normal 'cos as far as I understand, it is only filled once the
certificate has been accepted.

I also quit Barrier on the client side,
restarted it, and same thing. Never a prompt, only "Barrier is
starting".

As a user :

launch barrier on the server (in graphic mode), if it is only an icon
in the taskbar, right-click it > show, hit F4 and check "Enable ssl",
also check that the machine name is present (in "Screen name")
d° on the client, which should ask you to accept the certificate
almost as soon as it is launched.

As root :

copy the aforementioned user directory to get the same in /root.

Since you mentioned root and 'manually', I quit on both machines then
ran from terminal as root. Same results.

Terminal ? In both the machines aren't in graphic mode, this can't work.

I've got to be missing something

Once it is configured and operational, I strongly suggest you save your
configuration (ie: $HOME/barrier.conf) on both the server and the
client, this way it is easier to remember what you did or copy ths
client's file to another client.

Jean-Yves

@JiffB commented on GitHub (Apr 3, 2023): On Mon, 03 Apr 2023 11:32:25 -0700 Jeff Henze ***@***.***> wrote: > > * on the client, launch manually barrier _and_ accept the server > > certificate, > > I'm unable to get a prompt on the client to accept the (server) > certificate. Also, prior I was testing with "Enable SSL" unchecked, > which would imply no certificate. So I checked it on both client and > server, and still getting the same thing: client sits there at > "Barrier is starting", no prompts. Do you do that from into the graphic interface (you MUST do so), also, launch barrier (the full program), not barriec ! > When I look in ~/.local/share/ > barrier/SSL it's empty. Looks normal 'cos as far as I understand, it is only filled once the certificate has been accepted. > I also quit Barrier on the client side, > restarted it, and same thing. Never a prompt, only "Barrier is > starting". As a user : * launch barrier on the server (in graphic mode), if it is only an icon in the taskbar, right-click it > show, hit F4 and check "Enable ssl", also check that the machine name is present (in "Screen name") * d° on the client, which should ask you to accept the certificate almost as soon as it is launched. As root : copy the aforementioned user directory to get the same in /root. > Since you mentioned root and 'manually', I quit on both machines then > ran from terminal as root. Same results. Terminal ? In both the machines aren't in graphic mode, this can't work. > I've got to be missing something > Once it is configured and operational, I strongly suggest you save your configuration (ie: $HOME/barrier.conf) on both the server and the client, this way it is easier to remember what you did or copy ths client's file to another client. Jean-Yves

gitea-mirror commented

2026-05-05 07:48:33 -06:00

Author

Owner

@gephenzie commented on GitHub (Apr 6, 2023):

Do you do that from into the graphic interface (you MUST do so), also, launch barrier (the full program), not barriec !

Yes, I'm in the graphic env, running "barrier" on both machines

As a user : * launch barrier on the server (in graphic mode), if it is only an icon in the taskbar, right-click it > show, hit F4 and check "Enable ssl", also check that the machine name is present (in "Screen name") * d° on the client, which should ask you to accept the certificate almost as soon as it is launched. As root : copy the aforementioned user directory to get the same in /root.

Did that and I get the same results as I did earlier - the client just sits at "Barrier is starting". I never get an offer to accept a certificate.

Terminal ? In both the machines aren't in graphic mode, this can't work.

I just attempted it to see. It didn't work when I did, so otherwise I've been running in the XFCE DE.

Once it is configured and operational, I strongly suggest you save your configuration (ie: $HOME/barrier.conf) on both the server and the client, this way it is easier to remember what you did or copy ths client's file to another client.

You bet I will. I think I have something, I don't know what, blocking communications between the two devices. The client never sees a server, so it never finishes starting (that's a guess). I'm not sure what would be blocking it since my firewall on both machines is off.

@gephenzie commented on GitHub (Apr 6, 2023): > Do you do that from into the graphic interface (you MUST do so), also, launch barrier (the full program), not barriec ! Yes, I'm in the graphic env, running "barrier" on both machines > As a user : * launch barrier on the server (in graphic mode), if it is only an icon in the taskbar, right-click it > show, hit F4 and check "Enable ssl", also check that the machine name is present (in "Screen name") * d° on the client, which should ask you to accept the certificate almost as soon as it is launched. As root : copy the aforementioned user directory to get the same in /root. Did that and I get the same results as I did earlier - the client just sits at "Barrier is starting". I never get an offer to accept a certificate. > Terminal ? In both the machines aren't in graphic mode, this can't work. I just attempted it to see. It didn't work when I did, so otherwise I've been running in the XFCE DE. > Once it is configured and operational, I strongly suggest you save your configuration (ie: $HOME/barrier.conf) on both the server and the client, this way it is easier to remember what you did or copy ths client's file to another client. You bet I will. I think I have something, I don't know what, blocking communications between the two devices. The client never sees a server, so it never finishes starting (that's a guess). I'm not sure what would be blocking it since my firewall on both machines is off.

gitea-mirror commented

2026-05-05 07:48:34 -06:00

Author

Owner

@JiffB commented on GitHub (Apr 6, 2023):

On Thu, 06 Apr 2023 11:47:48 -0700
Jeff Henze @.***> wrote:

Do you do that from into the graphic interface (you MUST do so),
also, launch barrier (the full program), not barriec !

Yes, I'm in the graphic env, running "barrier" on both machines

Fine, we can rule out the environment.

As a user : * launch barrier on the server (in graphic mode), if it
is only an icon in the taskbar, right-click it > show, hit F4 and
check "Enable ssl", also check that the machine name is present (in
"Screen name") * d° on the client, which should ask you to accept
the certificate almost as soon as it is launched. As root : copy
the aforementioned user directory to get the same in /root.

Did that and I get the same results as I did earlier - the client
just sits at "Barrier is starting". I never get an offer to accept a
certificate.

Hum, I'l say that it can be either :

firewall(s) problem (default port is : 24800 TCP),
a program problem, or dependencies problem,
some security framework missing authorization e.g.. to write to /tmp
(SE Linux, Apparmor, etc).

NOTE : as barriers (server) is launched from the saved session into
XFCE, I notice that there are some changes from the original line
I wrote :
= this part I wrote :
/usr/bin/barriers -f --no-tray --debug INFO --name ws01
! this one not !
--disable-client-cert-checking -c /tmp/Barrier.cqmERQ --address :24800
| | | | |
this, certainly not this is normal and intrinsic to barrier

but I don't think that's relevant.

Once it is configured and operational, I strongly suggest you save
your configuration (ie: $HOME/barrier.conf) on both the server and
the client, this way it is easier to remember what you did or copy
ths client's file to another client.

You bet I will. I think I have something, I don't know what, blocking
communications between the two devices. The client never sees a
server, so it never finishes starting (that's a guess). I'm not sure
what would be blocking it since my firewall on both machines is off.

Double check and test that these firewalls are really down.

Testing if barrier port is open shouldn't to any result, as the program
has not started, but just in case :
nmap -Pn -p 24800 | egrep -io 'open|closed|filtered'
of course to be launched from each machine.

@JiffB commented on GitHub (Apr 6, 2023): On Thu, 06 Apr 2023 11:47:48 -0700 Jeff Henze ***@***.***> wrote: > > Do you do that from into the graphic interface (you MUST do so), > > also, launch barrier (the full program), not barriec ! > > Yes, I'm in the graphic env, running "barrier" on both machines Fine, we can rule out the environment. > > As a user : * launch barrier on the server (in graphic mode), if it > > is only an icon in the taskbar, right-click it > show, hit F4 and > > check "Enable ssl", also check that the machine name is present (in > > "Screen name") * d° on the client, which should ask you to accept > > the certificate almost as soon as it is launched. As root : copy > > the aforementioned user directory to get the same in /root. > > Did that and I get the same results as I did earlier - the client > just sits at "Barrier is starting". I never get an offer to accept a > certificate. Hum, I'l say that it can be either : * firewall(s) problem (default port is : 24800 TCP), * a program problem, or dependencies problem, * some security framework missing authorization e.g.. to write to /tmp (SE Linux, Apparmor, etc). NOTE : as barriers (server) is launched from the saved session into XFCE, I notice that there are some changes from the original line I wrote : = this part I wrote : /usr/bin/barriers -f --no-tray --debug INFO --name ws01 ! this one not ! --disable-client-cert-checking -c /tmp/Barrier.cqmERQ --address :24800 | | | | | this, certainly not this is normal and intrinsic to barrier but I don't think that's relevant. > > Once it is configured and operational, I strongly suggest you save > > your configuration (ie: $HOME/barrier.conf) on both the server and > > the client, this way it is easier to remember what you did or copy > > ths client's file to another client. > > You bet I will. I think I have something, I don't know what, blocking > communications between the two devices. The client never sees a > server, so it never finishes starting (that's a guess). I'm not sure > what would be blocking it since my firewall on both machines is off. Double check and test that these firewalls are really down. Testing if barrier port is open shouldn't to any result, as the program has not started, but just in case : nmap <other machine IP> -Pn -p 24800 | egrep -io 'open|closed|filtered' of course to be launched from each machine.

gitea-mirror commented

2026-05-05 07:48:37 -06:00

Author

Owner

@JiffB commented on GitHub (Apr 6, 2023):

On Thu, 06 Apr 2023 11:47:48 -0700
Jeff Henze @.***> wrote:

CORRECTION (just tested) : use the nmap test as is on the client, but
it won't work on the server (it'll return
"closed").

@JiffB commented on GitHub (Apr 6, 2023): On Thu, 06 Apr 2023 11:47:48 -0700 Jeff Henze ***@***.***> wrote: CORRECTION (just tested) : use the nmap test as is on the client, but it won't work on the server (it'll return "closed").

gitea-mirror commented

2026-05-05 07:48:38 -06:00

Author

Owner

@G2G2G2G commented on GitHub (Apr 9, 2023):

This project is dead, use https://github.com/input-leap/input-leap a fork of it which is active

@G2G2G2G commented on GitHub (Apr 9, 2023): This project is dead, use https://github.com/input-leap/input-leap a fork of it which is active

gitea-mirror commented

2026-05-05 07:48:39 -06:00

Author

Owner

@Arsenii-Zhelobetskyi commented on GitHub (Aug 6, 2024):

Hey, Guysss, if it is still relevant, I have made it work! I have unchecked ssl certificates on both client and server, and after that I turned a VPN on my ubuntu. That was enough to make barrier run. I also turned off the auto config on the client.

@Arsenii-Zhelobetskyi commented on GitHub (Aug 6, 2024): Hey, Guysss, if it is still relevant, I have made it work! I have unchecked ssl certificates on both client and server, and after that I turned a VPN on my ubuntu. That was enough to make barrier run. I also turned off the auto config on the client.

gitea-mirror commented

2026-05-05 07:48:40 -06:00

Author

Owner

@joshuacv commented on GitHub (Apr 21, 2026):

I dont know if this helps anyone still. I got it to work by manually generating SSL certificates on both machines and then UNCHECKING "use SSL" on both machines. voodoo!

@joshuacv commented on GitHub (Apr 21, 2026): I dont know if this helps anyone still. I got it to work by manually generating SSL certificates on both machines and then UNCHECKING "use SSL" on both machines. voodoo!

gitea-mirror commented

2026-05-05 07:48:41 -06:00

Author

Owner

@nbolton commented on GitHub (Apr 21, 2026):

Barrier is no longer in development. Check out Deskflow (upstream) or Input Leap (fork).

https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap

If this is still an issue in those projects, we would appreciate a cross-post of this issue.

@nbolton commented on GitHub (Apr 21, 2026): Barrier is no longer in development. Check out Deskflow (upstream) or Input Leap (fork). https://github.com/deskflow/deskflow https://github.com/input-leap/input-leap If this is still an issue in those projects, we would appreciate a cross-post of this issue.

Rows
Columns

[GH-ISSUE #1922] Stuck on "Barrier is starting" #1404

What happened?

Version

Git commit hash (if applicable)

If applicable, where did you install Barrier from?

What OSes are you seeing the problem on? (Check all that apply)

What OS versions are you using?

Relevant log output

Any other information