github-starred/barrier
2
0
Fork 0
mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 22:01:23 -06:00
Code Issues 1.0k Projects Packages Wiki Activity Actions

[GH-ISSUE #235] Windows IPC connection error #191

New issue
Open
opened 2026-05-05 05:38:03 -06:00 by gitea-mirror · 24 comments
gitea-mirror commented 2026-05-05 05:38:03 -06:00
Owner
Copy link

Originally created by @kexoyi on GitHub (Jan 22, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/235

Server: Windows 10 Pro 1709

Client: macOS Mojave 10.14.2

Version: 2.2

I am unable to build Barrier on macOS. I was able to build it just fine Windows. When the program is created, finder puts a prohibited sign on the icon telling me that the program is incomplete or damaged. I also inspected the package's contents and there is nothing in there accept the app icon.

Here is a Pastebin of what happens when I run the script:
https://pastebin.com/V2iAwWge

I have noticed that there is a fatal error saying "fatal: not a git repository (or any of the parent directories): .git". I am thinking this is the cause but have no clue on how to fix it.

What I do to produce this is simply dropping the script in the terminal and running it.

  • When did the problem start to occur? When I ran the script.
  • Is there a way to work around it? Unknown
  • Does this bug prevent you from using Barrier entirely? Yes
Originally created by @kexoyi on GitHub (Jan 22, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/235 Server: Windows 10 Pro 1709 Client: macOS Mojave 10.14.2 Version: 2.2 I am unable to build Barrier on macOS. I was able to build it just fine Windows. When the program is created, finder puts a prohibited sign on the icon telling me that the program is incomplete or damaged. I also inspected the package's contents and there is nothing in there accept the app icon. Here is a Pastebin of what happens when I run the script: https://pastebin.com/V2iAwWge I have noticed that there is a fatal error saying "fatal: not a git repository (or any of the parent directories): .git". I am thinking this is the cause but have no clue on how to fix it. What I do to produce this is simply dropping the script in the terminal and running it. * When did the problem start to occur? When I ran the script. * Is there a way to work around it? Unknown * Does this bug prevent you from using Barrier entirely? Yes
gitea-mirror commented 2026-05-05 05:38:08 -06:00
Author
Owner
Copy link

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

Any reason for building barrier yourself instead of using the .dmg we provide for 2.11?

<!-- gh-comment-id:456247810 --> @AdrianKoshka commented on GitHub (Jan 22, 2019): Any reason for building barrier yourself instead of using the `.dmg` we provide for 2.11?
gitea-mirror commented 2026-05-05 05:38:12 -06:00
Author
Owner
Copy link

@kexoyi commented on GitHub (Jan 22, 2019):

I am doing 2.2 because I have been unable to use macOS as the client. It will say "Barrier is starting..." but will never actually run. I have read that if I build 2.2 I should not have this issue. I have also tried making mac the server and my pc the host but the barrier still does not work with transferring the mouse even though it says they are running and connected.

<!-- gh-comment-id:456249843 --> @kexoyi commented on GitHub (Jan 22, 2019): I am doing 2.2 because I have been unable to use macOS as the client. It will say "Barrier is starting..." but will never actually run. I have read that if I build 2.2 I should not have this issue. I have also tried making mac the server and my pc the host but the barrier still does not work with transferring the mouse even though it says they are running and connected.
gitea-mirror commented 2026-05-05 05:38:15 -06:00
Author
Owner
Copy link

@jwestfall69 commented on GitHub (Jan 22, 2019):

I ran into that too when making debug builds on osx, Try this

Go into build/bundle/ and edit build_installer.sh. This script is responsible for populating Barrier.app with everything it needs and generating the .dmg file.

Near the top remove or comment out the following

# sanity check so we don't distribute packages full of debug symbols
if [ "Debug" != "Release" ]; then
    echo Will only build installers for Release builds
    exit 1
fi

I also stop it from making the dmg as the debug build are too big for it causing the process to error out and leave the temp dmg image mounted. You can stop it by putting an exit right before the following block in the script (near the bottom).

# create the DMG to be distributed in build/bundle
cd ../../..
hdiutil create -size 64m -fs HFS+ -volname "Barrier" temp.dmg || exit 1
hdiutil attach temp.dmg -mountpoint mnt || exit 1

Then run the script.

<!-- gh-comment-id:456252498 --> @jwestfall69 commented on GitHub (Jan 22, 2019): I ran into that too when making debug builds on osx, Try this Go into build/bundle/ and edit build_installer.sh. This script is responsible for populating Barrier.app with everything it needs and generating the .dmg file. Near the top remove or comment out the following ``` # sanity check so we don't distribute packages full of debug symbols if [ "Debug" != "Release" ]; then echo Will only build installers for Release builds exit 1 fi ``` I also stop it from making the dmg as the debug build are too big for it causing the process to error out and leave the temp dmg image mounted. You can stop it by putting an ```exit``` right before the following block in the script (near the bottom). ``` # create the DMG to be distributed in build/bundle cd ../../.. hdiutil create -size 64m -fs HFS+ -volname "Barrier" temp.dmg || exit 1 hdiutil attach temp.dmg -mountpoint mnt || exit 1 ``` Then run the script.
gitea-mirror commented 2026-05-05 05:38:17 -06:00
Author
Owner
Copy link

@kexoyi commented on GitHub (Jan 22, 2019):

You saved the day @jwestfall69 I have both Windows and macOS on 2.2! Oddly enough now on both ends it is saying "Barrier is starting." again. But I am getting different errors than I had before I build 2.2.

Error on Windows:

INFO: connecting to service...
ERROR: ipc connection error, code=19
ERROR: ipc connection error, connection refused

Error on macOS :

WARNING: failed to connect to server: Timed out
/Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303
NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
/Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143
INFO: OpenSSL 1.0.2q 20 Nov 2018
/Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851

I double checked my Windows firewall just to be safe and I have allowed barrier, barriers, and barrierc as well.

EDIT:
I forgot to enable to the service on Windows and now it is running fine but still produces errors. But macOS is still not running.

Here is what the Mac's log says:

[2019-01-21T20:11:46] INFO: starting client
[2019-01-21T20:11:46] INFO: config file: /private/var/folders/nz/w4stf_9d5s5fkg5bv4s0xcbw0000gn/T/Barrier.mMBeOm
[2019-01-21T20:11:46] INFO: log level: INFO
2019-01-21 20:11:46.958 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.966 barrierc[32480:1685365] starting cocoa loop
2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
[2019-01-21T20:11:46] INFO: drag and drop enabled
/Users/user/Downloads/barrier-master/src/lib/barrier/App.cpp,178
[2019-01-21T20:11:46] NOTE: started client
/Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,395
[2019-01-21T20:11:46] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
/Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143
[2019-01-21T20:11:46] INFO: OpenSSL 1.0.2q 20 Nov 2018
/Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851
[2019-01-21T20:12:01] WARNING: failed to connect to server: Timed out
/Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303
[2019-01-21T20:12:02] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
/Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143
[2019-01-21T20:12:02] INFO: OpenSSL 1.0.2q 20 Nov 2018
/Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851
[2019-01-21T20:12:17] WARNING: failed to connect to server: Timed out
/Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303
[2019-01-21T20:12:18] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
/Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143
[2019-01-21T20:12:18] INFO: OpenSSL 1.0.2q 20 Nov 2018
/Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851

Here is what Window's log says:

[2019-01-21T20:22:51] WARNING: failed to connect to server: Connection was refused
C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302
[2019-01-21T20:22:52] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146
[2019-01-21T20:22:52] INFO: OpenSSL 1.0.2l 25 May 2017
C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839
[2019-01-21T20:22:53] WARNING: failed to connect to server: Connection was refused
C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302
[2019-01-21T20:22:54] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146
[2019-01-21T20:22:54] INFO: OpenSSL 1.0.2l 25 May 2017
C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839
[2019-01-21T20:22:55] WARNING: failed to connect to server: Connection was refused
C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302
[2019-01-21T20:22:56] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146
[2019-01-21T20:22:56] INFO: OpenSSL 1.0.2l 25 May 2017
C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839
[2019-01-21T20:22:57] WARNING: failed to connect to server: Connection was refused
C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302
[2019-01-21T20:22:58] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146
[2019-01-21T20:22:58] INFO: OpenSSL 1.0.2l 25 May 2017
C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839

<!-- gh-comment-id:456256252 --> @kexoyi commented on GitHub (Jan 22, 2019): You saved the day @jwestfall69 I have both Windows and macOS on 2.2! Oddly enough now on both ends it is saying "Barrier is starting." again. But I am getting different errors than I had before I build 2.2. Error on Windows: > INFO: connecting to service... > ERROR: ipc connection error, code=19 > ERROR: ipc connection error, connection refused Error on macOS : > WARNING: failed to connect to server: Timed out /Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303 > NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 /Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143 > INFO: OpenSSL 1.0.2q 20 Nov 2018 /Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851 I double checked my Windows firewall just to be safe and I have allowed barrier, barriers, and barrierc as well. EDIT: I forgot to enable to the service on Windows and now it is running fine but still produces errors. But macOS is still not running. Here is what the Mac's log says: > [2019-01-21T20:11:46] INFO: starting client > [2019-01-21T20:11:46] INFO: config file: /private/var/folders/nz/w4stf_9d5s5fkg5bv4s0xcbw0000gn/T/Barrier.mMBeOm > [2019-01-21T20:11:46] INFO: log level: INFO > 2019-01-21 20:11:46.958 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.966 barrierc[32480:1685365] starting cocoa loop > 2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.966 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:11:46.967 barrierc[32480:1685399] pid(32480)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > [2019-01-21T20:11:46] INFO: drag and drop enabled > /Users/user/Downloads/barrier-master/src/lib/barrier/App.cpp,178 > [2019-01-21T20:11:46] NOTE: started client > /Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,395 > [2019-01-21T20:11:46] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > /Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143 > [2019-01-21T20:11:46] INFO: OpenSSL 1.0.2q 20 Nov 2018 > /Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851 > [2019-01-21T20:12:01] WARNING: failed to connect to server: Timed out > /Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303 > [2019-01-21T20:12:02] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > /Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143 > [2019-01-21T20:12:02] INFO: OpenSSL 1.0.2q 20 Nov 2018 > /Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851 > [2019-01-21T20:12:17] WARNING: failed to connect to server: Timed out > /Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303 > [2019-01-21T20:12:18] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > /Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143 > [2019-01-21T20:12:18] INFO: OpenSSL 1.0.2q 20 Nov 2018 > /Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851 Here is what Window's log says: > [2019-01-21T20:22:51] WARNING: failed to connect to server: Connection was refused > C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302 > [2019-01-21T20:22:52] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146 > [2019-01-21T20:22:52] INFO: OpenSSL 1.0.2l 25 May 2017 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839 > [2019-01-21T20:22:53] WARNING: failed to connect to server: Connection was refused > C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302 > [2019-01-21T20:22:54] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146 > [2019-01-21T20:22:54] INFO: OpenSSL 1.0.2l 25 May 2017 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839 > [2019-01-21T20:22:55] WARNING: failed to connect to server: Connection was refused > C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302 > [2019-01-21T20:22:56] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146 > [2019-01-21T20:22:56] INFO: OpenSSL 1.0.2l 25 May 2017 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839 > [2019-01-21T20:22:57] WARNING: failed to connect to server: Connection was refused > C:\Users\user\Desktop\barrier-2.1.2\src\lib\barrier\ClientApp.cpp,302 > [2019-01-21T20:22:58] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\client\Client.cpp,146 > [2019-01-21T20:22:58] INFO: OpenSSL 1.0.2l 25 May 2017 > C:\Users\user\Desktop\barrier-2.1.2\src\lib\net\SecureSocket.cpp,839 >
gitea-mirror commented 2026-05-05 05:38:19 -06:00
Author
Owner
Copy link

@jwestfall69 commented on GitHub (Jan 22, 2019):

The IPC issue on windows is because the barrierd service isnt running. Its normally installed/started by the barrier installer. See if its under the list of services and start it. If its not there, you likely need to manually added it. To do that check the [Run] section in dist/inno/barrier.iss.in for details about what the installer is doing to install/start it.

<!-- gh-comment-id:456261209 --> @jwestfall69 commented on GitHub (Jan 22, 2019): The IPC issue on windows is because the barrierd service isnt running. Its normally installed/started by the barrier installer. See if its under the list of services and start it. If its not there, you likely need to manually added it. To do that check the ```[Run]``` section in dist/inno/barrier.iss.in for details about what the installer is doing to install/start it.
gitea-mirror commented 2026-05-05 05:38:21 -06:00
Author
Owner
Copy link

@kexoyi commented on GitHub (Jan 22, 2019):

So I decided to go back to 2.1.1 on windows and Mac. Here are my logs now.

Mac:

[2019-01-21T20:56:01] INFO: starting client
[2019-01-21T20:56:01] INFO: config file: /var/folders/nz/w4stf_9d5s5fkg5bv4s0xcbw0000gn/T/Barrier.tkPZuN
[2019-01-21T20:56:01] INFO: log level: INFO
2019-01-21 20:56:01.302 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699174] starting cocoa loop
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
[2019-01-21T20:56:01] INFO: drag and drop enabled
[2019-01-21T20:56:01] NOTE: started client
[2019-01-21T20:56:01] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
[2019-01-21T20:56:01] INFO: OpenSSL 1.0.2n 7 Dec 2017
[2019-01-21T20:56:16] WARNING: failed to connect to server: Timed out
[2019-01-21T20:56:17] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
[2019-01-21T20:56:17] INFO: OpenSSL 1.0.2n 7 Dec 2017
[2019-01-21T20:56:32] WARNING: failed to connect to server: Timed out
[2019-01-21T20:56:33] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
[2019-01-21T20:56:33] INFO: OpenSSL 1.0.2n 7 Dec 2017

Windows:

[2019-01-21T20:53:49] INFO: connecting to service...
[2019-01-21T20:53:49] INFO: connection established
[2019-01-21T20:53:48] INFO: using last known command: "C:/Program Files/Barrier/barrierc.exe" -f --no-tray --debug INFO --name DESKTOP-4S2N8J3 --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "C:\Users\user\AppData\Local\Barrier" [192.168.7.40]:24800
[2019-01-21T20:53:48] INFO: service command updated
[2019-01-21T20:53:48] INFO: starting new process as privileged user
[2019-01-21T20:53:48] INFO: server status: active
[2019-01-21T20:53:48] INFO: drag and drop enabled
[2019-01-21T20:53:48] ERROR: failed to get desktop path, no drop target available, error=2
[2019-01-21T20:53:48] NOTE: started client
[2019-01-21T20:53:48] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
[2019-01-21T20:53:48] INFO: OpenSSL 1.0.2l 25 May 2017
[2019-01-21T20:53:49] WARNING: failed to connect to server: Connection was refused
[2019-01-21T20:53:49] INFO: server status: active
[2019-01-21T20:53:50] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
[2019-01-21T20:53:50] INFO: OpenSSL 1.0.2l 25 May 2017
[2019-01-21T20:53:51] WARNING: failed to connect to server: Connection was refused
[2019-01-21T20:53:52] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800

<!-- gh-comment-id:456263836 --> @kexoyi commented on GitHub (Jan 22, 2019): So I decided to go back to 2.1.1 on windows and Mac. Here are my logs now. Mac: > [2019-01-21T20:56:01] INFO: starting client > [2019-01-21T20:56:01] INFO: config file: /var/folders/nz/w4stf_9d5s5fkg5bv4s0xcbw0000gn/T/Barrier.tkPZuN > [2019-01-21T20:56:01] INFO: log level: INFO > 2019-01-21 20:56:01.302 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699174] starting cocoa loop > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > 2019-01-21 20:56:01.311 barrierc[32640:1699190] pid(32640)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! > [2019-01-21T20:56:01] INFO: drag and drop enabled > [2019-01-21T20:56:01] NOTE: started client > [2019-01-21T20:56:01] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > [2019-01-21T20:56:01] INFO: OpenSSL 1.0.2n 7 Dec 2017 > [2019-01-21T20:56:16] WARNING: failed to connect to server: Timed out > [2019-01-21T20:56:17] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > [2019-01-21T20:56:17] INFO: OpenSSL 1.0.2n 7 Dec 2017 > [2019-01-21T20:56:32] WARNING: failed to connect to server: Timed out > [2019-01-21T20:56:33] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > [2019-01-21T20:56:33] INFO: OpenSSL 1.0.2n 7 Dec 2017 Windows: > [2019-01-21T20:53:49] INFO: connecting to service... > [2019-01-21T20:53:49] INFO: connection established > [2019-01-21T20:53:48] INFO: using last known command: "C:/Program Files/Barrier/barrierc.exe" -f --no-tray --debug INFO --name DESKTOP-4S2N8J3 --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "C:\Users\user\AppData\Local\Barrier" [192.168.7.40]:24800 > [2019-01-21T20:53:48] INFO: service command updated > [2019-01-21T20:53:48] INFO: starting new process as privileged user > [2019-01-21T20:53:48] INFO: server status: active > [2019-01-21T20:53:48] INFO: drag and drop enabled > [2019-01-21T20:53:48] ERROR: failed to get desktop path, no drop target available, error=2 > [2019-01-21T20:53:48] NOTE: started client > [2019-01-21T20:53:48] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > [2019-01-21T20:53:48] INFO: OpenSSL 1.0.2l 25 May 2017 > [2019-01-21T20:53:49] WARNING: failed to connect to server: Connection was refused > [2019-01-21T20:53:49] INFO: server status: active > [2019-01-21T20:53:50] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800 > [2019-01-21T20:53:50] INFO: OpenSSL 1.0.2l 25 May 2017 > [2019-01-21T20:53:51] WARNING: failed to connect to server: Connection was refused > [2019-01-21T20:53:52] NOTE: connecting to '192.168.7.40': 192.168.7.40:24800
gitea-mirror commented 2026-05-05 05:38:23 -06:00
Author
Owner
Copy link

@kexoyi commented on GitHub (Jan 22, 2019):

I really don't know what happened but it has now decided to work. All I did was add aliases. Switch pc to client, and mac to server. It still didn't work but when I swapped my pc back to server and mac back to client, it is now all the sudden working. I don't really understand what caused this, but it is now working.

<!-- gh-comment-id:456267209 --> @kexoyi commented on GitHub (Jan 22, 2019): I really don't know what happened but it has now decided to work. All I did was add aliases. Switch pc to client, and mac to server. It still didn't work but when I swapped my pc back to server and mac back to client, it is now all the sudden working. I don't really understand what caused this, but it is now working.
gitea-mirror commented 2026-05-05 05:38:26 -06:00
Author
Owner
Copy link

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

Perhaps windows was just being wonky about starting a service?

<!-- gh-comment-id:456504391 --> @AdrianKoshka commented on GitHub (Jan 22, 2019): Perhaps windows was just being wonky about starting a service?
gitea-mirror commented 2026-05-05 05:38:28 -06:00
Author
Owner
Copy link

@mirh commented on GitHub (Sep 23, 2019):

Could it have something to do with ports being busy or something?

Error 19 should be OperationError, and I just noticed how oddly 24801 is reported in use even though config has 24800.
And as mentioned in https://github.com/symless/synergy-core/issues/6458, after killing and restarting everything it seemed to be solved.

<!-- gh-comment-id:534251185 --> @mirh commented on GitHub (Sep 23, 2019): Could it have something to do with ports being busy or something? Error 19 [should be](https://doc.qt.io/qt-5/qabstractsocket.html#SocketError-enum) OperationError, and I just noticed how oddly 24801 is reported in use even though config has 24800. And as mentioned in https://github.com/symless/synergy-core/issues/6458, after killing and restarting everything it seemed to be solved.
gitea-mirror commented 2026-05-05 05:38:31 -06:00
Author
Owner
Copy link

@ExpandingMan commented on GitHub (Oct 29, 2020):

When using windows as client and linux as server, I get (on windows)

[2020-10-29T19:13:44] ERROR: ipc connection error, connection refused
[2020-10-29T19:13:45] INFO: connecting to service...

Were you implying the service may not be running on linux, or on windows? On linux, I have the server running as barriers -f -c barrier.conf with a simple screen config. On windows I have no idea what's happening because it's windows.

Update: I was also having the windows config file issue which mysteriously seems to have solved itself. However, no matter what I do I seem to get the ipc connection error only on windows. The linux machines all seem to be able to connect to each other.

<!-- gh-comment-id:719076273 --> @ExpandingMan commented on GitHub (Oct 29, 2020): When using windows as client and linux as server, I get (on windows) ``` [2020-10-29T19:13:44] ERROR: ipc connection error, connection refused [2020-10-29T19:13:45] INFO: connecting to service... ``` Were you implying the service may not be running on linux, or on windows? On linux, I have the server running as `barriers -f -c barrier.conf` with a simple screen config. On windows I have no idea what's happening because it's windows. Update: I was also having the windows config file issue which mysteriously seems to have solved itself. However, no matter what I do I seem to get the ipc connection error only on windows. The linux machines all seem to be able to connect to each other.
gitea-mirror commented 2026-05-05 05:38:34 -06:00
Author
Owner
Copy link

@wienyang commented on GitHub (Nov 30, 2020):

i reinstalled barrier and it worked fine now

<!-- gh-comment-id:735584842 --> @wienyang commented on GitHub (Nov 30, 2020): i reinstalled barrier and it worked fine now
gitea-mirror commented 2026-05-05 05:38:37 -06:00
Author
Owner
Copy link

@groundstation1 commented on GitHub (Jan 8, 2021):

When using windows as client and linux as server, I get (on windows)

[2020-10-29T19:13:44] ERROR: ipc connection error, connection refused
[2020-10-29T19:13:45] INFO: connecting to service...

Were you implying the service may not be running on linux, or on windows? On linux, I have the server running as barriers -f -c barrier.conf with a simple screen config. On windows I have no idea what's happening because it's windows.

Update: I was also having the windows config file issue which mysteriously seems to have solved itself. However, no matter what I do I seem to get the ipc connection error only on windows. The linux machines all seem to be able to connect to each other.

I had this error on windows, even before clicking "start". The problem was the service not running on the windows machine. You can check in the task manager, it has a services tab. From there you can also get to the system settings for services and see if it's disabled and if it's set to launch with windows or not.

<!-- gh-comment-id:756768061 --> @groundstation1 commented on GitHub (Jan 8, 2021): > When using windows as client and linux as server, I get (on windows) > > ``` > [2020-10-29T19:13:44] ERROR: ipc connection error, connection refused > [2020-10-29T19:13:45] INFO: connecting to service... > ``` > > Were you implying the service may not be running on linux, or on windows? On linux, I have the server running as `barriers -f -c barrier.conf` with a simple screen config. On windows I have no idea what's happening because it's windows. > > Update: I was also having the windows config file issue which mysteriously seems to have solved itself. However, no matter what I do I seem to get the ipc connection error only on windows. The linux machines all seem to be able to connect to each other. I had this error on windows, even before clicking "start". The problem was the service not running on the windows machine. You can check in the task manager, it has a services tab. From there you can also get to the system settings for services and see if it's disabled and if it's set to launch with windows or not.
gitea-mirror commented 2026-05-05 05:38:42 -06:00
Author
Owner
Copy link

@Hocnonsense commented on GitHub (Apr 9, 2021):

I got this error after kill barrier in Windows Task Manager.
version: 2.3.3-release-3395cca9

<!-- gh-comment-id:816618600 --> @Hocnonsense commented on GitHub (Apr 9, 2021): I got this error after kill `barrier` in Windows Task Manager. version: 2.3.3-release-3395cca9
gitea-mirror commented 2026-05-05 05:38:45 -06:00
Author
Owner
Copy link

@matjaz321 commented on GitHub (Apr 22, 2021):

I got this error after kill barrier in Windows Task Manager.
version: 2.3.3-release-3395cca9

Same, but I fixed it by re-installing

<!-- gh-comment-id:824668627 --> @matjaz321 commented on GitHub (Apr 22, 2021): > > > I got this error after kill `barrier` in Windows Task Manager. > version: 2.3.3-release-3395cca9 Same, but I fixed it by re-installing
gitea-mirror commented 2026-05-05 05:38:48 -06:00
Author
Owner
Copy link

@Hocnonsense commented on GitHub (Apr 22, 2021):

I got this error after kill barrier in Windows Task Manager.
version: 2.3.3-release-3395cca9

Same, but I fixed it by re-installing

I restart the computer and barrier run again. It seems that the server of barrier start automatically and only once?

<!-- gh-comment-id:824680442 --> @Hocnonsense commented on GitHub (Apr 22, 2021): > > I got this error after kill `barrier` in Windows Task Manager. > > version: 2.3.3-release-3395cca9 > > Same, but I fixed it by re-installing I restart the computer and `barrier` run again. It seems that the server of `barrier` start automatically and only once?
gitea-mirror commented 2026-05-05 05:38:50 -06:00
Author
Owner
Copy link

@mirh commented on GitHub (Apr 22, 2021):

Check the barrier service.

<!-- gh-comment-id:824700075 --> @mirh commented on GitHub (Apr 22, 2021): Check the barrier service.
gitea-mirror commented 2026-05-05 05:38:52 -06:00
Author
Owner
Copy link

@CratylusCO commented on GitHub (Oct 8, 2021):

I did all this and noticed barrierd service wasn't running. I didn't want to mess with RUN or anything else, so I verified all the firewall rules were right, ended barrier.exe task and ran the installer again. Fixed everything and barrierd service started running.

<!-- gh-comment-id:938728403 --> @CratylusCO commented on GitHub (Oct 8, 2021): I did all this and noticed barrierd service wasn't running. I didn't want to mess with RUN or anything else, so I verified all the firewall rules were right, ended barrier.exe task and ran the installer again. Fixed everything and barrierd service started running.
gitea-mirror commented 2026-05-05 05:38:55 -06:00
Author
Owner
Copy link

@AymenFJA commented on GitHub (Jan 29, 2022):

I fixed it by going to the Task Manager and switch to the service tab, look for barrier and right-click on it, and start as it was stopped for some reason.

<!-- gh-comment-id:1024992006 --> @AymenFJA commented on GitHub (Jan 29, 2022): I fixed it by going to the `Task Manager` and switch to the `service` tab, look for `barrier` and right-click on it, and `start` as it was stopped for some reason.
gitea-mirror commented 2026-05-05 05:38:57 -06:00
Author
Owner
Copy link

@VNRARA commented on GitHub (Jul 30, 2022):

Years later and I still don't get why there isn't some sort of auto restart of this programmed into barrier to auto restart.

<!-- gh-comment-id:1200289610 --> @VNRARA commented on GitHub (Jul 30, 2022): Years later and I still don't get why there isn't some sort of auto restart of this programmed into barrier to auto restart.
gitea-mirror commented 2026-05-05 05:39:00 -06:00
Author
Owner
Copy link

@ingxfm commented on GitHub (Sep 5, 2022):

As for @jwestfall69 and @AymenFJA, the Barrier service was not running, in my case.

<!-- gh-comment-id:1236846337 --> @ingxfm commented on GitHub (Sep 5, 2022): As for @jwestfall69 and @AymenFJA, the Barrier service was not running, in my case.
gitea-mirror commented 2026-05-05 05:39:03 -06:00
Author
Owner
Copy link

@jhgorse commented on GitHub (Feb 26, 2023):

Where is the code for registering the service on windows installation?

<!-- gh-comment-id:1445420980 --> @jhgorse commented on GitHub (Feb 26, 2023): Where is the code for registering the service on windows installation?
gitea-mirror commented 2026-05-05 05:39:04 -06:00
Author
Owner
Copy link

@sumless commented on GitHub (Sep 11, 2023):

This issue happened to me while upgrading from Barrier 2.3.3 to Barrier 2.3.4 in a Windows 10 environment.
The following steps resolved my issue:

  1. Uninstall Barrier
  2. Uninstall Bonjour
  3. Reboot the operating system
  4. reinstall Barrier
<!-- gh-comment-id:1713236911 --> @sumless commented on GitHub (Sep 11, 2023): This issue happened to me while upgrading from Barrier 2.3.3 to Barrier 2.3.4 in a Windows 10 environment. The following steps resolved my issue: 1. Uninstall Barrier 2. Uninstall Bonjour 3. Reboot the operating system 4. reinstall Barrier
gitea-mirror commented 2026-05-05 05:39:08 -06:00
Author
Owner
Copy link

@JuninhoFreitas commented on GitHub (Feb 15, 2024):

Okay,
So here is the solution i found to Windows:

  1. Close your barrier (quit option in Task Bar icon)
  2. Win+R: services
  3. Look for the service of Barrier (you can just start typing barrier and it will find)
  4. Start if it is stopped, restart if it is running
  5. After started, open barrier as administrator
  6. If everything worked, than you will see "Barrier is Running"
  7. If not, try to start manully
  8. If it still not working, find you ip (the bold Ip in "IP ADRESSES:")
  9. Click in the menu bar "Barrier"
  10. Select Change Settings
  11. In networking, replace the IP in "Address" field with the one you copy
  12. Disable SSL and require certificate
  13. Click ok, and repeat the process from the step 1
  14. Let me know if it worked to you

PT-BR:

Okay,
Então aqui está a solução que encontrei para o Windows:

  1. Feche o Barrier (opção de Sair no ícone da barra de tarefas)
  2. Win+R: "services"
  3. Procure pelo serviço do Barrier (você pode começar a digitar "barrier" e ele encontrará)
  4. Inicie se estiver parado, reinicie se estiver em execução
  5. Depois de iniciado, abra o Barrier como administrador
  6. Se tudo funcionou, você verá "Barrier is Running"
  7. Se não, tente iniciar manualmente
  8. Se ainda não estiver funcionando, encontre seu IP (o IP em negrito em "IP ADRESSES:")
  9. Clique na barra de menu "Barrier"
  10. Selecione Alterar Configurações
  11. Na rede, substitua o IP no campo "Endereço" pelo que você copiou
  12. Desative SSL e exigir certificado
  13. Clique em OK e repita o processo a partir do passo 1
  14. Me avise se funcionou para você.
<!-- gh-comment-id:1945983249 --> @JuninhoFreitas commented on GitHub (Feb 15, 2024): Okay, So here is the solution i found to Windows: 1. Close your barrier (quit option in Task Bar icon) 2. Win+R: services 3. Look for the service of Barrier (you can just start typing barrier and it will find) 4. Start if it is stopped, restart if it is running 5. After started, open barrier as administrator 6. If everything worked, than you will see "Barrier is Running" 7. If not, try to start manully 8. If it still not working, find you ip (the bold Ip in "IP ADRESSES:") 9. Click in the menu bar "Barrier" 10. Select Change Settings 11. In networking, replace the IP in "Address" field with the one you copy 12. Disable SSL and require certificate 13. Click ok, and repeat the process from the step 1 14. Let me know if it worked to you PT-BR: Okay, Então aqui está a solução que encontrei para o Windows: 1. Feche o Barrier (opção de Sair no ícone da barra de tarefas) 2. Win+R: "services" 3. Procure pelo serviço do Barrier (você pode começar a digitar "barrier" e ele encontrará) 4. Inicie se estiver parado, reinicie se estiver em execução 5. Depois de iniciado, abra o Barrier como administrador 6. Se tudo funcionou, você verá "Barrier is Running" 7. Se não, tente iniciar manualmente 8. Se ainda não estiver funcionando, encontre seu IP (o IP em negrito em "IP ADRESSES:") 9. Clique na barra de menu "Barrier" 10. Selecione Alterar Configurações 11. Na rede, substitua o IP no campo "Endereço" pelo que você copiou 12. Desative SSL e exigir certificado 13. Clique em OK e repita o processo a partir do passo 1 14. Me avise se funcionou para você.
gitea-mirror commented 2026-05-05 05:39:09 -06:00
Author
Owner
Copy link

@Rivonivo commented on GitHub (Jan 4, 2025):

Okay, So here is the solution i found to Windows:

  1. Close your barrier (quit option in Task Bar icon)
  2. Win+R: services
  3. Look for the service of Barrier (you can just start typing barrier and it will find)
  4. Start if it is stopped, restart if it is running
  5. After started, open barrier as administrator
  6. If everything worked, than you will see "Barrier is Running"
  7. If not, try to start manully
  8. If it still not working, find you ip (the bold Ip in "IP ADRESSES:")
  9. Click in the menu bar "Barrier"
  10. Select Change Settings
  11. In networking, replace the IP in "Address" field with the one you copy
  12. Disable SSL and require certificate
  13. Click ok, and repeat the process from the step 1
  14. Let me know if it worked to you

PT-BR:

Okay, Então aqui está a solução que encontrei para o Windows:

  1. Feche o Barrier (opção de Sair no ícone da barra de tarefas)
  2. Win+R: "services"
  3. Procure pelo serviço do Barrier (você pode começar a digitar "barrier" e ele encontrará)
  4. Inicie se estiver parado, reinicie se estiver em execução
  5. Depois de iniciado, abra o Barrier como administrador
  6. Se tudo funcionou, você verá "Barrier is Running"
  7. Se não, tente iniciar manualmente
  8. Se ainda não estiver funcionando, encontre seu IP (o IP em negrito em "IP ADRESSES:")
  9. Clique na barra de menu "Barrier"
  10. Selecione Alterar Configurações
  11. Na rede, substitua o IP no campo "Endereço" pelo que você copiou
  12. Desative SSL e exigir certificado
  13. Clique em OK e repita o processo a partir do passo 1
  14. Me avise se funcionou para você.

i love u <3 searches for 2 hours now your way worked

<!-- gh-comment-id:2571411234 --> @Rivonivo commented on GitHub (Jan 4, 2025): > Okay, So here is the solution i found to Windows: > > 1. Close your barrier (quit option in Task Bar icon) > 2. Win+R: services > 3. Look for the service of Barrier (you can just start typing barrier and it will find) > 4. Start if it is stopped, restart if it is running > 5. After started, open barrier as administrator > 6. If everything worked, than you will see "Barrier is Running" > 7. If not, try to start manully > 8. If it still not working, find you ip (the bold Ip in "IP ADRESSES:") > 9. Click in the menu bar "Barrier" > 10. Select Change Settings > 11. In networking, replace the IP in "Address" field with the one you copy > 12. Disable SSL and require certificate > 13. Click ok, and repeat the process from the step 1 > 14. Let me know if it worked to you > > PT-BR: > > Okay, Então aqui está a solução que encontrei para o Windows: > > 1. Feche o Barrier (opção de Sair no ícone da barra de tarefas) > 2. Win+R: "services" > 3. Procure pelo serviço do Barrier (você pode começar a digitar "barrier" e ele encontrará) > 4. Inicie se estiver parado, reinicie se estiver em execução > 5. Depois de iniciado, abra o Barrier como administrador > 6. Se tudo funcionou, você verá "Barrier is Running" > 7. Se não, tente iniciar manualmente > 8. Se ainda não estiver funcionando, encontre seu IP (o IP em negrito em "IP ADRESSES:") > 9. Clique na barra de menu "Barrier" > 10. Selecione Alterar Configurações > 11. Na rede, substitua o IP no campo "Endereço" pelo que você copiou > 12. Desative SSL e exigir certificado > 13. Clique em OK e repita o processo a partir do passo 1 > 14. Me avise se funcionou para você. i love u <3 searches for 2 hours now your way worked
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
enhancement/builds/windows-multi-versions-build
martin-furter-barrier-term
enhancement/builds/macos-universal
enhancement/builds/macos-universal-qt6-test
2.3.x
fix/lang-translation/ssl-slash-tls
feature/build/compile/32-bit
feature/build/compile/armv7
testing-framework
README-update
remotes/fork/README-update
remotes/fork/smartzeroconf
smartzeroconf
pages-devel
remotes/fork/pages-devel
pkgconfig
remotes/fork/pkgconfig
release
remotes/fork/release
v2.4.0
v2.3.4
v2.3.3
1.11.0-stable
v1.11.0-rc2
v2.3.2
v1.10.3-stable
v2.3.2-alpha
v2.3.1
v2.3.0
v1.10.2-stable
v1.10.2-rc1
v1.10.2-rc2
v2.1.2
v2.0.8-beta
v2.0.7-beta
v2.0.4-beta
v2.0.3-beta
v2.1.1
v2.1.0
v1.9.1-stable
v2.0.0
v1.9.0-stable
v2.0.0-RC2
v2.0.0-RC1
v2.0.0-stable
v1.8.8-stable
v1.8.7-stable
v1.8.6-stable
v1.8.5-stable
v1.8.4-stable
v1.8.3-stable
v1.8.1-stable
v1.8.0-beta
v1.7.3-stable
v1.7.2-stable
v1.7.1-stable
1.7.0
1.6.3-final
1.6.2
1.6.1
1.6.0
Labels
Clear labels   
HiDPI

   
bounty

   
bsd/freebsd

   
bsd/openbsd

   
bug

   
bug

   
build-infra

   
cantfix

   
critical

   
doc

   
duplicate

   
enhancement

   
fix-available

   
from git

   
from release

   
good first issue

   
help wanted

   
installer/package

   
invalid

   
linux

   
macOS

   
meta

   
needs testing

   
pull-request

Mirrored from GitHub Pull Request

  
query

   
question

   
regression

   
regression

   
v2.4.0

   
windows

   
wontfix

   
work-in-progress
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#191
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?