Barrier: Barrier installed in Ubuntu Linux only stops at "Barrier is starting"

[josephcalixtro]

Operating Systems

Server: Ubuntu 18.04.1 LTS

Client: Windows 10 Pro

Barrier Version

1.9.π

Steps to reproduce bug

1.Set Windows 10 as client
2.Set Ubuntu Linux as Server

1. Start Barrier
2. "Barrier is starting" dialog is stuck

Other info

I Tried using the stated resolutions and also the steps in building in Linux. Since I am new to this Operating System and this application is the best way other than the usual KVM sharing, I tried this one. I also noticed the error stated in the logs when I tried to show it

[2018-11-22T11:52:43] INFO: starting server
[2018-11-22T11:52:43] INFO: command: /usr/local/bin/barriers -f --no-tray --debug DEBUG --name joseph-X450EA --enable-crypto -c /tmp/Barrier.dd3743 --address :24800
[2018-11-22T11:52:43] INFO: config file: /tmp/Barrier.ed3743
[2018-11-22T11:52:43] INFO: log level: DEBUG
[2018-11-22T11:52:43] DEBUG: opening configuration "/tmp/Barrier.dd3743"
/home/joseph/barrier/src/lib/barrier/ServerApp.cpp,221
[2018-11-22T11:52:43] DEBUG: configuration read successfully
/home/joseph/barrier/src/lib/barrier/ServerApp.cpp,232
[2018-11-22T11:52:43] DEBUG: XOpenDisplay(":0")
/home/joseph/barrier/src/lib/platform/XWindowsScreen.cpp,885
[2018-11-22T11:52:43] DEBUG: xscreensaver window: 0x00000000
/home/joseph/barrier/src/lib/platform/XWindowsScreenSaver.cpp,350
[2018-11-22T11:52:44] ERROR: process exited with error code: 11
[2018-11-22T11:52:44] INFO: detected process not running, auto restarting
[2018-11-22T11:52:45] DEBUG: starting process

Thanks for the further advice.

[AdrianKoshka]

Did you configure the server?

Also you really shouldn't be building from master unless you're doing development work and/or testing patches. We have releases

[l0o0]

I have this issue too.
I have downloaded the 2.1.2 source file from GitHub then compile.
If Ubuntu 16.04 as a server, win10 is a client, everything is OK.
If win10 as a server, Ubuntu as a client, Barrier is stuck in "Barrier is starting". The log is below:

[2018-11-26T15:36:46] INFO: starting client
[2018-11-26T15:36:46] INFO: config file: /tmp/Barrier.Xelgnj
[2018-11-26T15:36:46] INFO: log level: INFO
[2018-11-26T15:36:46] NOTE: started client
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/barrier/ClientApp.cpp,394
[2018-11-26T15:36:46] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/client/Client.cpp,146
[2018-11-26T15:36:46] INFO: OpenSSL 1.0.2g  1 Mar 2016
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/net/SecureSocket.cpp,839
[2018-11-26T15:37:01] WARNING: failed to connect to server: Timed out
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/barrier/ClientApp.cpp,302
[2018-11-26T15:37:02] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/client/Client.cpp,146
[2018-11-26T15:37:02] INFO: OpenSSL 1.0.2g  1 Mar 2016
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/net/SecureSocket.cpp,839
[2018-11-26T15:37:17] WARNING: failed to connect to server: Timed out
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/barrier/ClientApp.cpp,302
[2018-11-26T15:37:18] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/client/Client.cpp,146
[2018-11-26T15:37:18] INFO: OpenSSL 1.0.2g  1 Mar 2016
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/net/SecureSocket.cpp,839
[2018-11-26T15:37:33] WARNING: failed to connect to server: Timed out
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/barrier/ClientApp.cpp,302
[2018-11-26T15:37:34] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/client/Client.cpp,146
[2018-11-26T15:37:34] INFO: OpenSSL 1.0.2g  1 Mar 2016
    /home/l0o0/Downloads/barrier-2.1.2/src/lib/net/SecureSocket.cpp,839

I have tried to install from flatpak. Is it necessary to download so many packages?

After installing from flatpak and reboot. I select barrier form ubuntu dash. The problem is still here.
Here is the log:

[2018-11-26T15:56:31] INFO: starting client
[2018-11-26T15:56:31] INFO: config file: /tmp/Barrier.dXbkUj
[2018-11-26T15:56:31] INFO: log level: INFO
[2018-11-26T15:56:31] NOTE: started client
[2018-11-26T15:56:31] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:56:31] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:56:46] WARNING: failed to connect to server: Timed out
[2018-11-26T15:56:47] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:56:47] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:57:02] WARNING: failed to connect to server: Timed out
[2018-11-26T15:57:03] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:57:03] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:57:18] WARNING: failed to connect to server: Timed out
[2018-11-26T15:57:19] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:57:19] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:57:34] WARNING: failed to connect to server: Timed out
[2018-11-26T15:57:35] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:57:35] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:57:50] WARNING: failed to connect to server: Timed out
[2018-11-26T15:57:51] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:57:51] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:58:06] WARNING: failed to connect to server: Timed out
[2018-11-26T15:58:07] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:58:07] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:58:22] WARNING: failed to connect to server: Timed out
[2018-11-26T15:58:23] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:58:23] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:58:38] WARNING: failed to connect to server: Timed out
[2018-11-26T15:58:39] NOTE: connecting to '172.20.48.87': 172.20.48.87:24800
[2018-11-26T15:58:39] INFO: OpenSSL 1.0.2j  26 Sep 2016
[2018-11-26T15:58:54] WARNING: failed to connect to server: Timed out

[AdrianKoshka]

I have downloaded the 2.1.2 source file from GitHub then compile.

You're not meant to do this. 2.1.2 just introduced the flatpak. 2.10 is (more or less) identical.

I have tried to install from flatpak. Is it necessary to download so many packages?

Yep

If win10 as a server, Ubuntu as a client, Barrier is stuck in "Barrier is starting".

I know for windows you have to allow barrier.exe and barriers.exe through the firewall and open the port that barrier uses.

[l0o0]

@AdrianKoshka Thank you for your quick reply. After adding barriers.exe and barrierc.exe to the firewall exception programs, it works.

I think a simple tutorial or wiki will be appreciated.

[AdrianKoshka]

We do have a wiki, but I don't know the specific steps to adding the rule(s) to the windows firewall. I've offered before that if anyone can write up a tutorial for how to do it, I'm more than happy to add it to the wiki with credit.

[l0o0]

I have made a screenshot to show how to add exception programs in window defender firewall win10. I'm sorry that the interface is Chinese.

Maybe you can use these screenshot in the wiki.

[AdrianKoshka]

I'll get around to adding them, non-chinese ones would be preferable though. Even though the buttons are exactly the same. Thanks for the English instructions.

[AdrianKoshka]

A very lazy effort on my part, but: https://github.com/debauchee/barrier/wiki/Adding-Barrier-to-the-Windows-Firewall (Added credit)

[l0o0]

@AdrianKoshka I think screenshots were captured by l0o0 :smiley:

[AdrianKoshka]

Oh jeez! My bad! I'll fix that right away!

[N3BB3Z4R]

Same problem "Barrier is Starting", it still no works in Win10 as server and Ubuntu as client.

[zk-g]

Same, on debian 10 as client it keep say "barrier is starting" while in win10 as server It say it's in function

[leflings]

Just wanted to say I had the same issues, but I found that disabling SSL in barrier settings solved it. Of course this solution isn't for everyone, but it works in a pinch.

[AdrianKoshka]

If you were using an outdated version of the flatpak, that could be why.

[edegaudenzi]

Manual workaround: https://github.com/debauchee/barrier/issues/480

[ttfreeman]

Just wanted to say I had the same issues, but I found that disabling SSL in barrier settings solved it. Of course this solution isn't for everyone, but it works in a pinch.

How do you disable SSL in barrier setting?

[pratyushlohumi26]

Add exceptions in your windows firewall, put the name of the screens as same on the server-side (windows in case of me) as suggested in the above comments.

It still wasn't connected,

WHAT MORE I HAD TO DO: In my ubuntu (client side) TeamViewer was running in background as I exited it, barrier started working for me. Now I can control ubuntu with my windows mouse/keyboard.