Shangrila Posted December 28, 2017 Share Posted December 28, 2017 I have just finished setting up a second configuration where an older Dell Precision owns the keyboard and mouse and dual-boots Windows 10 and Centos 7. A MacBook Pro shares the keyboard and mouse. This is working fine for me even when I reboot between Windows and Linux (Centos). The Centos side didn't work at first, even after following the Drew2Apps cleanup procedures for Linux. However, after I repeated the procedures, including removing the Synergy 2.0.4 install and re-installing it, Synergy came up running fine. Note: I found the ~/.config files to be removed during the cleanup were not quite the same as Drew2Apps indicated when I did this. In my case only ~/.config/Symless was there to be removed. Quote Link to comment Share on other sites More sharing options...
Robert Fury Posted December 29, 2017 Share Posted December 29, 2017 Same issue, so frustrating. And the fact I can't config Synergy 2 manually. [ Config ] [2017-12-28T22:12:04] debug: service cloud connection error [ Config ] [2017-12-28T22:12:04] debug: current version is update to date [ Service ] [2017-12-28T22:12:04] debug: got user auth token: [ Service ] [2017-12-28T22:12:05] debug: retrying cloud connection [ Service ] [2017-12-28T22:12:05] debug: closing existing websocket connection [ Service ] [2017-12-28T22:12:05] error: websocket read error 335544539: short read [ Service ] [2017-12-28T22:12:05] debug: clearing last profile snapshot [ Service ] [2017-12-28T22:12:05] debug: retrying websocket connection in 26s [ Service ] [2017-12-28T22:12:05] debug: retrying websocket connection now Quote Link to comment Share on other sites More sharing options...
AskMP Posted December 30, 2017 Share Posted December 30, 2017 Synergy 2 has not worked for days, now constantly giving errors connecting to auto-config and when multiple computers do connect, they don’t show on either. Mac <-> Windows Quote Link to comment Share on other sites More sharing options...
MadMonkey Posted December 30, 2017 Share Posted December 30, 2017 Same here it worked for a couple a days then when I reset one of my computers I could not get it to work again. Whats the deal with that???????????? Quote Link to comment Share on other sites More sharing options...
MadMe86 Posted December 30, 2017 Share Posted December 30, 2017 At the moment it works for me...again. it would be nice if it would be possible to get rid of the cloud... i had not tested 1.8... if it keeps that way i will give it a try... Quote Link to comment Share on other sites More sharing options...
Guest Andrew Nelless Posted January 5, 2018 Share Posted January 5, 2018 On 12/18/2017 at 6:21 AM, ameyp said: [ Service ] [2017-12-18T11:44:15] debug: connecting websocket: pubsub1.cloud.symless.com:443 pubsub1.cloud.symless.com uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is not valid for the name pubsub1.cloud.symless.com. Error code: SEC_ERROR_UNKNOWN_ISSUER @ameypI've posted an explanation of this behaviour here Quote Link to comment Share on other sites More sharing options...
Chris Van Doren Posted January 11, 2018 Share Posted January 11, 2018 (edited) Worked the first day I upgraded about a week ago and hasnt worked since for me either from a Windows 10 PC server to a Mac client. I've been a customer of the old version for over 10 years; paying for this upgrade seems to have been a mistake. Edited January 11, 2018 by Chris Van Doren 1 Quote Link to comment Share on other sites More sharing options...
Dr Hien Posted January 15, 2018 Share Posted January 15, 2018 also not working second day. for all the marketing on the site guaranteeing seamless functioning total let down Quote Link to comment Share on other sites More sharing options...
MadMe86 Posted January 15, 2018 Share Posted January 15, 2018 (edited) Check your Network... for me it works... My System is working flawless... whats your configuration? Edited January 15, 2018 by MadMe86 Question added 1 Quote Link to comment Share on other sites More sharing options...
Dr Hien Posted January 16, 2018 Share Posted January 16, 2018 connecting 2 macs on the same LAN just stopped working sees computer does not share mouse Quote Link to comment Share on other sites More sharing options...
Eric Powell Posted January 17, 2018 Share Posted January 17, 2018 I've been having the same problems. Working one day, not the next, and nothing can change it's mind about working when it wants to. The problem for me centers around the Mac computer (I have 1-Mac, 2-Win, 1-Linux.) When the Mac is in the equation, everything is random as to whether it works or not. When it works, it works well; when it stops working, go home. You take the Mac computer out of the equation, and everything works reliably, pretty much without a glitch. Put the Mac back in and it all goes to the bottom of the cesspool. I've been updating as new releases are out, and I'm currently on 2.0.4, and have been since back in December. Waiting for the next release to install it again on my Mac. Quote Link to comment Share on other sites More sharing options...
Daniel K Posted January 17, 2018 Share Posted January 17, 2018 Same problem here. But I resolved it by restarting the Synergy service from both PCs. Quote Link to comment Share on other sites More sharing options...
epaul Posted January 18, 2018 Share Posted January 18, 2018 I had the same issue with 2.0 as most of the others and I'm using Mac High Sierra, it worked for about 1 week, but got flakey yesterday and today. Today I couldn't even get it to work, so I gave up and went back to 1.8 which is working fine now. I take another stab at 2.x when another release happens... Quote Link to comment Share on other sites More sharing options...
samr Posted January 18, 2018 Share Posted January 18, 2018 2 hours ago, epaul said: I had the same issue with 2.0 as most of the others and I'm using Mac High Sierra, it worked for about 1 week, but got flakey yesterday and today. Today I couldn't even get it to work, so I gave up and went back to 1.8 which is working fine now. I take another stab at 2.x when another release happens... Yeah, 2.1 is supposed to be better but who knows ¯\_(ツ)_/¯. Quote Link to comment Share on other sites More sharing options...
Telmo Cardoso Posted January 19, 2018 Share Posted January 19, 2018 One thing I noticed... it might help support to dig into one more issue. I have Windows and OSX connected. When I put windows to sleep in the next morning when it wake up it can no longer connect to OSX. I need to manually restart services in order for it to connect again. Quote Link to comment Share on other sites More sharing options...
Popular Post Nerdaddy Posted January 19, 2018 Popular Post Share Posted January 19, 2018 I had this aswell. My setup is 2 64bit Windows 10 machines. Everything fine after install, but on day 2 it wouldn't work. If I rebooted the machines then it would start working again, but this is not how most people operate these days. For me, I 99% of the time just hit the power button on my laptops which put the machines into Hibernation, meaning when I hit the power again, the machine just restarts where I'd left off. I'm guessing this is what most other people do as well. Resarting the synergy service manually on my slave machine fixed my connection. So, what I have done is to make a little batch file thats start and stops the service. net stop Synergy net start Synergy I've saved in into a file named RestartService.bat into the folder C:\Program Files\Synergy And then using the Task Scheduler in windows, created a new task that triggers the batch file upon resume from hibernation. TRIGGER Begin the Task -> On an Event Log -> System Source -> Power-Troubleshooter Event ID -> 1 ACTION Action -> Start a Program Program/Script -> "C:\Program Files\Synergy\RestartService.bat" GENERAL Security Options Run whether user is logged in or not (selected) Run with highest privileges (checked) I've put this on both my machines and as long as I un-hibernate the machines in the correct order, i.e, master first, then slave, so far it seems to be working. Hope my work around helps others until Symless get it sorted properly. Regarding the real issue, my guess is its down to the ports used and the fact that when resuming from hibernation, the code in Synergy isn't getting a new port and so within your network, your router doesn't have a path to route the traffic to the other machine. Just a guess though. 2 Quote Link to comment Share on other sites More sharing options...
GranPaSmurf Posted January 19, 2018 Share Posted January 19, 2018 Nerdaddy, I like the idea of a quick script. On my Win 7, I was having a hard time with Synergy 2.04 staying connected. I drug a shortcut to the 'services' section of Component Services over to the task-bar. Then restarting the service is just a couple of clicks. I've noticed that after an update or reinstall, this restarting of the service is needed. After a few restarts, or a couple of days, something along the line 'learns' and the connection becomes more reliable. 1 Quote Link to comment Share on other sites More sharing options...
eee Posted January 19, 2018 Share Posted January 19, 2018 (edited) Yep, got those problems too. On my Linux (Arch) machine: [ Service ] [2018-01-19T19:17:04] error: websocket handshake error 3: WebSocket upgrade handshake failed [ Service ] [2018-01-19T19:17:04] error: websocket handshake response 400: Bad Request Edited January 19, 2018 by eee Quote Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted January 26, 2018 Synergy Team Share Posted January 26, 2018 Sorry about that. Have you raised a support ticket yet? https://symless.com/contact/customer-support Quote Link to comment Share on other sites More sharing options...
n0mad Posted January 30, 2018 Share Posted January 30, 2018 Same here. Just paid for version 2, doesn't work at all. OSX Server / Windows Client. Also why not leave us an option to use LAN-only connections? Quote Link to comment Share on other sites More sharing options...
Guest Steve Williams Posted January 31, 2018 Share Posted January 31, 2018 Hi n0nad, Part of the Synergy 2 philosophy is to make the product as simple to use as possible for as many people as possible, so we abstract away the networking layer to further this objective. That said, we have upcoming features to detect the fastest network to use as well as an option to allow the user to nominate which network to use. Look out for this in Synergy 2.1. It would be great if you could raise a support ticket (https://symless.com/contact/customer-support) and we'll take a look at what's going on in your environment. Steve Quote Link to comment Share on other sites More sharing options...
Ditta Posted January 31, 2018 Share Posted January 31, 2018 (edited) Thanks you for the response, Steve. From your reply, it seems that you believe that n0nad's experience is quite isolated. As you will find on this thread that this is an experience shared by many other paying users. Can I please request that you take time to thoroughly test 2.x yourselves before hoisting it on customers? It will also be useful if you could provide access to older versions that worked (e.g 1.8) whilst you take your time to address these issues. Edited January 31, 2018 by Ditta Quote Link to comment Share on other sites More sharing options...
Guest Steve Williams Posted January 31, 2018 Share Posted January 31, 2018 11 minutes ago, Ditta said: From your reply, it seems that you believe that n0nad's experience is quite isolated. As you will find on this thread that this is an experience shared by many other paying users. Can I please request that you take time to thoroughly test 2.x yourselves before hoisting it on customers? Hi Ditta, I fully appreciate that some users experience issues, but its far from every Synergy 2 user. The best way to help us make the product better is to raise tickets with our support system - https://symless.com/contact/customer-support. This allows us to analyze and understand any issues being experienced and take forward steps to address them in future product updates. Steve Quote Link to comment Share on other sites More sharing options...
Popular Post GranPaSmurf Posted January 31, 2018 Popular Post Share Posted January 31, 2018 (edited) Thanks for the perspective Steve. Issues and problems are reported and accumulate here. It doesn't mean EVERY Synergy user has the same issues. If a doctor sees patients all day that all, 100%, have the flu, that doesn't mean that the whole population, 100%, have the flu. If you skim the forum, you will see a bunch of users with problems. That's OK, they're supposed to be here. Another quick skim will turn up a lot of "thanks, that worked" messages. As always, the support team should have a support ticket for every issue raised here on the forum, even if we are able to suggest a quick fix, Support tickets help drive the direction of development. https://symless.com/contact/customer-support Edited February 9, 2018 by GranPaSmurf grammar 2 1 Quote Link to comment Share on other sites More sharing options...
Popular Post n0mad Posted January 31, 2018 Popular Post Share Posted January 31, 2018 Update: (on my host, OSX) force-closing synergy-config seemed to solve this for me as well. Besides this minor inconvenience, everything else works flawlessly. Hope to see this bug fixed soon. Thanks. 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.