All Activity

The tilde is not working 🤨

I agree with LaFemmeLoca: the whole reason I use Synergy is that I need access to an older program that won't run on anything newer than macOS10.13.6. I'd still like to know if both computers need to run the same version of Synergy, or if I can use Synergy 1 on my old computer (running macOS10.13.6) and Synergy 3 on my newer computer (running macOS14.4.1).

I hope when you end of life Synergy 1 Pro that you will then figure out how to connect to macOS 10.13.6 because it is my second 'monitor' that I use for certain things and would love to continue to use it after 2028. Otherwise, I will have no need for your product. :(

Older post I realize, but posting an answer anyway as I experienced this same error message recently. For me, the issue was with a Chrome window prompt pending a confirmation. Once I closed that window my keyboard worked again as usual.

On Synergy1, try to use the MacOS as server and Windows as client, it solved the issue on my computers.

How is this still not fixed. Version: 3.0.79.1-rc3

I spoke with their support on this issue. If you're going to copy images from Mac to Windows, they can't be files (including image files). It has to be "clippings" or screenshots. So just do your usal Command + Shift + 4 while also adding "control" (yes my hand looks like a Velociraptor now). Once you're in Windows you can paste the clipping in either Paint, OneNote or whichever image software you're using.

Conscious meetings: Dating without limitations Authentic Maidens [URL=https://datesnow.life]Top-notch Сasual Dating[/URL]

I am also having this problem on my M2 Pro Macbook Pro. Ubuntu box is my primary machine and I have my Macbook off to the side. After a while the Mac will fall asleep and I have to physically press a button on it to wake it up. I have verified that: wake for wifi access enabled on the Mac allow Synergy to control at login screen is enabled Regarding "Elevated privleges", this option no long seems to be available in Synergy?

They have NOT fixed the webpage. Incredibly frustrating. Still waiting to hear from support.

What was your experience to get it work properly? I am also using V3 ultimate with no such luck. I am using a Mac as the master.

Yes. Well I’m using the latest, V3 Ultimate.

Did this ever get sorted out? I know it has been a question since version 1.1xxx Im asking 6 months later than the previous poster.

I bought the Synergy 3 RC3 v3.0.79.1-rc3 and set up my Mac Studios as the sever with a Dell Inspiron laptop as the client. I am using a Dell U3223QE monitor and everything was working okay with the Logitech mouse and MX key S keyboard. Today (the day after setting the system up) I could not get my Mac Studio to wake up. I could see the mouse but the keyboard would not work to put in my password on the Mac. I had to use the Mac keyboard to wake up my Mac. I am new to the Logitech keyboard and to Synergy, so I may be missing something about getting my Mac to wake up using the connected Logitech keyboard. Any ideas, hotkey settings, anyone know how to make it work?

You need to use the option "--enable-crytpo" to use TLS encryption, see below my working synergy-client.service file. [Unit] Description=Synergy Service Requires=display-manager.service After=display-manager.service [Service] Type=simple Restart=always RestartSec=3 ExecStartPre=/bin/bash -c "sleep 10; /bin/systemctl set-environment LIGHTDMXAUTH=/var/run/lightdm/root/:0" ExecStart=/bin/bash -c "XAUTHORITY=${LIGHTDMXAUTH} /usr/bin/synergyc -f --enable-crypto -n CLIENT_NAME SERVER_ADDRESS" [Install] WantedBy=graphical.target I managed to get it working with lightdm, but didn't have the same luck with sddm.

I had the same issue installing Debian 11 version on Debian 12. Thought I would give the Ubuntu 22 version a go, and was successful. Installed with `sudo dpkg -i <synergy-ubuntu-file-name>` Could then configure it as per normal. Hope it helps someone (or myself) in the future.

I ran into this issue after updating to RC3 with Ubuntu 22.04 as primary and Windows 11 as a client. I was able to resolve this by resetting my configuration on both devices and re-configuring them.

Awesome thank you that solved it!

Hi Mickey 👋 Would you mind opening a support ticket so we can help you fix the problem? I know you said you don't want help, but I hope you reconsider, since it's normally a very simple problem. Most issues with Synergy 3.0 RC and Synergy 3.1 Beta are a simple fix and we have workarounds for many known bugs. Thank you for your patience while we work our way toward a stable release! I really appreciate you being a customer and sticking with us 🙂

Could you try following the reset procedure below and see if that helps: Open Synergy Navigate to Local settings Press the Reset options button Select reset all computers Repeat steps 1-4 for each computer Important - restart each computer as some config files may be held in memory After the restart open Synergy again and follow the setup instructions

Hi, Is it possible to get a Scientific linux 6.10 version with Synergy-1.3.4-2.el6.rf installed to talk to Synergy 3? I've sat this up before, but then on older versions of Synergy. If not, are there any updates for Linux that will fit Scientific Linux 6.10?

Hi, I randomly had this issue crop up with Synergy 3 RC2 and updated to RC3, where it persists. Everything was working fine for months until today. I use a KVM switch, and the cursor is invisible for the client machine. If I connect a separate mouse to the client machine, everything works fine. I've read where some people had scroll lock enabled. That wasn't the case here. I also reset Synergy on both computers and restarted them and reset my router, but none of that changed anything. Please help me fix this so I don't have to have a separate mouse installed on the client!

what does it take to get supports attention? could anyone please help to point support to this thread? thank yo

Thank you, Jason. For my part I have four computers (win7,win8,win10 and win11) The win7 is the synergy server and I was just adding the win11. The win7 (left),10 (middle) and 11 (right) are all across and the win10 (top) is above the win8. The new win11 box was registering with the win7 server, but the mouse would not go in to it. I restarted the synergy service on both and it had no effect. I rebooted both, but still the problem persisted. I just happened to need to reboot the win8 (the middle one) for a disk check (some bad areas on an external drive), and that (somehow) solved the problem. Ironically it was the intermediary client that was the problem all along. The server (win7) was seeing the win11 computer and the win11 client was detecting the server, so there was so initial connectivity problem, just a win8 box being a jerk.

Hey! I've got two windows 10 machines and a Mac that's the keyboard/mouse server. One windows machine has no issues connecting to the Mac, but the second one I get TLS errors. I've updated the synergy version on both machines, removed and reinstalled it, tried setting a manual config, disabled windows firewall, verified both machines are on the same network, and I can't figure out what's going on. This is the error log from the Mac side: synergy-core [2024-02-17T00:20:54] - DEBUG - opening new socket: 0103D410 synergy-core [2024-02-17T00:20:54] - DEBUG - openssl version: OpenSSL 3.2.0 23 Nov 2023 synergy-core [2024-02-17T00:20:54] - DEBUG1 - openssl flags: compiler: clang -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -D_REENTRANT -DOPENSSL_BUILDING_OPENSSL -DNDEBUG synergy-core [2024-02-17T00:20:54] - DEBUG1 - openssl built on: built on: Thu Nov 23 13:20:19 2023 UTC synergy-core [2024-02-17T00:20:54] - DEBUG1 - openssl platform: platform: darwin64-arm64-cc synergy-core [2024-02-17T00:20:54] - DEBUG1 - openssl dir: OPENSSLDIR: "/opt/homebrew/etc/openssl@3" synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=1 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=2 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=3 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=4 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - checking clipboard synergy-core [2024-02-17T00:20:54] - DEBUG2 - flags: 0 synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=5 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=6 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=7 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:54] - DEBUG2 - want to read, error=2, attempt=8 synergy-core [2024-02-17T00:20:54] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=9 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=10 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=11 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=12 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=13 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=14 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=15 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=16 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=17 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=18 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=19 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=20 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=21 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=22 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=23 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=24 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=25 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=26 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=27 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=28 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - checking clipboard synergy-core [2024-02-17T00:20:55] - DEBUG2 - flags: 0 synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=29 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:55] - DEBUG2 - want to read, error=2, attempt=30 synergy-core [2024-02-17T00:20:55] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=31 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=32 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=33 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=34 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=35 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=36 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=37 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=38 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=39 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=40 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=41 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=42 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - want to read, error=2, attempt=43 synergy-core [2024-02-17T00:20:56] - DEBUG2 - retry accepting secure socket synergy-core [2024-02-17T00:20:56] - DEBUG2 - accepting secure socket synergy-core [2024-02-17T00:20:56] - ERROR - tls error occurred (generic failure) synergy-core [2024-02-17T00:20:56] - ERROR - openssl error: error:0A000126:SSL routines::unexpected eof while reading synergy-core [2024-02-17T00:20:56] - ERROR - failed to accept secure socket synergy-core [2024-02-17T00:20:56] - WARNING - client connection may not be secure synergy-service [2024-02-17T00:20:56] - DEBUG2 - send notify electron errorCount synergy-service [2024-02-17T00:20:56] - DEBUG2 - send notify electron errorCount synergy-service [2024-02-17T00:20:56] - DEBUG2 - send notify electron errorCount synergy-core [2024-02-17T00:20:56] - DEBUG2 - writef(CALV) synergy-core [2024-02-17T00:20:57] - DEBUG2 - wrote 4 bytes synergy-core [2024-02-17T00:20:57] - DEBUG2 - writing secure socket: 0x600002218000 synergy-core [2024-02-17T00:20:57] - DEBUG2 - flags: 0 And this is the windows 10 machine: synergy-core [2024-02-16T23:30:56] - WARNING - failed to connect to server: Timed out synergy-core [2024-02-16T23:30:56] - DEBUG - retry in 1 seconds synergy-core [2024-02-16T23:30:57] - NOTE - connecting to '192.168.0.100': 192.168.0.100:24800 synergy-core [2024-02-16T23:30:57] - DEBUG - opening new socket: 327A7BB0 synergy-core [2024-02-16T23:30:57] - DEBUG1 - bind to network interface: 192.168.0.115 synergy-core [2024-02-16T23:30:57] - DEBUG1 - connecting to server synergy-core [2024-02-16T23:30:57] - DEBUG1 - connected; wait for hello synergy-core [2024-02-16T23:30:59] - DEBUG - closing socket: 327A7BB0 synergy-core [2024-02-16T23:30:59] - DEBUG1 - connection timed out synergy-core [2024-02-16T23:30:59] - WARNING - failed to connect to server: Timed out synergy-core [2024-02-16T23:30:59] - DEBUG - retry in 1 seconds synergy-core [2024-02-16T23:31:00] - NOTE - connecting to '192.168.0.100': 192.168.0.100:24800 Other thing of note is the windows machine is a fresh install of windows 10 pro. There's no anti-virus or firewall software installed on it beyond windows defender which is disabled.