chrislet

Synergy 2.0.4 not connecting

8 posts in this topic

I am unable to get my two computers to share the mouse and keyboard.

Computers are both on Windows 10 with all updates.

I get two errors.

"There was a problem connecting to the auto-config service. Retry"

and

"There was a problem connecting to the background service. Retry"

Clicking "Retry" does not resolve the issue.

Neither sees the other in the configuration window, only their own name.

https://symless.com/support does not lead anywhere useful.

[ Config  ] [2017-12-28T21:40:05] info: Upload path: https://synergy-logs.symless.com/203c58ca884759d99cbcc95b49a3c0b5/logs/11732-2017-12-28T21-40-03.log

[ Config  ] [2017-12-28T21:43:59] info: Upload path: https://synergy-logs.symless.com/203c58ca884759d99cbcc95b49a3c0b5/logs/11732-2017-12-28T21-43-57.log

Share this post


Link to post
Share on other sites

Have the same problem. For some reason can't successfully submit a ticket with the log file (unless it is successful and the website is not reporting that).

In any case, can't get Synergy 2 at all to work. Downgrading back to 1.8.

Share this post


Link to post
Share on other sites

I've decided to leave Synergy 2, as the features it promises are not worth the pain of reliance on a cloud solution.

Better luck next year Symless.

  • Like 1
  • Confused 1

Share this post


Link to post
Share on other sites

I've been having the same problems as described by Chrislet.
After several attempts the two macs are now connected, but not to each other. changing the configuration in the dialog (moving the screens about) does sync to both devices, but the mouse will not travel across and neither can control the other. Both will also periodically throw up one of the above connection errors again. 
The PC connected in this three way, does not connect at all, and gets stuck with the retry messages.

I tried previously with v2.0.0, and it worked for about 4 hours, but the next day I was unable to get any of them to see/control the other. After checking networks, restarting, reinstalling and pretty much just hammering the connections, I gave up and reinstalled 1.8, which worked. mostly. (mouse lag increases with time, and one of the macs doesnt play along)

So now I've waiting a few months and tried 2.0.4, but it's even less cooperative than 2.0.0 was.

Share this post


Link to post
Share on other sites

I have been trying for awhile to get 2.x working, with "we have a new version available, try now" responses, with no reason why the new version would work or success with the new version. Everything the same as- 

On 12/28/2017 at 8:46 PM, chrislet said:

I am unable to get my two computers to share the mouse and keyboard.

Computers are both on Windows 10 with all updates.

I get two errors.

"There was a problem connecting to the auto-config service. Retry"

and

"There was a problem connecting to the background service. Retry"

Clicking "Retry" does not resolve the issue.

Neither sees the other in the configuration window, only their own name.

https://symless.com/support does not lead anywhere useful.

[ Config  ] [2017-12-28T21:40:05] info: Upload path: https://synergy-logs.symless.com/203c58ca884759d99cbcc95b49a3c0b5/logs/11732-2017-12-28T21-40-03.log

[ Config  ] [2017-12-28T21:43:59] info: Upload path: https://synergy-logs.symless.com/203c58ca884759d99cbcc95b49a3c0b5/logs/11732-2017-12-28T21-43-57.log

 

In addition; when trying to send the new log files for 2.0.4 I have the same results as-

On 1/2/2018 at 8:54 AM, Exivus said:

Have the same problem. For some reason can't successfully submit a ticket with the log file (unless it is successful and the website is not reporting that).

The Submit Request button just doesn't do anything.

 

Is there any solutions to get this working?  I am in a corporate environment, with proxy servers to get out, if that helps.

 

If I simply open Synergy, the "There was a problem connecting to the auto-config service. Retry" error comes up, with the following in the console-

Quote

 

[ Config ] [2018-01-25T14:54:40] debug: install dir: C:\Program Files\Synergy

[ Config ] [2018-01-25T14:54:40] info: log filename: C:\ProgramData\Symless\Synergy\synergy-combined.log

[ Config ] [2018-01-25T14:54:40] warning: version check disabled, skipping

[ Config ] [2018-01-25T14:54:40] debug: connecting to background service

[ Config ] [2018-01-25T14:54:40] debug: connected to background service

[ Config ] [2018-01-25T14:54:40] debug: saying hello to background service

[ Config ] [2018-01-25T14:54:40] debug: new added screen pos: 257 161

[ Service ] [2018-01-25T14:54:40] debug: saying hello to config ui

[ Config ] [2018-01-25T14:54:42] debug: service cloud connection error

[ Service ] [2018-01-25T14:54:40] debug: retrying websocket connection now

[ Service ] [2018-01-25T14:54:40] warning: already connecting websocket

[ Service ] [2018-01-25T14:54:40] debug: connecting websocket: pubsub1.cloud.symless.com:443

[ Service ] [2018-01-25T14:54:40] debug: tcp session ssl handshake error: The network connection was aborted by the local system

[ Service ] [2018-01-25T14:54:40] error: websocket connect failed

[ Service ] [2018-01-25T14:54:40] debug: clearing last profile snapshot

[ Config ] [2018-01-25T14:54:42] debug: service cloud connection error

[ Service ] [2018-01-25T14:54:40] debug: retrying websocket connection in 9s

[ Service ] [2018-01-25T14:54:40] error: can't send profile snapshot, not yet received from cloud

[ Config ] [2018-01-25T14:54:42] debug: service cloud connection error

[ Config ] [2018-01-25T14:54:43] debug: current version is update to date

[ Service ] [2018-01-25T14:54:43] debug: got user auth token: <removed after pasting log>

[ Service ] [2018-01-25T14:54:49] debug: retrying websocket connection now

[ Service ] [2018-01-25T14:54:49] debug: connecting websocket: pubsub1.cloud.symless.com:443

 

If I hit Retry, it stays with the Retrying.... message forever with this in the console-

Quote

 

[ Config ] [2018-01-25T14:58:20] debug: rpc keep alive failed

[ Config ] [2018-01-25T14:58:20] error: rpc connection offline

[ Config ] [2018-01-25T14:58:25] debug: rpc keep alive failed

[ Config ] [2018-01-25T14:58:25] error: rpc connection offline

[ Config ] [2018-01-25T14:58:30] debug: rpc keep alive failed

[ Config ] [2018-01-25T14:58:30] error: rpc connection offline

[ Config ] [2018-01-25T14:58:35] debug: rpc keep alive failed

[ Config ] [2018-01-25T14:58:35] error: rpc connection offline

[ Config ] [2018-01-25T14:58:40] debug: rpc keep alive failed

[ Config ] [2018-01-25T14:58:40] error: rpc connection offline

[ Config ] [2018-01-25T14:58:45] debug: rpc keep alive failed

[ Config ] [2018-01-25T14:58:45] error: rpc connection offline

 

 

Is there a way to configure a Proxy Server or run with IP's instead (not relying on the cloud connection)?

Any help would be appreciated

Share this post


Link to post
Share on other sites

I am facing similar issues and the support site won't allow me to submit a ticket.

Share this post


Link to post
Share on other sites
5 hours ago, compas said:

I am facing similar issues and the support site won't allow me to submit a ticket.

Sorry about that. There's a bug on the support form that we're urgently fixing. Please email us for now: [email protected]

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