github-starred/barrier

Fork 0

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

[GH-ISSUE #643] TIS/TM non-main-thread error in macOS #509

New issue

Closed

opened 2026-05-05 06:33:40 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:33:40 -06:00

Owner

Originally created by @spencerkohan on GitHub (Apr 29, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/643

Operating Systems

Server: macOS Mojave 10.14.5

Client: Ubuntu 18.04

Barrier Version

server: 2.3.2-Release-210c2b70

client: 2.3.2-snapshot-9080ce45

Steps to reproduce bug

When I try to start the server, I am unable to connect a client, and when I look at the logs I see this error:

pid(3008)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!

On the client side, I see this error:

ssl error occurred (generic error)
error: 1408F10B:SSL routines ssl13_get_record:wrong version number
failed to connect secure socket

Other info

When did the problem start to occur? When I tried to use barrier for the first time
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

Originally created by @spencerkohan on GitHub (Apr 29, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/643 ### Operating Systems ### Server: macOS Mojave 10.14.5 Client: Ubuntu 18.04 ### Barrier Version ### server: 2.3.2-Release-210c2b70 client: 2.3.2-snapshot-9080ce45 ### Steps to reproduce bug ### When I try to start the server, I am unable to connect a client, and when I look at the logs I see this error: ``` pid(3008)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! ``` On the client side, I see this error: ``` ssl error occurred (generic error) error: 1408F10B:SSL routines ssl13_get_record:wrong version number failed to connect secure socket ``` ### Other info ### * When did the problem start to occur? When I tried to use barrier for the first time * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here.

gitea-mirror closed this issue

2026-05-05 06:33:43 -06:00

gitea-mirror commented

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

Author

Owner

@simons-public commented on GitHub (May 3, 2020):

The TIS/TSM error happens on MacOS even when Barrier is working. Here is a log from mine as an example.

It seems like it might be an issue on the client side if you aren't seeing client connections in the server's logs. Can you test connecting to the server with the openssl comand on the client? For example:

$ openssl s_client -connect hostname:24800

Also, check that you don't have old fingerprints (just like with ssh) in ~/.local/share/barrier/SSL/Fingerprints'. You can add the server to the trusted fingerprints on the client with the barrierc` command:

$ barrierc --enable-crypto hostname

@simons-public commented on GitHub (May 3, 2020): The `TIS/TSM` error happens on MacOS even when Barrier is working. Here is a [log from mine as an example.](https://gist.github.com/simons-public/02c6cdd2c1dfa2874bc5eb3241cb84cb) It seems like it might be an issue on the client side if you aren't seeing client connections in the server's logs. Can you test connecting to the server with the `openssl` comand on the client? For example: $ openssl s_client -connect hostname:24800 Also, check that you don't have old fingerprints (just like with ssh) in `~/.local/share/barrier/SSL/Fingerprints'. You can add the server to the trusted fingerprints on the client with the `barrierc` command: $ barrierc --enable-crypto hostname

gitea-mirror commented

2026-05-05 06:33:50 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 23, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:33:53 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

This has been fixed in #653 (reopening so that it does not appear that a bot just closed an issue for no reason).

@p12tic commented on GitHub (Jan 10, 2021): This has been fixed in #653 (reopening so that it does not appear that a bot just closed an issue for no reason).

No labels

Rows
Columns