Jump to content

Failed to accept secure socket


Matt McMillen

Recommended Posts

Matt McMillen
Hi all, I have a fresh install of Synergy on a newly imaged Windows 7 SP1 machine that cannot connect to my Mac OS 10.10.3 client. I was using version 1.7.1 on both, then 1.7.3 and have tried 1.7.4, all generating the same log entries: 015-07-28T12:41:03] WARNING: failed to accept secure socket [2015-07-28T12:41:05] NOTE: accepted client connection [2015-07-28T12:41:08] INFO: watchdog status: ok [2015-07-28T12:41:19] WARNING: failed to accept secure socket [2015-07-28T12:41:22] NOTE: accepted client connection [2015-07-28T12:41:37] WARNING: failed to accept secure socket [2015-07-28T12:41:39] NOTE: accepted client connection [2015-07-28T12:41:54] WARNING: failed to accept secure socket [2015-07-28T12:41:56] NOTE: accepted client connection over and over and over. I have tried toggling SSL encryption on and off on both the server and client, which also doesn't help. The client shows a time out message while all this is going on. Any ideas for troubleshooting/resolution are most appreciated. *UPDATE* I realized yesterday that while I had 1.7.4 on my Win7 server, I did not have it on the Mac 10.10.3 client. I updated there, and can maintain a connection with SSL off on both the server and client. this is still not optimal though, as there are times I have a need to pass PII between machines. Still looking for a solution to allow use with SSL.
Link to comment
Share on other sites

  • 4 weeks later...
Scott Boutwell
[quote="Matt McMillen"]Hi all, I have a fresh install of Synergy on a newly imaged Windows 7 SP1 machine that cannot connect to my Mac OS 10.10.3 client. I was using version 1.7.1 on both, then 1.7.3 and have tried 1.7.4, all generating the same log entries: 015-07-28T12:41:03] WARNING: failed to accept secure socket [2015-07-28T12:41:05] NOTE: accepted client connection [2015-07-28T12:41:08] INFO: watchdog status: ok [2015-07-28T12:41:19] WARNING: failed to accept secure socket [2015-07-28T12:41:22] NOTE: accepted client connection [2015-07-28T12:41:37] WARNING: failed to accept secure socket [2015-07-28T12:41:39] NOTE: accepted client connection [2015-07-28T12:41:54] WARNING: failed to accept secure socket [2015-07-28T12:41:56] NOTE: accepted client connection over and over and over. I have tried toggling SSL encryption on and off on both the server and client, which also doesn't help. The client shows a time out message while all this is going on. Any ideas for troubleshooting/resolution are most appreciated. *UPDATE* I realized yesterday that while I had 1.7.4 on my Win7 server, I did not have it on the Mac 10.10.3 client. I updated there, and can maintain a connection with SSL off on both the server and client. this is still not optimal though, as there are times I have a need to pass PII between machines. Still looking for a solution to allow use with SSL.[/quote] Can confirm same results with windows 7 32bit boxes. Client and server both work without SSL enabled.
Link to comment
Share on other sites

Jorge Dardon
Same thing for me Windows 7 server machine and Windows 10 client machine. AFter the upgrade to 1.4.7 encryption no longer works. Same error as previous post. And also works without SSL enabled.
Link to comment
Share on other sites

  • 2 weeks later...
michael maskalans
Upgraded to 1.7.4 from unknown earlier versions (I had a drive failure on my server machine, and the synergy binary was one of the losses) where I had encryption manually configured and functional. Clients would no longer connect to the new server at all so I updated the clients. All is well with SSL off, but nothing will hold a conection with SSL enabled. The fingerprint showed on first launch of the server but not subsequently. It did prompt for matching fingerprints on the clients, once. server MacOS 10.11 build 15A278b client1 Windows 7sp1 fully updated client2 MacOS 10.10.4
Link to comment
Share on other sites

  • 2 weeks later...
Just updated to 1.7.4 on server and client and getting this as well. Without SSL client (Ubuntu 14.04 64-bit) works fine. With SSL turned on on the server (Win10 Pro 64-bit) client won't connect.
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...