JorVe

Couldn't connect to Synergy Cloud

25 posts in this topic

So...

I just went to pirate bay and downloaded a hacked version of Synergy. i Admit...
Before installing i decided that i shouldn't do that, not when actively working with it and bought Synergy not 5 minutes ago.
 

Happy to finally get rid of my two keyboards on my way to small desk i installed and Voila.
It doesn't work because it can't connect to the cloud.
I won't come with the "Wish i had not paid for it", as it seems to be a great software (when it works) i can wait one more day. but i still would love to use that where i paid for because it's a need and not a fun toy.

Anyone here to support me :)
Regards J

Share this post


Link to post
Share on other sites

JorVe, sometime the cloud connection is a little spotty. Don't immediately conclude it's the program or installation. 

What are your OS systems? 

What does your Synergy UI look like? 

Sometimes start/stop the Synergy service boosts it. Sometimes it a system restart seems to get it off the the ground. Then give it a few minutes before you worry. It sometimes takes up to 3 or 4 minutes. 

Once you are all green you are likely to be able just use it and forget it. 

  • Thanks 1

Share this post


Link to post
Share on other sites

Hello KringleKrebs,


It seems i need to be more patient :) as it connected at the moment i wanted to make you a screenshot.

Windows 10 and Mint works perfectly.
 

So all happy i bought it and didn't get any illegal stuff.
Cheers for your quick reply.
I keep a mouse connected to my Linux machine.. I already noticed that this is a must to click on a certain retry button :D once in a while.

so for all readers:
Issue Resolved, and please be patient at first use!!
 

 

Share this post


Link to post
Share on other sites

yeh, had the same issue. cloud isnt as stable as I hoped it was.

they know this, I hope they will fix this in the future.

they are making synergy less cloud dependant but it'l still require initial contact

Share this post


Link to post
Share on other sites
9 hours ago, JorVe said:

I just went to pirate bay and downloaded a hacked version of Synergy. i Admit...

Haha, brilliant.

What's the link?

  • Haha 1

Share this post


Link to post
Share on other sites
On 15/11/2017 at 3:04 AM, Nick Bolton said:

Haha, brilliant.

What's the link?

Hello Nick.
You can find a copy of your software when searching for it on any of the Torrent bays.

Not sure if you want it though :P you might end up with sharing more than just a mouse and keyboard :D 
And i'm sure you don't need an illegal version of your own software.

 

Regards J
 

Share this post


Link to post
Share on other sites

OK. So I've used Synergy in the past. Just bought version 2 and loaded it on a Win7 system and Fedora 26. Getting the same issue on the Fedora system - "Couldn't connect to Synergy Cloud. Please check your internet connection and then try again."

My internet connection is fine. No issues there. 

WTH good is this if I can't use it? I bought the pro version specifically so I could use it with my Fedora system.

So what's the fix? Is there one before I request a refund?

If it helps any, it's 2.0.4-1243.stable.

Edited by Gonzo

Share this post


Link to post
Share on other sites

Hello Gonzo, due to your name, and my Icon i need to reply to you.
We seem to live in the same street.

My system is a WIN 10 Computer and UBUNTU Linux at the moment, and man, it didn't connect same issue as you had.

There is something called "patience" it doesn't come in the installation file, i think it's an addon that you need for the first few minutes.
If you can't find that addon, or you are not compatible with the addon "Patience"..... you might want to have to request a refund.

It took my system a few minutes to connect, and i rebooted booth systems in that time.
Have a Tea, look out of the window and within a few minutes you will be fine,

Regards J

Share this post


Link to post
Share on other sites

and I get this with when I check the status (system name removed):

 

Dec 22 09:11:37 .... synergy-service[3017]: [ Config  ] [2017-12-22T09:11:37] debug: service cloud connection error
Dec 22 09:11:37 .... synergy-service[3017]: [ Service ] [2017-12-22T09:11:37] error: websocket handshake error 3: WebSocket upgr
Dec 22 09:11:37 .... synergy-service[3017]: [ Service ] [2017-12-22T09:11:37] error: websocket handshake response 400: Bad Reque
Dec 22 09:11:37 .... synergy-service[3017]: [ Service ] [2017-12-22T09:11:37] debug: clearing last profile snapshot
Dec 22 09:11:37 .... synergy-service[3017]: [ Service ] [2017-12-22T09:11:37] debug: retrying websocket connection in 20s
Dec 22 09:11:37 .... synergy-service[3017]: [ Config  ] [2017-12-22T09:11:37] debug: service cloud connection error
Dec 22 09:11:37 .... synergy-service[3017]: [ Config  ] [2017-12-22T09:11:37] error: Reply status code: 0
Dec 22 09:11:37 .... synergy-service[3017]: [ Config  ] [2017-12-22T09:11:37] error: failed to check update: reply has error: SS
Dec 22 09:11:37 .... synergy-service[3017]: [ Config  ] [2017-12-22T09:11:37] error: Reply status code: 0
Dec 22 09:11:39 .... synergy-service[3017]: [ Config  ] [2017-12-22T09:11:39] error: Reply status code: 0

Share this post


Link to post
Share on other sites

JorVe, I like your avatar... And yes, your assumption is correct, my name is from the same ilk as Big Bird from many years ago. 

But. here's the thing. I read about being patient with their cloud. I've done that. I've rebooted both systems a few times, restarted the services on both and it still won't connect. How long should I be "patient" then? It shouldn't take upwards of 30 minutes to connect, should it?

Share this post


Link to post
Share on other sites

Hey Gonzo :)
I'm now installing it on a Fedora machine, i downloaded the new stable version.
I'll have a look if i have the same issue.

Back to you in a few

Share this post


Link to post
Share on other sites

Thanks, JorVe!

And FWIW, I'm posting this from this from the Fedora system, so my internet connection would seem to be fine.

Share this post


Link to post
Share on other sites

Are you running Firewalls?, sudo systemctl status firewalld

is this at a home or work environment how's the ports?
sudo firewall-cmd --list-all  (Fedora comes with it installed and running by default)
Maybe you want to stop it, see if it changes anything.

I'm at a home environment, with all ports open at the moment.
And it works for me :(, 

Regards J

Edited by JorVe

Share this post


Link to post
Share on other sites

Both are work systems. I'm at work. And firewallD isn't even running. 

Share this post


Link to post
Share on other sites

so then, should I go back to an earlier version? and if so, how far back? Should I keep version 2 on my windows 7 system? Should I ask for a refund?

Share this post


Link to post
Share on other sites

Hey Gonzo.

I'm sorry that my mental support didn't work.
I can assure you that the cloud is online as i was typing on the wrong machine a second ago wondering why i wasn't writing in this post.

I can only assume that something is blocking you, but that doesn't help you either.
Let's see if Nick or someone else reads this post and knows what it could be.

Chin up, it's your last day at work before X-Mas, have some great food, and some drinks...... 
no wait... A LOT of alcohol and come back to this problem next week somewhere.

Regards And happy holidays !!
 

Share this post


Link to post
Share on other sites

I'll wait. But in the meantime, I'll try a fresh install. Just to see.

And thanks for the help. Hope your holidays are happy too!

Share this post


Link to post
Share on other sites

go check if it works on your home network. if it does then ask your company to help you with getting this to work.

WebSocket-upgrades can fail because of a port that isn't open, this might be the problem here.

 

Share this post


Link to post
Share on other sites

Thanks, but that's not an option. I "could" check it on my home network, but even if it did work, it wouldn't help. I'd still have to have the port(s) opened at work, which won't happen. Plus, I didn't buy it to use at home.

So I go back then to the question, how far back should I go in versions to get it to work? And should I request a refund if it won't work on my work's network? 

Share this post


Link to post
Share on other sites

Hey Gonzo.

I don't think we can answer those questions for you.

If my humble opinion would matter...
Synergy would want you to upgrade if you use a lower version.
Also do you put yourself on a version that has been upgraded due to various reasons and bug-fixes.

Synergy hasn't changed the way it communicates with the CLOUD as far as i know.
Maybe your company has made changes to the infrastructure, for whatever reasons.

If i would use this in my company, i would ask my IT team if there are limitations for using a cloud connected device before buying it, no matter if it worked prior.
And because you said it worked before,and i tell you it is working,
Is requesting a refund OK for a reason that does point to your infrastructure is the question?.

I think that users like me, Moderators like Jaap, cannot help you with this :)
See if you can poke Nick, (don't use a pointy stick) and see if he can tell you.

Regards J.

Share this post


Link to post
Share on other sites

checking at home tells us if this really is the problem, right now all we know is that it doesn't work.

if you test it at home and change permissions in the windows firewall to see if you can replicate the issue we know what the problem exactly is.

Share this post


Link to post
Share on other sites

on fedora 27 synergy version "synergy-2.0.5-1379.stable.3f23b557.el7.centos.x86_64.rpm" i get Couldn't connect to Synergy Cloud.

Noting wrong with my internet.

Share this post


Link to post
Share on other sites

Itiot,

First, try restarting Synergy, maybe more than once.

From terminal:

  sudo systemctl restart synergy

If no joy, then try a reboot. 

Edited by GranPaSmurf

Share this post


Link to post
Share on other sites

restart, remove old config and reinstall, reboot the laptop, try to chance the config file with my costumer id noting works.

systemctl status synergy.service
● synergy.service - Synergy Service
   Loaded: loaded (/usr/lib/systemd/system/synergy.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2018-02-11 14:44:08 CET; 2h 16min ago
 Main PID: 3296 (synergy-service)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/synergy.service
           └─3296 /usr/bin/synergy-service

Feb 11 16:53:55 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:55] error: Reply status code: 0
Feb 11 16:53:56 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
Feb 11 16:53:56 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
Feb 11 16:53:56 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
Feb 11 16:53:56 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
Feb 11 16:53:57 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:57] error: Reply status code: 0
Feb 11 16:53:57 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:57] error: Reply status code: 0
Feb 11 16:53:58 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:58] error: Reply status code: 0
Feb 11 16:53:58 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:58] error: Reply status code: 0
Feb 11 16:53:59 thortop.netbulae.eu synergy-service[3296]: [ Config  ] [2018-02-11T16:53:59] error: Reply status code: 0

 

cat /var/log/synergy/synergy-combined.log
[ Service ] [2018-02-11T12:00:40] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2018-02-11T12:00:40] debug: install dir: /usr/bin
[ Service ] [2018-02-11T12:00:40] info: starting service...
[ Router  ] [2018-02-11T12:00:40] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-02-11T12:00:40] debug: Initialized
[ Service ] [2018-02-11T12:00:40] warning: core uid is not set in config file
[ Service ] [2018-02-11T12:00:40] info: Session monitor started
[ Service ] [2018-02-11T12:00:40] info: Active X session changed from "--" to "2"
[ Service ] [2018-02-11T12:00:40] info: Active X user changed from "--" to "1000"
[ Service ] [2018-02-11T12:00:40] info: Active X display changed from "--" to ":0"
[ Service ] [2018-02-11T12:00:40] debug: creating rpc endpoints
[ Service ] [2018-02-11T12:00:40] debug: rpc endpoints created
[ Service ] [2018-02-11T12:00:55] info: Session monitor stopped
[ Service ] [2018-02-11T12:00:55] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T12:00:55] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T12:00:55] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T12:01:56] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2018-02-11T12:01:56] debug: install dir: /usr/bin
[ Service ] [2018-02-11T12:01:56] info: starting service...
[ Router  ] [2018-02-11T12:01:56] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-02-11T12:01:56] debug: Initialized
[ Service ] [2018-02-11T12:01:56] warning: core uid is not set in config file
[ Service ] [2018-02-11T12:01:56] info: Session monitor started
[ Service ] [2018-02-11T12:01:56] debug: creating rpc endpoints
[ Service ] [2018-02-11T12:01:56] debug: rpc endpoints created
[ Service ] [2018-02-11T12:02:08] warning: Active X "greeter" session "c1" ignored
[ Service ] [2018-02-11T12:02:08] warning: Active X "greeter" session "c1" ignored
[ Service ] [2018-02-11T12:02:08] warning: Active X "greeter" session "c1" ignored
[ Service ] [2018-02-11T12:02:28] warning: Active X "greeter" session "c1" ignored
[ Service ] [2018-02-11T12:02:28] warning: Active X "greeter" session "c1" ignored
[ Service ] [2018-02-11T12:02:28] warning: Active X "greeter" session "c1" ignored
[ Service ] [2018-02-11T12:02:29] info: Active X session changed from "--" to "2"
[ Service ] [2018-02-11T12:02:29] info: Active X user changed from "--" to "1000"
[ Service ] [2018-02-11T12:02:29] info: Active X display changed from "--" to ":0"
[ Service ] [2018-02-11T12:04:16] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T12:04:16] debug: saying hello to config ui
[ Config  ] [2018-02-11T12:04:18] warning: version check disabled, skipping
[ Config  ] [2018-02-11T12:04:19] error: Reply status code: 0
[ Config  ] [2018-02-11T12:04:19] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T12:04:19] error: Reply status code: 0
[ Config  ] [2018-02-11T12:04:21] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:38] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:38] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:39] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:39] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:39] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:39] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:39] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:39] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:40] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:40] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:40] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:40] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:40] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:41] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:41] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:41] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:41] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:41] error: Reply status code: 0
[ Config  ] [2018-02-11T12:06:42] error: Reply status code: 0
[ Service ] [2018-02-11T12:12:30] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T12:12:30] debug: saying hello to config ui
[ Config  ] [2018-02-11T12:12:30] warning: version check disabled, skipping
[ Config  ] [2018-02-11T12:12:30] error: Reply status code: 0
[ Config  ] [2018-02-11T12:12:30] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T12:12:30] error: Reply status code: 0
[ Config  ] [2018-02-11T12:12:30] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T12:12:30] error: Reply status code: 0
[ Config  ] [2018-02-11T12:12:32] error: Reply status code: 0
[ Config  ] [2018-02-11T12:13:40] error: Reply status code: 0
[ Config  ] [2018-02-11T12:13:41] error: Reply status code: 0
[ Service ] [2018-02-11T12:14:14] info: Session monitor stopped
[ Service ] [2018-02-11T12:14:14] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T12:14:14] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T12:14:14] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T12:14:14] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2018-02-11T12:14:14] debug: install dir: /usr/bin
[ Service ] [2018-02-11T12:14:14] info: starting service...
[ Router  ] [2018-02-11T12:14:14] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-02-11T12:14:14] debug: Initialized
[ Service ] [2018-02-11T12:14:14] debug: setting core uid from config: 1000
[ Service ] [2018-02-11T12:14:14] info: Session monitor started
[ Service ] [2018-02-11T12:14:14] info: Active X session changed from "--" to "2"
[ Service ] [2018-02-11T12:14:14] info: Active X user changed from "--" to "1000"
[ Service ] [2018-02-11T12:14:14] info: Active X display changed from "--" to ":0"
[ Service ] [2018-02-11T12:14:14] debug: creating rpc endpoints
[ Service ] [2018-02-11T12:14:14] debug: rpc endpoints created
[ Service ] [2018-02-11T12:14:22] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T12:14:22] debug: saying hello to config ui
[ Config  ] [2018-02-11T12:14:22] warning: version check disabled, skipping
[ Config  ] [2018-02-11T12:14:22] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:22] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T12:14:22] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:24] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:25] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:25] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:25] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:26] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:26] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:26] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:26] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:26] error: Reply status code: 0
[ Config  ] [2018-02-11T12:14:26] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:36] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:36] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:36] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:36] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:37] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:50] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:50] error: Reply status code: 0
[ Config  ] [2018-02-11T12:16:50] error: Reply status code: 0
[ Config  ] [2018-02-11T13:00:51] error: Reply status code: 0
[ Config  ] [2018-02-11T13:00:51] error: Reply status code: 0
[ Config  ] [2018-02-11T13:00:51] error: Reply status code: 0
[ Config  ] [2018-02-11T13:00:52] error: Reply status code: 0
[ Service ] [2018-02-11T13:06:09] info: Session monitor stopped
[ Service ] [2018-02-11T13:06:09] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T13:06:09] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T13:06:09] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-02-11T13:06:09] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2018-02-11T13:06:09] debug: install dir: /usr/bin
[ Service ] [2018-02-11T13:06:09] info: starting service...
[ Router  ] [2018-02-11T13:06:09] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-02-11T13:06:09] debug: Initialized
[ Service ] [2018-02-11T13:06:09] debug: setting core uid from config: 1000
[ Service ] [2018-02-11T13:06:09] info: Session monitor started
[ Service ] [2018-02-11T13:06:09] info: Active X session changed from "--" to "2"
[ Service ] [2018-02-11T13:06:09] info: Active X user changed from "--" to "1000"
[ Service ] [2018-02-11T13:06:09] info: Active X display changed from "--" to ":0"
[ Service ] [2018-02-11T13:06:09] debug: creating rpc endpoints
[ Service ] [2018-02-11T13:06:09] debug: rpc endpoints created
[ Service ] [2018-02-11T13:06:17] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T13:06:17] debug: saying hello to config ui
[ Config  ] [2018-02-11T13:06:17] warning: version check disabled, skipping
[ Config  ] [2018-02-11T13:06:17] error: Reply status code: 0
[ Config  ] [2018-02-11T13:06:17] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T13:06:17] error: Reply status code: 0
[ Config  ] [2018-02-11T13:06:20] error: Reply status code: 0
[ Service ] [2018-02-11T13:07:43] debug: setting core uid from rpc: 0
[ Service ] [2018-02-11T13:07:43] debug: saying hello to config ui
[ Config  ] [2018-02-11T13:07:43] warning: version check disabled, skipping
[ Config  ] [2018-02-11T13:07:43] error: Reply status code: 0
[ Config  ] [2018-02-11T13:07:43] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T13:07:43] error: Reply status code: 0
[ Config  ] [2018-02-11T13:07:46] error: Reply status code: 0
[ Config  ] [2018-02-11T13:07:58] error: Reply status code: 0
[ Config  ] [2018-02-11T13:07:58] error: Reply status code: 0
[ Config  ] [2018-02-11T13:07:58] error: Reply status code: 0
[ Config  ] [2018-02-11T13:07:58] error: Reply status code: 0
[ Service ] [2018-02-11T13:08:24] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T13:08:24] debug: saying hello to config ui
[ Config  ] [2018-02-11T13:08:24] warning: version check disabled, skipping
[ Config  ] [2018-02-11T13:08:24] error: Reply status code: 0
[ Config  ] [2018-02-11T13:08:24] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T13:08:24] error: Reply status code: 0
[ Config  ] [2018-02-11T13:08:26] error: Reply status code: 0
[ Service ] [2018-02-11T13:09:27] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T13:09:27] debug: saying hello to config ui
[ Config  ] [2018-02-11T13:09:27] warning: version check disabled, skipping
[ Config  ] [2018-02-11T13:09:27] error: Reply status code: 0
[ Config  ] [2018-02-11T13:09:27] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T13:09:27] error: Reply status code: 0
[ Config  ] [2018-02-11T13:09:30] error: Reply status code: 0
[ Service ] [2018-02-11T13:22:55] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T13:22:55] debug: saying hello to config ui
[ Config  ] [2018-02-11T13:22:55] warning: version check disabled, skipping
[ Service ] [2018-02-11T13:32:22] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T13:32:22] debug: saying hello to config ui
[ Config  ] [2018-02-11T13:32:22] warning: version check disabled, skipping
[ Config  ] [2018-02-11T13:32:22] error: Reply status code: 0
[ Config  ] [2018-02-11T13:32:22] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T13:32:22] error: Reply status code: 0
[ Config  ] [2018-02-11T13:32:24] error: Reply status code: 0
[ Service ] [2018-02-11T13:34:06] info: Session monitor stopped
[ Service ] [2018-02-11T14:44:08] debug: service log path: /var/log/synergy/synergy-service.log
[ Service ] [2018-02-11T14:44:08] debug: install dir: /usr/bin
[ Service ] [2018-02-11T14:44:08] info: starting service...
[ Router  ] [2018-02-11T14:44:08] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-02-11T14:44:08] debug: Initialized
[ Service ] [2018-02-11T14:44:08] debug: setting core uid from config: 1000
[ Service ] [2018-02-11T14:44:08] info: Session monitor started
[ Service ] [2018-02-11T14:44:08] info: Active X session changed from "--" to "2"
[ Service ] [2018-02-11T14:44:08] info: Active X user changed from "--" to "1000"
[ Service ] [2018-02-11T14:44:08] info: Active X display changed from "--" to ":0"
[ Service ] [2018-02-11T14:44:08] debug: creating rpc endpoints
[ Service ] [2018-02-11T14:44:08] debug: rpc endpoints created
[ Service ] [2018-02-11T14:44:16] debug: setting core uid from rpc: 1000
[ Service ] [2018-02-11T14:44:16] debug: saying hello to config ui
[ Config  ] [2018-02-11T14:44:17] warning: version check disabled, skipping
[ Config  ] [2018-02-11T14:44:18] error: Reply status code: 0
[ Config  ] [2018-02-11T14:44:18] error: failed to check update: reply has error: SSL handshake failed
[ Config  ] [2018-02-11T14:44:18] error: Reply status code: 0
[ Config  ] [2018-02-11T14:44:20] error: Reply status code: 0
[ Config  ] [2018-02-11T14:44:22] error: Reply status code: 0
[ Config  ] [2018-02-11T14:44:22] error: Reply status code: 0
[ Config  ] [2018-02-11T14:44:22] error: Reply status code: 0
[ Config  ] [2018-02-11T14:44:22] error: Reply status code: 0
[ Config  ] [2018-02-11T16:52:18] error: Reply status code: 0
[ Config  ] [2018-02-11T16:52:18] error: Reply status code: 0
[ Config  ] [2018-02-11T16:52:18] error: Reply status code: 0
[ Config  ] [2018-02-11T16:52:19] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:55] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:56] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:57] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:57] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:58] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:58] error: Reply status code: 0
[ Config  ] [2018-02-11T16:53:59] error: Reply status code: 0

 

Share this post


Link to post
Share on other sites

Looks like good troubleshooting. Let's see what others say.

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