Leaderboard

It seems that the Linux client does not have an SSL fingerprint generated. Can you try stopping Synergy on it and close/quit Synergy then reboot machine. After rebooting, launch Synergy and check if it generates an SSL fingerprint.

Hi @Loops. The closest reason that I can think of to be the reason for this is... Either; Your user account is an admin and runs Chrome with elevation(could also be using non-admin user account but elevated Chrome) but Synergy is not elevated to have admin rights. Or, Synergy is running with multiple instances(other instances does not have UI shown, plus elevated chrome and not elevated Synergy). What I usually do is to manually stopping the Synergy services either from services.msc or end process/end process tree in Taskmgr.exe.

I put both hosts into DEBUG mode and here's a snippet from the Server side during a Webex hangup. longrow = client milo = server [2017-07-26T14:00:20] NOTE: client "longrow" is dead [2017-07-26T14:00:20] INFO: jump from "longrow" to "milo" at 1280,720 [2017-07-26T14:00:20] INFO: entering screen [2017-07-26T14:00:20] DEBUG: active sides: 2 [2017-07-26T14:00:21] NOTE: accepted client connection [2017-07-26T14:00:21] DEBUG: received client "longrow" info shape=0,0 1920x1080 at 13,0 [2017-07-26T14:00:21] DEBUG: active sides: 2 [2017-07-26T14:00:21] NOTE: