Ilya

[RC2] Experiences, Troubleshooting, Tips/Tricks, Discussion

33 posts in this topic

Anyone else have a completely bricked product now that the RC's have rolled out? I missed RC1 but upgraded to RC2 from Beta5 (was forced) and I'm dead in the water. Machines don't even see each other (same network) and my desktop usually can't connect to the 'background service'. I'm VERY annoyed. I was very patient with the beta's and we made good progress as most of my issues were resolved with each one but we just went back to the stone age with the RC's. UGH. And for them to close the EAB forum is STUPID. I emailed them, posting here. Not expecting much help from them to be honest.

Might need to claim a refund and go back to using 1.8.8 for good. I can't even go back to Beta5 as it won't connect to the service.

This is hot garbage and is extremely rushed. EXTREMELY.

Share this post


Link to post
Share on other sites

I think you'll get help on this forum quicker than on the Early Access.

Let's pre-suppose that not everyone is having your same experience, so stick around a bit and see what happens. Taking the refund at this point will take you out of the goodies you've already qualified for.

I'm running RC2 very successfully. One Win10, 1 Win7(32 bit) and Kubuntu 17.04. It's so smooth and responsive that I'm beginning to wonder if version 1 added a little lag I hadn't noticed.

First, restart all your machines. Then wait a few minutes for the cloud connection to settle. See what happens. Let us know

Edited by KringleKrebs

Share this post


Link to post
Share on other sites
11 minutes ago, KringleKrebs said:

I think you'll get help on this forum quicker than on the Early Access.

Let's pre-suppose that not everyone is having your same experience, so stick around a bit and see what happens. Taking the refund at this point will take you out of the goodies you've already qualified for.

I'm running RC2 very successfully. One Win10, 1 Win7(32 bit) and Kubuntu 17.04. It's so smooth and responsive that I'm beginning to wonder if version 1 added a little lag I hadn't noticed.

First, restart all your machines. Then wait a few minutes for the cloud connection to settle. See what happens. Let us know

I ended up writing myself a batch script to uninstall properly (evidently you need to remove registry keys, etc. which was not previously mentioned in the EAB forum).

Here is the script below:

:: Following guide is the basis of this script
:: https://symless.com/forums/topic/4519-synergy-2-how-to-uninstall-and-reinstall/

:: Removing Synergy

WMIC product where name="Synergy (64-bit)" CALL uninstall

:: Removing registry items

REG delete HKEY_CURRENT_USER\Software\Symless /f
REG delete HKEY_CURRENT_USER\Software\Synergy /f

:: Deleting directories

RMDIR "C:\ProgramData\Symless" /s /q
RMDIR "C:\ProgramData\Synergy v2" /s /q
RMDIR "%USERPROFILE%\AppData\Local\Symless" /s /q
RMDIR "%USERPROFILE%\AppData\Local\Synergy" /s /q

After doing that:

  1. Restarted both machines
  2. After logging back in, gave machines a little time and then launched Synergy
  3. Was prompted to login to Symless cloud or whatever...thought that for sure it'd work now because I was seeing something new. NADA.
  4. "There was a problem connecting to the auto-config service. Retry..." on both machines appears and does NOTHING when you retry.

 

 

Share this post


Link to post
Share on other sites
3 minutes ago, Ilya said:

4. "There was a problem connecting to the auto-config service. Retry..." on both machines appears and does NOTHING when you retry.

I closed Synergy, restarted the services, and re-opened. Both displayed above message again, but after retrying my main desktop looks to be 'running' but not quite (box is gray). My work laptop, however, briefly didn't display that message and then changed to "There was a problem connecting to the background service. Retry..."

What the hell happened to this thing? Is the background service the 'cloud' service? Is there any way to disable the cloud service? I have no need or desire to use 'cloud' for anything on a product like this.

Share this post


Link to post
Share on other sites

I'm seeing the same problems on a Windows & Mac setup with RC2. Typically when I open Synergy, it just says "There was a problem connecting to the auto-config service. Retry"

After a long series of restarting the services/computers/synergy client, I could get each computer to connect to the service successfully. Neither computer could see each other though. Each computer only showed their own screen, and even those were greyed out.

Beta 5 had been working pretty well for me previously.

  • Sad 1

Share this post


Link to post
Share on other sites

My desktop PC looks to be staying 'up' (but again, gray screen and can't see the other machine). My laptop however, which I can't mess with the firewall on because it's a work issued machine with it's own group policy, etc. is havin none of it.

Here is the log from my laptop:

[ Config  ] [2017-11-07T10:08:25] DEBUG: install dir: C:\Program Files\Synergy
[ Config  ] [2017-11-07T10:08:25] INFO: log filename: C:/Users/User/AppData/Local/Symless/Synergy/synergy.log
[ Config  ] [2017-11-07T10:08:25] DEBUG: connecting to background service
[ Config  ] [2017-11-07T10:08:25] DEBUG: connected to background service
[ Config  ] [2017-11-07T10:08:25] DEBUG: saying hello to background service
[ Config  ] [2017-11-07T10:08:25] DEBUG: new added screen pos: 257 161
[ Service ] [2017-11-07T10:08:25] debug: saying hello to config ui
[ Service ] [2017-11-07T10:08:25] error: can't send profile snapshot, not yet received from cloud
[ Config  ] [2017-11-07T10:08:25] DEBUG: service cloud connection error
[ Config  ] [2017-11-07T10:08:30] DEBUG: current version is update to date
[ Config  ] [2017-11-07T10:08:35] error: rpc function call failed: synergy.cloud.retry
[ Config  ] [2017-11-07T10:08:35] error: rpc connection offline
[ Service ] [2017-11-07T10:08:30] debug: retrying cloud connection
[ Service ] [2017-11-07T10:08:30] debug: closing existing websocket connection
[ Service ] [2017-11-07T10:08:35] debug: retrying websocket connection now
[ Service ] [2017-11-07T10:08:35] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-07T10:08:35] error: websocket read error 336462100: uninitialized
[ Service ] [2017-11-07T10:08:35] debug: clearing last profile snapshot
[ Config  ] [2017-11-07T10:08:35] DEBUG: service cloud connection error
[ Service ] [2017-11-07T10:08:35] debug: retrying websocket connection in 9s
[ Service ] [2017-11-07T10:08:35] debug: got user auth token: <redacted>
[ Service ] [2017-11-07T10:08:39] debug: cloud client connected
[ Config  ] [2017-11-07T10:08:39] DEBUG: service cloud connection recovered
[ Service ] [2017-11-07T10:08:39] debug: websocket connected
[ Config  ] [2017-11-07T10:08:50] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:08:50] error: rpc connection offline
[ Config  ] [2017-11-07T10:08:55] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:08:55] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:00] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:00] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:05] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:05] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:10] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:10] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:15] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:15] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:20] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:20] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:25] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:25] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:30] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:30] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:35] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:35] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:40] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:40] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:45] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:45] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:50] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:50] error: rpc connection offline
[ Config  ] [2017-11-07T10:09:55] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:09:55] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:00] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:00] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:05] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:05] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:10] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:10] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:15] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:15] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:20] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:20] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:25] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:25] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:30] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:30] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:35] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:35] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:40] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:40] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:45] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:45] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:50] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:50] error: rpc connection offline
[ Config  ] [2017-11-07T10:10:55] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:10:55] error: rpc connection offline
[ Config  ] [2017-11-07T10:11:00] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:11:00] error: rpc connection offline
[ Config  ] [2017-11-07T10:11:05] debug: rpc keep alive failed
[ Config  ] [2017-11-07T10:11:05] error: rpc connection offline
....and on and on and on with the RPC connection issue

 

Share this post


Link to post
Share on other sites
42 minutes ago, KringleKrebs said:

First, restart all your machines. Then wait a few minutes for the cloud connection to settle. See what happens. Let us know

Golden. I like most of you have been frustrated with this since B2. Once you finally get everything working correctly, you come in to work the next day and get a forced upgrade only to have to start the whole infuriating process over again. Now RC2 same thing...

Do a clean uninstall and removal of orphaned files, restart, reinstall, restart. WAIT A WHILE (10-15 minutes) before you start synergy. Either the background process is hella slow to load or the cloud takes a while to negotiate the connection. Don't know, don't care. I'm one of those simpletons that just wants my keyboard/mouse to control 1 mac and 1 pc without fail the way that Synergy one has for years. I'm finally back to a working RC2 now, we'll see what happens tomorrow. 

 

  • Thanks 1

Share this post


Link to post
Share on other sites

I'm experiencing the same issues. I had similar issues with a couple of the beta releases.
I've fully removed the client on multiple computers and reinstalled, but none of them can even login.
Obviously, I have internet access.

While I realize that this is a beta, it is increasingly irritating to find my workflow crippled by broken synergy updates...

Edited by squidflex

Share this post


Link to post
Share on other sites
9 minutes ago, Swervedriver said:

Golden. I like most of you have been frustrated with this since B2. Once you finally get everything working correctly, you come in to work the next day and get a forced upgrade only to have to start the whole infuriating process over again. Now RC2 same thing...

Do a clean uninstall and removal of orphaned files, restart, reinstall, restart. WAIT A WHILE (10-15 minutes) before you start synergy. Either the background process is hella slow to load or the cloud takes a while to negotiate the connection. Don't know, don't care. I'm one of those simpletons that just wants my keyboard/mouse to control 1 mac and 1 pc without fail the way that Synergy one has for years. I'm finally back to a working RC2 now, we'll see what happens tomorrow. 

 

Holy crap. I closed both windows like 20-25 minutes ago and just relaunched and although my desktop PC is telling me to 'Sign in with Symless', my machines connected. On my laptop, Synergy shows the laptop as 'scanning' (grey with green bar going across) and desktop as green.

I'll take it. Tomorrow I'll be sure to leave them be for a good half-hour before attempting anything.

Edited by Ilya

Share this post


Link to post
Share on other sites

im having the same issue, the cloud is down. This is really anoying, check back in a couple of hours(I dont know how long it will last) and tell us if anything changed

Share this post


Link to post
Share on other sites
46 minutes ago, Ilya said:

...

What the hell happened to this thing? Is the background service the 'cloud' service? Is there any way to disable the cloud service? I have no need or desire to use 'cloud' for anything on a product like this.

 

Ilya, It's my understanding, at least with previous betas, that the cloud connection only matches the credentials of the machines so they can securely connect. Then it's not connected again until you restart Synergy, as in morning start-up. Then the cloud connection compares the credentials profile and if there is no change, backs out. Maybe RC2 stays connected...

As to not using the cloud connection: there has been some discussion on the forum about cable connections to do the same thing. My guess is you won't see this addressed until Synergy 2 is fully functional and has been on the market for a while. So after all is working wonderfully for a while, the devs might get bored enough to think about a cable connection. As for right now, enjoy the feature of the cloud connection making an auto-configuration.

Share this post


Link to post
Share on other sites

I was using RC1 yesterday fine until about 4:15ish (eastern). Forced to switch to RC2. Seemed good until I left.  Came in this morning, booted up Win 10 laptop and click on "sign in with Symless".. browser opens and says "logging you in .. please return to synergy". Synergy says "couldn't connect to synergy cloud. please check your internet connection and then try again".

Can't "~" to load the log file... 

Occurs on both computers (Win 10 and Mac OS X Sierra).

My network connection is fine.  Sent email at 8:58 am to [email protected] no response... 

Share this post


Link to post
Share on other sites
4 minutes ago, Cheryl Lomedico said:

I was using RC1 yesterday fine until about 4:15ish (eastern). Forced to switch to RC2. Seemed good until I left.  Came in this morning, booted up Win 10 laptop and click on "sign in with Symless".. browser opens and says "logging you in .. please return to synergy". Synergy says "couldn't connect to synergy cloud. please check your internet connection and then try again".

Can't "~" to load the log file... 

Occurs on both computers (Win 10 and Mac OS X Sierra).

My network connection is fine.  Sent email at 8:58 am to [email protected] no response... 

Yeah I've gotten no response to my email either. I can't imagine there is a million users of Synergy. It's more than likely a small community, so not getting even a slight response with some basic troubleshooting is no bueno. Luckily, Swerve's suggestion above seemed to do it for me.

I've been working in IT for 15 years and very few pieces of software have frustrated me as much as Synergy has over the last few weeks.

EDIT: Just as I posted that, I got an email response to my earlier ticket submission...telling me to try Synergy 2.0 (RC2). LOL. I AM ALREADY ON 2.0!

Got to be kidding me. Did they even read my ticket?

Edited by Ilya

Share this post


Link to post
Share on other sites

Just downloaded and tried my Synergy 2 today.  I upgraded my subscription a month ago.  Same problem as everyone else.  One computer just gets the gray box with green scrolling progress bar.  What a disappointment. 

Share this post


Link to post
Share on other sites

I have found the newer versions, except for the logon into the API, to be not bad.  There are some glitches but as mentioned 1) log into the Symless cloud is not desired and 2) communication and forced updates to the next RC - that are not desired.

Share this post


Link to post
Share on other sites
Just now, Cheryl Lomedico said:

I have found the newer versions, except for the logon into the API, to be not bad.  There are some glitches but as mentioned 1) log into the Symless cloud is not desired and 2) communication and forced updates to the next RC - that are not desired.

Honestly, I'd be very content using Beta5 for months and months. Thing was pretty dang solid for me. Other than occasionally having to restart the service, but I wrote myself a quick batch script and it took me one click and 2 seconds of waiting.

Share this post


Link to post
Share on other sites
2 minutes ago, Brian Davis said:

They just released a new version a few minutes ago...

Testing. Wish me luck! lol

Share this post


Link to post
Share on other sites
1 minute ago, Swervedriver said:

Just updated. That was more like a RC. Up and running within literally a minute. 

I can confirm the same.

I did a clean uninstall using my script above, rebooted, installed 2.0 stable. Signed into Symless, told me to retry the background service, and voila...in like flynn. In seconds.

Share this post


Link to post
Share on other sites

Same here but .....

on my mac, I went to move the app to desktop 4 (F3 then move to desktop 4), the connection actually disconnects and cursor goes to my windows session. Also when I try to move the cursor from Windows to Mac, I have to move my mouse several times (6-8x) to get the cursor over..

Try to get the log file link but it won't show...

Not thrilled.. seems it went backwards...

Tried transition again - smooth movements...

Edited by Cheryl Lomedico

Share this post


Link to post
Share on other sites

on my mac, I went to move the app to desktop 4 (F3 then move to desktop 4), the connection actually disconnects and cursor goes to my windows session. Also when I try to move the cursor from Windows to Mac, I have to move my mouse several times (6-8x) to get the cursor over..

-> figured out a work around...

Share this post


Link to post
Share on other sites

The new release Synergy_v2.0.0-stable_b1232-060bdcb0-x64 fixed my problems!  Thanks!

Shouldn't I see a menu of some sort?  All I see on all 3 screens is the monitor config panel and nothing else.  No buttons, no menus, no anything.  It seems there should be config options somewhere?

Share this post


Link to post
Share on other sites
9 minutes ago, asguardian said:

The new release Synergy_v2.0.0-stable_b1232-060bdcb0-x64 fixed my problems!  Thanks!

Shouldn't I see a menu of some sort?  All I see on all 3 screens is the monitor config panel and nothing else.  No buttons, no menus, no anything.  It seems there should be config options somewhere?

Nope, its very basic right now. Literally no configuration on windows as far as I am aware other than hand editing config files. 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.