Waterfox 0 Posted January 3, 2020 Share Posted January 3, 2020 I was having this problem on a new installation of Synergy, version 1.11.0-stable-b2173efb Toggling SSL off and back on did not make a cert generate. I have Windows Subsystem for Linux (WSL) and so I was able to follow planetehack's above instructions in the installed copy of debian. Now it works perfectly! Link to post Share on other sites
BagronkeN 0 Posted January 3, 2020 Share Posted January 3, 2020 3 hours ago, Sam Aaron said: Hi there, I'm seeing the issue with an absent SSL cert too. I'm running the 1.11.0 server on Windows 10. I upgraded from Basic to Pro. I tried disabling and re-enabling SSL to no avail. I also tried uninstalling and re-installing Synergy - again to no avail. Is there any way to force Synergy to generate a cert? You can generate one manually outside of Synergy (but takes some tinkering). It might be worth testing to install an older version and see if that generates a cert, and then upgrade to the latest version. Also please consider contacting Synergy support, they are apparently not monitoring the forum for bugs, but are relying on tickets/support emails. Link to post Share on other sites
Popular Post ldlx 2 Posted January 4, 2020 Popular Post Share Posted January 4, 2020 Have a look here: https://github.com/symless/synergy-core/issues/6608 --> https://github.com/symless/synergy-core/commit/1bc2cf57d90533bc3a4f4a029f4bab74caa12275 Workaround: move/copy openssl.exe and synergy.conf from the OpenSSL-subdir to the Synergy program folder. 2 Link to post Share on other sites
JohnLBevan 0 Posted January 8, 2020 Share Posted January 8, 2020 Note: Regarding the fix suggested by PlanetHack, a new bug in Git Bash may cause the initial slash in the subject to be expanded to the Git Bash exe's path. Quote writing new private key to 'synergy.key' ----- name is expected to be in the format /type0=value0/type1=value1/type2=... where characters may be escaped by \. This name is not in that format: 'C:/Program Files/Git/... To avoid that, use two slashes for the certificate's subject. See https://stackoverflow.com/a/54924640/361842 for more. cd '/c/Users/myUsername/AppSettings/Local/Synergy/SSL' openssl req -nodes -new -x509 -keyout synergy.key -out synergy.cert -days 3650 -sha256 -subj "//CN=myComputerName" cat synergy.key synergy.cert > synergy.pem rm -f synergy.key synergy.cert Thanks @PlanetHack for the fix! Link to post Share on other sites
Popular Post Jamie Newbon 19 Posted January 15, 2020 Popular Post Share Posted January 15, 2020 Hi, There is a development build available that has a fix for this issue in it, could you please give it a go Synergy v1.11.1-snapshot Thanks Jamie 4 2 Link to post Share on other sites
Sam Aaron 0 Posted January 15, 2020 Share Posted January 15, 2020 Hi there, I managed to resolve the issues manually by generating the SSL certs using a WSL shell. Great to see that you're working on fixing the issue though :-) Link to post Share on other sites
likearaptor 0 Posted January 15, 2020 Share Posted January 15, 2020 4 hours ago, Jamie Newbon said: Hi, There is a development build available that has a fix for this issue in it, could you please give it a go Synergy v1.11.1-snapshot Thanks Jamie This fixed it for me Link to post Share on other sites
Screech 0 Posted January 21, 2020 Share Posted January 21, 2020 On 1/15/2020 at 6:00 AM, Jamie Newbon said: Hi, There is a development build available that has a fix for this issue in it, could you please give it a go Synergy v1.11.1-snapshot Thanks Jamie Thanks Jamie, this snapshot build worked for me as well. Link to post Share on other sites
wesruv 0 Posted January 24, 2020 Share Posted January 24, 2020 (edited) Had the same problem, Windows 10 Pro on both server and client Disabling/Re-enabling TLS did not help Used GitBash in Windows following @planetehack's instructions and problem was fixed immediately. @planetehack++ Edited January 24, 2020 by wesruv Accidental submit Link to post Share on other sites
Dave T 0 Posted January 26, 2020 Share Posted January 26, 2020 The snapshot worked for me to. Thanks! Link to post Share on other sites
windracer 0 Posted January 28, 2020 Share Posted January 28, 2020 +1 for the snapshot. Thank you! Link to post Share on other sites
Shawn Hall 6 Posted January 28, 2020 Share Posted January 28, 2020 Thank you, @ldlx - moving openssl & the synergy.conf into the synergy folder solved it for me. Link to post Share on other sites
Pioto 0 Posted January 29, 2020 Share Posted January 29, 2020 (edited) The snapshot version did work for me as well, insofar as it generated a .pem file. However, my Windows server (where I installed the snapshot) and my Mac client don't seem to agree on the fingerprint of the server. Eyeballing, the fingerprint shown on my client is nothing like the one shown on the server. Upgrading the client to the snapshot as well does show the expected fingerprint, though. edit: one other oddity: client shows "Synergy is connected (with TLSv1.2)", while the server shows "Synergy is connected (with TLSv1.3)" in the status bar. Logs on both ends show they only negotiated TLSv1.2. Edited January 29, 2020 by Pioto one more observation i missed Link to post Share on other sites
Guest Posted February 4, 2020 Share Posted February 4, 2020 Hello Guys. Thank you all for your answers. If someone still has an issue, can you please use the link in my signature and create a ticket for us? So, we will check closer with the dev team. Link to post Share on other sites
TiiiMMMaHHH 1 Posted February 5, 2020 Share Posted February 5, 2020 For what it's worth, this is a confirmed bug due to a bad port that got overlooked: https://github.com/symless/synergy-core/issues/6608 Just copy openssl executable and the conf file one directory up and you'll be good until the next release when things are corrected presumably. 1 Link to post Share on other sites
Captinde 1 Posted February 6, 2020 Share Posted February 6, 2020 On 1/15/2020 at 6:00 AM, Jamie Newbon said: Hi, There is a development build available that has a fix for this issue in it, could you please give it a go Synergy v1.11.1-snapshot Thanks Jamie Thanks Jamie, that worked like a charm. Link to post Share on other sites
marinegeek23 1 Posted March 5, 2020 Share Posted March 5, 2020 The snapshot worked for me as well - thank you! Link to post Share on other sites
Cymatics 0 Posted March 13, 2020 Share Posted March 13, 2020 I fixed this issue by using teamviewer, but this could be solved by using any regular flash drive. My Windows 10 version was upgraded to pro, but did not create the Synergy.pem file. I copied the synergy.pem file off of my macbook and placed it onto my Windows pc in the directory that it said it was missing. It didn't work at first, but I turned TLS off and turned it back on, and now I'm connecting just fine using TLSv1.2. I also opened the synergy.pem file with notepad. Link to post Share on other sites
Mr. Anderson 1 Posted March 15, 2020 Share Posted March 15, 2020 Hi, I Removed synergy_1.10.3.stable from my client and server following the "Reinstall from Fresh" guide and installed: synergy_v1.11.0-stable and was unable to connect. I read Jamie's post, downloaded the snapshot and installed it over my server install and now I could connect. Then just to be consistent I installed it over my client. Thank you Jamie's Post: There is a development build available that has a fix for this issue in it, could you please give it a go Synergy v1.11.1-snapshot Thanks Jamie Jamie Newbon Link to post Share on other sites
Abrases 0 Posted March 18, 2020 Share Posted March 18, 2020 On 15/03/2020 at 8:56 AM, Mr. Anderson said: Hi, I Removed synergy_1.10.3.stable from my client and server following the "Reinstall from Fresh" guide and installed: synergy_v1.11.0-stable and was unable to connect. I read Jamie's post, downloaded the snapshot and installed it over my server install and now I could connect. Then just to be consistent I installed it over my client. Thank you Jamie's Post: There is a development build available that has a fix for this issue in it, could you please give it a go Synergy v1.11.1-snapshot Thanks Jamie Jamie Newbon Thanks it fix the issue for me ! Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now