Jialing

Synergy 2 is not working 2nd day

23 posts in this topic

Synergy 2 was working on the first day installation. Then, at the 2nd day, they are not connected. I wonder it's because my two devices (Mac OX X 10.11.6 and Windows 10)

I wonder it's because my devices' IP are assigned dynamically daily from startup in the morning. Because I need to use Synergy instantly, after several restart the services or reboot computers fail, I have to uninstall Synergy 2 and re-install Synergy 1. Therefore, the error log file was not saved. I'll obtain error log next try. Just let you know that my working environment will have both devices in dynamic IP after restart computers.  

(As to Synergy 1, I have to changed IP on the client side.)

Share this post


Link to post
Share on other sites

I have the same issue. Worked perfect the first day, but the second day it stopped. Same machines you're using too. I contacted support and they said this weekend they'll have a new release hopefully to fix this.

  • Like 1

Share this post


Link to post
Share on other sites

I'm seeing "There was a problem connecting to the auto-config service. Retry"

The console log just shows this:

[ Service ] [2017-12-12T21:43:07] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:43:08] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:43:08] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:43:08] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:43:08] debug: service cloud connection error
[ Service ] [2017-12-12T21:43:08] debug: retrying websocket connection in 21s
[ Service ] [2017-12-12T21:43:29] debug: retrying websocket connection now
[ Service ] [2017-12-12T21:43:29] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:43:30] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:43:30] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:43:30] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:43:30] debug: service cloud connection error
[ Service ] [2017-12-12T21:43:30] debug: retrying websocket connection in 19s
[ Service ] [2017-12-12T21:43:49] debug: retrying websocket connection now
[ Service ] [2017-12-12T21:43:49] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:43:50] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:43:50] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:43:50] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:43:50] debug: service cloud connection error
[ Service ] [2017-12-12T21:43:50] debug: retrying websocket connection in 19s
[ Service ] [2017-12-12T21:44:09] debug: retrying websocket connection now
[ Service ] [2017-12-12T21:44:09] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:44:10] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:44:10] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:44:10] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:44:10] debug: service cloud connection error
[ Service ] [2017-12-12T21:44:10] debug: retrying websocket connection in 25s
[ Service ] [2017-12-12T21:44:35] debug: retrying websocket connection now
[ Service ] [2017-12-12T21:44:35] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:44:35] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:44:35] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:44:35] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:44:35] debug: service cloud connection error
[ Service ] [2017-12-12T21:44:35] debug: retrying websocket connection in 8s
[ Service ] [2017-12-12T21:44:43] debug: retrying websocket connection now
[ Service ] [2017-12-12T21:44:43] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:44:44] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:44:44] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:44:44] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:44:44] debug: service cloud connection error
[ Service ] [2017-12-12T21:44:44] debug: retrying websocket connection in 11s
[ Service ] [2017-12-12T21:44:55] debug: retrying websocket connection now
[ Service ] [2017-12-12T21:44:55] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-12T21:44:56] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-12T21:44:56] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-12T21:44:56] debug: clearing last profile snapshot
[ Config  ] [2017-12-12T21:44:56] debug: service cloud connection error
[ Service ] [2017-12-12T21:44:56] debug: retrying websocket connection in 25s

If we constantly have a dependence on being connected to this auto-config service then this could be a bit of a problem...

 

Share this post


Link to post
Share on other sites

I have Synergy 2.0.3 on my Windows 10 laptop and MacBook 10.12.6. The Synergy app just doesn't show on my desktop on the Mac. I have tried restarting the MacBook and also Force Quitting down the Synergy app.

This is been going on since 2.0. beta. Only 2.0.1 ever worked.

Really getting annoyed with this app.

Share this post


Link to post
Share on other sites

Ditta,

I too am getting annoyed with this app.  Have been using it for 5+ years and now with this 2.0 version it is clearly it was released without proper testing.  I cannot connect a mac and centOS7 box.  Both are able to see the correct layout and I have restarted both computers.  I have just now force quit on the mac and now when I start the app back up, it is no where to be seen.  I can see it under "ps -ef  | grep synergy".

Had high hopes for this product but it is quickly becoming so much more of a hassle than a help that I am considering uninstalling it completely and not returning

Sorry I am not much of a help, I just needed to express my frustrations and its glad to know its not just me.

Share this post


Link to post
Share on other sites

I too am running the new 2.0.3.  I run 3 windows 10 pc's.  Scroll and copy/paste don't work on my other pc's when Chrome is open in my main pc.  Connection is still an issue as well.  Love this program getting annoyed too.

Share this post


Link to post
Share on other sites

Same ... Love the program in the past and at first love the increased responsiveness of 2.0 BUT it will not link and I dont like that you cant self configure like 1.0 this is frustrating shouldnt have paid the $20 for 2.0 at this rate ......

Share this post


Link to post
Share on other sites

Purchased upgrade this morning - only 5 days to go buy it now. Installed on both machines W10 latest updates. When I right click on the screen I want to be controller and select share from then the white dot moves on both machines and the other machine has a waiting time line on it that keeps flashing on and off. So they are communicating on some level - just doesnt want to share my keyboard and mouse.

More wasted time.

Share this post


Link to post
Share on other sites

I just followed the steps which Drew2Apps posted above and now this works!

I didn't need to re-boot on my second machine after following those steps, it just worked after installing "fresh" :)

 

Share this post


Link to post
Share on other sites

I only run it on 2 windows 10 machines - uninstalled synergy, installed mouse without borders works perfectly again.

Share this post


Link to post
Share on other sites

Just dropping a note to see if anyone else is in my same boat -- I usually run the app across two Fedora machines.  Version 2 is definitely not ready for primetime on this platform.  2.0.2 was OK at first, then stopped working.  2.0.3 no better.  Went back to 1.8 and all is well.  

Share this post


Link to post
Share on other sites

It looks like pubsub1.cloud.symless.com is using a self signed certificate. curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none. I suspect the issues will clean them self's up once the problem with the certificate is resolved.

Cheers

Share this post


Link to post
Share on other sites

Bought this at the start of the week and my needs are to use between two macs at office. Worked perfectly the first day. Just before heading home, I closed a bunch of windows and one of them was of Synergy's. Next day, I invoke the app, and nothing happens. Checked the process and I see a bunch of them running. Reached out to support and they just pointed me to user forms. Also how come there is no "user Guide". I'm not sure what was happening on the terminal, what does "share from..." even mean etc. 

Next day, I just clicked on the installable again to see if that makes any diff. I did it on both macs and it started working again...till I close any of it, or head home :)

It defeats the whole purpose of using this if I've to keep re-installing it everytime I want to use it. The product seems very promising to me as it definitely meets my need, but its just super frustrating at the moment.

Share this post


Link to post
Share on other sites

I just started using 2.03. Was using version 1 before. I have one Mac 10.12 and one one Win10 1709 x64. The main reason I decided to upgrade was to have the new feature where either of my two system's mouse/keyboard could be used to control both. It's kind of quirky but after a day of using it I think I kind of have it figured out.

Anyway, it does stop working altogether sometimes. But for me it always works again after killing synergy-service on my mac. I restart the service on my win 10 box too sometimes, but it thinks it's just my mac where i need to kill it. 

One time, when using the win 10 mouse/keyboard and crossing over to my mac, the keyboard typed only garbage characters and other weird things were happening. But killing mac synergy-service fixed that too.

Overall it's pretty usable, just annoying sometimes. But I'm hopeful that the developers will fix this stuff over time.

At this point, I'm not ready to go back to version 1 since I really like the two way "server" feature.

Share this post


Link to post
Share on other sites

i've installed successfully on my 2 windows 10 pc's but my mac wont work

i've followed the advice above from Drew2Apps but when i try to start synergy it comes up with "Synergy quit unexpectedly"

Share this post


Link to post
Share on other sites

I have given up. I've returned to the 1.8.8.

It was double wasted money ... The software never worked and I paid the full price when version 2 was released, only to feel robbed a few days later when I saw the black friday price. 

Share this post


Link to post
Share on other sites

This won't help the OPs exact use case, but I wanted to say that Synergy 2 will work with DHCP assigned addresses on both PCs. I do it every day. I have had a problem where the config UI won't show on one computer, but there is a workaround in this forum and even without the workaround I can get the PCs connected. 

Share this post


Link to post
Share on other sites

The procedures listed by Drew3Apps worked for me. The mouse and KB belong to a Windows 10 box and are shared with a MacBook Pro.

I also have a KVM switch between the Windows 10 and a Mac Pro tower. When I switch the KLV from Windows 10 to the Mac Pro, it takes over and all works as expected.

 

Share this post


Link to post
Share on other sites

[ Service ] [2017-12-18T11:44:15] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-12-18T11:44:16] error: websocket handshake error 3: WebSocket Upgrade handshake failed
[ Service ] [2017-12-18T11:44:16] error: websocket handshake response 400: Bad Request
[ Service ] [2017-12-18T11:44:16] debug: clearing last profile snapshot
[ Service ] [2017-12-18T11:44:16] debug: retrying websocket connection in 15s

Opening https://pubsub1.cloud.symless.com on Firefox gives following error:

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

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now