rerickson

Problem connecting to the background service

49 posts in this topic

Just now, Ken Rider said:

And now when I hit Retry the Synergy client went away and came back. It prompted me to "Sign in with Symless" but when I do it says "Couldn't connect to Synergy Cloud. Please check your Internet connection and then try again." That's an obviously wrong error message as I'm typing this reply on the Internet on the same system right now.

And yet another error... I closed the Synergy client, restarted the Synergy service and started the client again. It now is prompting me to sign in but says "Oops! There was a problem. Please try again."

Share this post


Link to post
Share on other sites
2 minutes ago, Ken Rider said:

And yet another error... I closed the Synergy client, restarted the Synergy service and started the client again. It now is prompting me to sign in but says "Oops! There was a problem. Please try again."

Attaching the Synergy logs. 

synergy-router.log

synergy-service.log

synergy.log

Share this post


Link to post
Share on other sites

Hey everyone, this issue is now fixed. Sorry for the downtime. You'll be glad to know that we're starting work on 2.1 now, which will have an offline mode. Also, the online mode will be far less reliant on the cloud. Only the bare minimum (activation and IP address exchange) will go through the cloud servers.

Share this post


Link to post
Share on other sites

Hi,

I am adding to this as well. Once I switch my network connection to a connection outside my company Lan it seems to connect fine to the AWS server it is calling out to. We have currently implemented new changes to our Corp Firewall so, I doubt I will be able to ask for those changes to be reverted. An offline mode would be great :)

Thanks in advance,

Sev

Share this post


Link to post
Share on other sites

Having the same issue... problem connecting to the background service. Was working great for a couple hours -

Share this post


Link to post
Share on other sites
17 hours ago, Nick Bolton said:

Hey everyone, this issue is now fixed. Sorry for the downtime. You'll be glad to know that we're starting work on 2.1 now, which will have an offline mode. Also, the online mode will be far less reliant on the cloud. Only the bare minimum (activation and IP address exchange) will go through the cloud servers.

Fixed? No I'm still having this problem! I'm running Synergy2.0.0-stable on all 3 machines (Mac-Ubuntu-Win7)

Share this post


Link to post
Share on other sites

This is very flaky at the moment, im up and down like a yoyo...

Share this post


Link to post
Share on other sites

This happens with all cloud services releases; it gets flaky.

You can't anticipate what will happen with cloud services. One minute, you could be barely processing any information and another minute, processing so much information you could practically use a dedicated AWS server.

The point is, cloud services are always inconsistent no matter what company you are referring to when they are first released. There needs to be time to refine the resource usage and to mitigate the sudden influx of new cloud users. Once most users are on Synergy 2 and there is no longer a sudden influx of users and a wide inconsistency between usages, Symless can go and refine their server configuration.

Share this post


Link to post
Share on other sites

Sorry, I still have this issue :(

I'm getting 'There was a problem connecting to the background service.'

Excerpt from my log file:

[ Config  ] [2017-11-09T07:28:19] DEBUG: connecting to background service
[ Config  ] [2017-11-09T07:28:19] DEBUG: connected to background service
[ Config  ] [2017-11-09T07:28:19] DEBUG: saying hello to background service
[ Config  ] [2017-11-09T07:28:19] DEBUG: new added screen pos: 257 161
[ Service ] [2017-11-09T07:28:19] debug: saying hello to config ui
[ Service ] [2017-11-09T07:28:19] error: can't send profile snapshot, not yet received from cloud
[ Config  ] [2017-11-09T07:28:20] DEBUG: service cloud connection error
[ Service ] [2017-11-09T07:28:20] debug: got user auth token: *************************************
[ Config  ] [2017-11-09T07:28:20] DEBUG: current version is update to date
[ Service ] [2017-11-09T07:28:23] debug: retrying cloud connection
[ Service ] [2017-11-09T07:28:23] debug: closing existing websocket connection
[ Service ] [2017-11-09T07:28:24] debug: retrying websocket connection now
[ Service ] [2017-11-09T07:28:24] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-09T07:28:24] error: websocket read error 336462100: uninitialized
[ Service ] [2017-11-09T07:28:24] debug: clearing last profile snapshot
[ Config  ] [2017-11-09T07:28:24] DEBUG: service cloud connection error
[ Service ] [2017-11-09T07:28:24] debug: retrying websocket connection in 4s
[ Service ] [2017-11-09T07:28:25] debug: cloud client connected
[ Config  ] [2017-11-09T07:28:25] DEBUG: service cloud connection recovered
[ Service ] [2017-11-09T07:28:25] debug: websocket connected
[ Config  ] [2017-11-09T07:28:29] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:29] error: rpc connection offline
[ Config  ] [2017-11-09T07:28:34] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:34] error: rpc connection offline
[ Config  ] [2017-11-09T07:28:39] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:39] error: rpc connection offline
[ Config  ] [2017-11-09T07:28:44] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:44] error: rpc connection offline
[ Config  ] [2017-11-09T07:28:49] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:49] error: rpc connection offline
[ Config  ] [2017-11-09T07:28:54] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:54] error: rpc connection offline
[ Config  ] [2017-11-09T07:28:59] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:28:59] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:04] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:04] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:09] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:09] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:14] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:14] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:19] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:19] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:24] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:24] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:29] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:29] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:34] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:34] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:39] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:39] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:44] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:44] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:49] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:49] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:54] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:54] error: rpc connection offline
[ Config  ] [2017-11-09T07:29:59] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:29:59] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:04] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:04] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:09] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:09] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:14] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:14] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:19] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:19] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:24] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:24] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:29] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:29] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:34] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:34] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:39] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:39] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:44] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:44] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:49] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:49] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:54] debug: rpc keep alive failed
[ Config  ] [2017-11-09T07:30:54] error: rpc connection offline
[ Config  ] [2017-11-09T07:30:57] DEBUG: restarting app with: C:\Program Files\Synergy\synergy-config.exe 
[ Config  ] [2017-11-09T07:30:57] DEBUG: connecting to background service
[ Config  ] [2017-11-09T07:30:57] DEBUG: connected to background service
[ Config  ] [2017-11-09T07:30:57] DEBUG: saying hello to background service
[ Config  ] [2017-11-09T07:30:58] DEBUG: new added screen pos: 257 161
[ Service ] [2017-11-09T07:30:57] debug: saying hello to config ui
[ Service ] [2017-11-09T07:30:58] error: can't send profile snapshot, not yet received from cloud
[ Config  ] [2017-11-09T07:30:58] DEBUG: service cloud connection error
[ Service ] [2017-11-09T07:30:59] debug: got user auth token: *************************************
[ Config  ] [2017-11-09T07:30:59] DEBUG: current version is update to date
[ Service ] [2017-11-09T07:31:04] debug: retrying cloud connection
[ Service ] [2017-11-09T07:31:04] debug: closing existing websocket connection
[ Service ] [2017-11-09T07:31:04] debug: retrying websocket connection now
[ Service ] [2017-11-09T07:31:04] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-09T07:31:04] error: websocket read error 336462100: uninitialized
[ Service ] [2017-11-09T07:31:04] debug: clearing last profile snapshot
[ Config  ] [2017-11-09T07:31:04] DEBUG: service cloud connection error
[ Service ] [2017-11-09T07:31:04] debug: retrying websocket connection in 1s
[ Service ] [2017-11-09T07:31:05] debug: retrying cloud connection
[ Service ] [2017-11-09T07:31:05] debug: retrying websocket connection now
[ Service ] [2017-11-09T07:31:05] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-09T07:31:05] error: websocket handshake error 336458004: uninitialized
[ Service ] [2017-11-09T07:31:05] debug: clearing last profile snapshot
[ Config  ] [2017-11-09T07:31:05] DEBUG: service cloud connection error
[ Service ] [2017-11-09T07:31:05] debug: retrying websocket connection in 3s
[ Service ] [2017-11-09T07:31:05] debug: tcp session ssl handshake error: unknown protocol
[ Service ] [2017-11-09T07:31:05] error: websocket connect failed
[ Service ] [2017-11-09T07:31:05] debug: clearing last profile snapshot
[ Config  ] [2017-11-09T07:31:05] DEBUG: service cloud connection error
[ Service ] [2017-11-09T07:31:05] debug: retrying websocket connection in 6s
[ Service ] [2017-11-09T07:31:05] debug: retrying cloud connection
[ Service ] [2017-11-09T07:31:05] debug: retrying websocket connection now
[ Service ] [2017-11-09T07:31:05] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Service ] [2017-11-09T07:31:06] debug: cloud client connected
[ Config  ] [2017-11-09T07:31:06] DEBUG: service cloud connection recovered
[ Service ] [2017-11-09T07:31:06] debug: websocket connected

 

 

Share this post


Link to post
Share on other sites

I think everyone is having that issue this morning.

Share this post


Link to post
Share on other sites

They should make sure the software and servers work before calling the release 'stable'

  • Like 1

Share this post


Link to post
Share on other sites
5 minutes ago, stuart macmillan said:

it should be working now.

 

Yes, working for me now :)

Share this post


Link to post
Share on other sites

Pity it didn't work when it was needed.

I'll stay with v1.8 for a while longer now, until it gets all sorted out and don't have to rely on the cloud.

Share this post


Link to post
Share on other sites
On ‎11‎/‎7‎/‎2017 at 10:32 PM, Nick Bolton said:

Hey everyone, this issue is now fixed. Sorry for the downtime. You'll be glad to know that we're starting work on 2.1 now, which will have an offline mode. Also, the online mode will be far less reliant on the cloud. Only the bare minimum (activation and IP address exchange) will go through the cloud servers.

This is by no means fixed. It worked briefly yesterday but now not at all. I have the Synergy client up on two Windows 10 systems. If I use the keyboard or mouse on one system, the Synergy client shows both systems as green. But the Synergy client on the other system shows its box as gray with the scrolling green line. If I do the opposite, i.e. using the mouse or keyboard on the second system, exactly the opposite happens. It's box turns green in the Synergy client but the Synergy client on the other system now shows it's box as gray with the scrolling green line. In neither case is the mouse or keyboard shared between the two.

Share this post


Link to post
Share on other sites
5 minutes ago, Ken Rider said:

This is by no means fixed. It worked briefly yesterday but now not at all. I have the Synergy client up on two Windows 10 systems. If I use the keyboard or mouse on one system, the Synergy client shows both systems as green. But the Synergy client on the other system shows its box as gray with the scrolling green line. If I do the opposite, i.e. using the mouse or keyboard on the second system, exactly the opposite happens. It's box turns green in the Synergy client but the Synergy client on the other system now shows it's box as gray with the scrolling green line. In neither case is the mouse or keyboard shared between the two.

I was able to get it working again. I stopped the Synergy service on both systems, deleted the log files (so I could send them if necessary) and started the services on both systems again. On one system the Synergy client got the "There was a problem connecting to the background service. Retry." When I retried the client restarted and I could now share my keyboard and mouse.

Share this post


Link to post
Share on other sites

I have now problems with the Sign in the app open the web site and saids

synergy-logo.png

Logging you in... Please return to Synergy

But the apps still in Sign in with Symless  Opps! There was a problem. Please try again, this was a fresh installation but look there is something in the background is not working.

Karl

Share this post


Link to post
Share on other sites
8 hours ago, Zathras42 said:

Pity it didn't work when it was needed.

I'll stay with v1.8 for a while longer now, until it gets all sorted out and don't have to rely on the cloud.

I have problems with the v 1.8 stop of works if I can back but there is not any update of version 1 I guess?

Share this post


Link to post
Share on other sites

Nick, can we get an update on this issue. We all love the potential product but it’s useless at the moment. 

Share this post


Link to post
Share on other sites
11 hours ago, Zathras42 said:

Pity it didn't work when it was needed.

I'll stay with v1.8 for a while longer now, until it gets all sorted out and don't have to rely on the cloud.

Ok after an uninstall everything I back to version 1.8 looks is more stable the only this version won't work with High Sierra isn't?

Karl

Share this post


Link to post
Share on other sites

Yes I am having this issue as well.  I am sure many people are but are not coming to the forums.  I don't think this is fixed and seems just no getting any good help.

Share this post


Link to post
Share on other sites

I bought a license today and started using Synergy for the first time. I have been struggling to get this working. The Linux version seems to be working properly (configured as server), but the Mac version, which I want to configure as client, does not seem to be working. First I was getting the messages about cloud connection errors. Now that seems to be resolved, but the configuration is stuck at the following step: "Next step: install Synergy 2 on another computer" This I have already done, but it seems to make no difference. I'm wondering if I'm missing something about the configuration, but also suspect that this is all related to these recent issues.

Screenshot 2017-11-09 16.06.23.png

Edited by DuncanR
  • Like 1

Share this post


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