Synergy 1.4.14 fails with "Protocol error"
Solution 1
Due to a change in the encryption protocols that Synergy uses - irrespective of server/client OS - password mis-matches can end in the following error:
synergy protocol error from server
Resetting (or removing) the password should allow successful connections.
- Linux:
Edit > Settings
- MacOS:
⌘
/Synergy > Preferences
- Windows:
Edit > Settings
(?)
Solution 2
I've been having this problem too, and here's what I did:
1) Confirmed that (Linux) client had the bold server IP entered as its server IP. Note: My server Synergy window has three IP addresses listed and one of them is bold/current.
2) Looked at the top bar of my Linux client and noticed several instances of Synergy running, so I quit all of them.
3) Stopped client and server, then started server, then started client.
Now the logs just show entering screen/leaving screen and they are calm again.
Related videos on Youtube
Peter Westlake
Updated on September 18, 2022Comments
-
Peter Westlake almost 2 years
Server: Debian testing, with the 1.4.14 deb downloaded and installed. Client: Windows 7, with 1.4.14 downloaded and installed. Both are Premium.
On Debian, start the server with
synergys -f -c synergy.conf
, because running it from the KDE menu makes it give an error "Option not supported on Linux: --enable-drag-drop" (and incidentally I can't find any file that might be telling it to use that option).On Windows, run the client. Both are using encryption, with a simple password to be sure it's correct. The client says "WARNING: failed to connect to server: Protocol error from server", and the server says "NOTE: new client disconnected".
I haven't changed any configuration except the password, and 1.4.12 worked on the same machines just minutes ago.
-
Topher Fangio almost 10 yearsThis was exactly my issue; try stopping the service and resetting the password on both machines, and then restarting the service (server first, then client).
-
protongun almost 10 yearsMy issue was also encryption password related. I forgot the configure the client with the same encryption password as on the network. A more helpful error than "protocol error from server" like "decryption failed" would have been helpful though
-
Danny Staple almost 10 yearsOdd - I can only make it work with no password. Even a very simple password set at both ends fails.
-
Alastair over 9 years@Nocturne , after a lot of searching, I found the hidden menu and I've added directions above.