mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #549] Service randomly stopped on MacOS Catalina 10.15.2 and won't start again #428
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#428
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @jojoharry16 on GitHub (Jan 31, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/549
Operating Systems
Server: Windows 10 version 1903 Build 18362.592
Client: MacOS Catalina 10.15.2
Barrier Version
Barrier v 2.3.2
Steps to reproduce bug
I'm afraid I can't repeat it since the service hasn't started since. I moved my mouse from MacOS to Windows and then couldn't move it back. Barrier is stuck on "Barrier is starting"
Other info
[2020-01-31T13:41:28] NOTE: connecting to '192.168.10.20': 192.168.10.20:24800
[2020-01-31T13:41:28] INFO: OpenSSL 1.0.2t 10 Sep 2019
[2020-01-31T13:41:28] NOTE: server fingerprint: A7:68:70:F5:B0:92:D1:42:B5:7F:B0:F1:24:BC:7C:F8:D8:EE:96:F6
[2020-01-31T13:41:28] NOTE: trustedServersFilename: /Users/CrazineX/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt
[2020-01-31T13:41:28] WARNING: failed to connect to server: Protocol error from server, check encryption settings
@the-wes commented on GitHub (Mar 3, 2020):
Please try disabling encryption temporarily on both systems to see if the problem goes away. If so, you can then re-enable encryption and it will probably work.
If that doesn't help, you should then get some new entries in the log, please share them here.
@github-actions[bot] commented on GitHub (Sep 30, 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.
@p12tic commented on GitHub (Jan 10, 2021):
Without additional information we can't solve this issue. I'm assuming the problem here is that the server does not accept the client due to misconfigured encryption. I've seen the same problem on Linux when it refused to accept too small RSA keys.