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

[GH-ISSUE #53] Client on macOS not working #45

New issue
Closed
opened 2026-05-05 04:51:11 -06:00 by gitea-mirror · 9 comments
gitea-mirror commented 2026-05-05 04:51:11 -06:00
Owner
Copy link

Originally created by @shuklaalok7 on GitHub (May 30, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/53

Operating Systems

Server: Windows 10 Pro Version 1803
Client: macOS High Sierra 10.13.4

Barrier Version

2.1.0-RELEASE

Steps to reproduce bug

  1. Start server on Windows
  2. Configure Barrier on macOS as client.
  3. Windows recognizes a zero-conf client.
  4. On macOS, it keeps showing that "Barrier is starting." In the logs, it shows time out while connecting to server.
  5. No matter what I do with the Windows machine, the macOS side does not run as a client.
  6. If it matters, both the devices are on the same network Windows is 192.168.1.34 and mac is 192.168.1.35.

Other info

  • I have enabled all access in Windows firewall and macOS firewall to these apps.
  • When I create server on macOS and run Barrier as client on Windows, it works.
  • Does this bug prevent you from using Barrier entirely? Yes, because Windows PC is a desktop with the best keyboard and mouse attached, and my mac lacks enough ports to attach external keyboard and mouse.
Originally created by @shuklaalok7 on GitHub (May 30, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/53 ### Operating Systems ### **Server:** Windows 10 Pro Version 1803 **Client:** macOS High Sierra 10.13.4 ### Barrier Version ### 2.1.0-RELEASE ### Steps to reproduce bug ### 1. Start server on Windows 2. Configure Barrier on macOS as client. 3. Windows recognizes a zero-conf client. 4. On macOS, it keeps showing that "Barrier is starting." In the logs, it shows time out while connecting to server. 4. No matter what I do with the Windows machine, the macOS side does not run as a client. 5. If it matters, both the devices are on the same network Windows is 192.168.1.34 and mac is 192.168.1.35. ### Other info ### * I have enabled all access in Windows firewall and macOS firewall to these apps. * When I create server on macOS and run Barrier as client on Windows, it works. * Does this bug prevent you from using Barrier entirely? **Yes**, because Windows PC is a desktop with the best keyboard and mouse attached, and my mac lacks enough ports to attach external keyboard and mouse.
gitea-mirror 2026-05-05 04:51:11 -06:00
gitea-mirror commented 2026-05-05 04:51:20 -06:00
Author
Owner
Copy link

@shuklaalok7 commented on GitHub (May 30, 2018):

Release 2.1.0 for Windows uses OpenSSL 1.0.2n, while for macOS, it uses OpenSSL 1.0.2l.
I don't know if it's relevant here but I am writing a difference that I found.

<!-- gh-comment-id:393012160 --> @shuklaalok7 commented on GitHub (May 30, 2018): Release 2.1.0 for Windows uses OpenSSL 1.0.2n, while for macOS, it uses OpenSSL 1.0.2l. I don't know if it's relevant here but I am writing a difference that I found.
gitea-mirror commented 2026-05-05 04:51:23 -06:00
Author
Owner
Copy link

@dayne commented on GitHub (Jun 9, 2018):

What happens if you launch the client with DEBUG2 on the client. Launch manually like this:

barrierc -f --no-tray --debug DEBUG2 --name hostname --enable-crypto your_server_ip:24800

<!-- gh-comment-id:396005247 --> @dayne commented on GitHub (Jun 9, 2018): What happens if you launch the client with DEBUG2 on the client. Launch manually like this: `barrierc -f --no-tray --debug DEBUG2 --name `hostname` --enable-crypto your_server_ip:24800`
gitea-mirror commented 2026-05-05 04:51:25 -06:00
Author
Owner
Copy link

@Mfoor commented on GitHub (Jun 14, 2018):

I also have the same issue as above. The log tells me the following:

[2018-06-14T04:45:28] INFO: starting client
[2018-06-14T04:45:28] INFO: config file: /var/folders/4j/g5jp97gn43b8dvfp32yt4b4r0000gn/T/Barrier.FBzYsZ
[2018-06-14T04:45:28] INFO: log level: INFO
[2018-06-14T04:45:28] INFO: drag and drop enabled
[2018-06-14T04:45:28] NOTE: started client
[2018-06-14T04:45:28] NOTE: connecting to '192.168.1.114': 192.168.1.114:24800
[2018-06-14T04:45:28] INFO: OpenSSL 1.0.2n 7 Dec 2017
2018-06-14 04:45:28.162 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.172 barrierc[59092:1775135] starting cocoa loop
2018-06-14 04:45:28.173 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.173 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.173 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
barrierc(59092,0x7000012af000) malloc: *** error for object 0x7fc4f2620e38: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
[2018-06-14T04:45:28] ERROR: process exited with error code: 6
[2018-06-14T04:45:28] INFO: detected process not running, auto restarting

<!-- gh-comment-id:397237244 --> @Mfoor commented on GitHub (Jun 14, 2018): I also have the same issue as above. The log tells me the following: [2018-06-14T04:45:28] INFO: starting client [2018-06-14T04:45:28] INFO: config file: /var/folders/4j/g5jp97gn43b8dvfp32yt4b4r0000gn/T/Barrier.FBzYsZ [2018-06-14T04:45:28] INFO: log level: INFO [2018-06-14T04:45:28] INFO: drag and drop enabled [2018-06-14T04:45:28] NOTE: started client [2018-06-14T04:45:28] NOTE: connecting to '192.168.1.114': 192.168.1.114:24800 [2018-06-14T04:45:28] INFO: OpenSSL 1.0.2n 7 Dec 2017 2018-06-14 04:45:28.162 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.172 barrierc[59092:1775135] starting cocoa loop 2018-06-14 04:45:28.173 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.173 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.173 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2018-06-14 04:45:28.174 barrierc[59092:1775155] pid(59092)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! barrierc(59092,0x7000012af000) malloc: *** error for object 0x7fc4f2620e38: incorrect checksum for freed object - object was probably modified after being freed. *** set a breakpoint in malloc_error_break to debug [2018-06-14T04:45:28] ERROR: process exited with error code: 6 [2018-06-14T04:45:28] INFO: detected process not running, auto restarting
gitea-mirror commented 2026-05-05 04:51:28 -06:00
Author
Owner
Copy link

@CrafterLaughter commented on GitHub (Jul 8, 2018):

I noticed the same behavior. I could always run the server on my Mac but not my Win10 PC. What it wound up being is "C:\Program Files\Barrier\barriers.exe" has to be allowed in Windows firewall. I expect the "s" in barriers, stands for server. Just adding barrier.exe for the firewall wouldn't allow it to work.

<!-- gh-comment-id:403258438 --> @CrafterLaughter commented on GitHub (Jul 8, 2018): I noticed the same behavior. I could always run the server on my Mac but not my Win10 PC. What it wound up being is "C:\Program Files\Barrier\barriers.exe" has to be allowed in Windows firewall. I expect the "s" in barriers, stands for server. Just adding barrier.exe for the firewall wouldn't allow it to work.
gitea-mirror commented 2026-05-05 04:51:29 -06:00
Author
Owner
Copy link

@AdrianKoshka commented on GitHub (Jul 8, 2018):

That'd be the correct assumption, barriers is the server, and barrierc is the client.

<!-- gh-comment-id:403324839 --> @AdrianKoshka commented on GitHub (Jul 8, 2018): That'd be the correct assumption, `barriers` is the server, and `barrierc` is the client.
gitea-mirror commented 2026-05-05 04:51:32 -06:00
Author
Owner
Copy link

@chrisvltn commented on GitHub (Jul 22, 2018):

I allowed port 24800, barriers.exe, and barrierc.exe in Windows Firewall and then I was able to use my Mac as a client. Without that I was always getting "Connection timeout error"

<!-- gh-comment-id:406892522 --> @chrisvltn commented on GitHub (Jul 22, 2018): I allowed port 24800, barriers.exe, and barrierc.exe in Windows Firewall and then I was able to use my Mac as a client. Without that I was always getting "_Connection timeout error_"
gitea-mirror commented 2026-05-05 04:51:33 -06:00
Author
Owner
Copy link

@walker0643 commented on GitHub (Sep 8, 2018):

3794767459 should fix this. Please reopen if it's still a problem after release 2.2. Thanks :)

<!-- gh-comment-id:419677340 --> @walker0643 commented on GitHub (Sep 8, 2018): 3794767459f83e812cd4d9cf9e8d4da56bc19bd3 should fix this. Please reopen if it's still a problem after release 2.2. Thanks :)
gitea-mirror commented 2026-05-05 04:51:35 -06:00
Author
Owner
Copy link

@Technocaveman commented on GitHub (Oct 22, 2018):

This should really be added to the Wiki as someone who is new to this software will probably not be aware of how it works

<!-- gh-comment-id:431823534 --> @Technocaveman commented on GitHub (Oct 22, 2018): This should really be added to the Wiki as someone who is new to this software will probably not be aware of how it works
gitea-mirror commented 2026-05-05 04:51:37 -06:00
Author
Owner
Copy link

@AdrianKoshka commented on GitHub (Oct 22, 2018):

Yeah, if someone can give me instructions on how to do this (this being adding barrier to the windows firewall), I'd be more than willing to add it to the wiki. You can either open an issue with detailed instructions, and I'll add it, or just give me the instructions here.

<!-- gh-comment-id:431947776 --> @AdrianKoshka commented on GitHub (Oct 22, 2018): Yeah, if someone can give me instructions on how to do this (this being adding barrier to the windows firewall), I'd be more than willing to add it to the wiki. You can either open an issue with detailed instructions, and I'll add it, or just give me the instructions here.
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#45
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?