Problem connecting to the auto-config service

[Kevin Farley]

None of my machines have been able to stay connected this morning, between logging me out and requiring me to log back in again but giving me the message "Oops! There was a problem" but no further actions available, or telling me the Cloud Service was unreachable, or the often seen "There was a problem connecting to the auto-config service. Retry" which does nothing.  Where do we go for network status updates so we don't need to waste time posting here or contacting support?

[Nick Bolton]

There was some brief downtime while we upgraded a server over Thanksgiving, which was resolved yesterday.

[Kevin Farley]

Thanks Nick.  Now that it seems Synergy is so closely reliant on the cloud services, downtime on your server seems like downtime for all of us, is there any plan for a zero downtime maintenance path, or at the very least choosing a time to upgrade your servers that isn't during prime usage periods?  I'm in Eastern Standard Time and it seems this affected me all morning long.  I realize as a global service, my prime time is potentially others down time, but there's got to be a better way, I rely on this for much of my day to day and it caused a lot of pain yesterday.  Appreciate you and your teams efforts, as a full stack engineer myself, I totally get the difficulty in pleasing everyone!

[Nick Bolton]

Don't worry, we're doing 4 things:

• Adding redundancy to our cloud infrastructure (we'll shoot for 99.99% uptime; 1h a year)
• Moving all non-essential things away from the cloud (auto-switching, config updates, etc)
• Make it still completely usable if the cloud goes offline (apart from the initial setup for when in online mode)
• Adding a full offline mode for people who can't use the internet (e.g. oil rigs, military bases, etc)

[Wei Jin]

Have the auto-config service resumed? My machines are still unable to connect to the auto-config service.

[JustDave]

I am having the same problem with my "client" machine. I had to restart both services, but the client will not re-connect.

[AnyFlow]

I just upgrade to synergy 2 today, and "There was a problem connecting to the auto-config service. Retrying..." on both my windows and mac. So sad.

[wuchichou]

I just downloaded synergy 2 and cannot connect to the auto-config service either.

[LiQing]

I guess, in China, the site 'https://pubsub1.cloud.symless.com/' has been blocked by A Firewall, you know.

I hope Synergy Team can resolve this problem for China users. If not, add a proxy feature??

 

[GaryZheng]

1 hour ago, LiQing said:

I guess, in China, the site 'https://pubsub1.cloud.symless.com/' has been blocked by A Firewall, you know.

I hope Synergy Team can resolve this problem for China users. If not, add a proxy feature??

 

Hi LiQing, where did you get the url "https://pubsub1.cloud.symless.com/'", I can only find "v1.api.cloud.symless.com" in capture tools. And by the way, even if add a proxy, still can't connect to auto-config service.

[LiQing]

4 minutes ago, GaryZheng said:

Hi LiQing, where did you get the url "https://pubsub1.cloud.symless.com/'", I can only find "v1.api.cloud.symless.com" in capture tools. And by the way, even if add a proxy, still can't connect to auto-config service.

You can find the url in log. Synergy maybe use global proxy, I can't find a way to set a global proxy on computer for Synergy. And I set the proxy in the router.

[GaryZheng]

2 hours ago, LiQing said:

You can find the url in log. Synergy maybe use global proxy, I can't find a way to set a global proxy on computer for Synergy. And I set the proxy in the router.

After some tests, I found synergy-service was not obey the system proxy settings, that’s why I can’t find it in capture tools. There is a software called profixer, you can config *.symless.com go through a proxy to walk around this instead of setting proxy in your router. But I think this is still a issue to us. Better way to solve this is adding proxy config right in the app or Synergy team can set more servers. 

[Wei Jin]

11 minutes ago, GaryZheng said:

After some tests, I found synergy-service was not obey the system proxy settings, that’s why I can’t find it in capture tools. There is a software called profixer, you can config *.symless.com go through a proxy to walk around this instead of setting proxy in your router. But I think this is still a issue to us. Better way to solve this is adding proxy config right in the app or Synergy team can set more servers. 

synergy still can not connect to pubsub1.cloud.symless.com:443 even though I setup a VPN. But pinged pubsub1.cloud.symless.com with OK responses.

[Wei Jin]

Is 45.55.221.2 the correct IP of domain pubsub1.cloud.symless.com? I opened this url <https://pubsub1.cloud.symless.com> in safari and got a page prompts Welcome to nginx!

[VVE1505]

I've been using Synergy for longer than I can remember and have loved it. Version 2 has me concerned. I like a clean interface, but there is NOTHING. No help, no anything. I tried v2 beta 4 and had to uninstall because it would not connect between my Windows 10 and Linux desktops. That was about a month ago. This weekend I upgraded to v2 and still there is a failure to connect to the auto-config service.

Even worse, there doesn't seem to be any resolution to all these threads I'm seeing in the forum. I did a wireshark capture and it looks like a session is established between my host and the 45.55.221.2 server and then just when data is being transfered back and forth, the server ends the connection. I'm going back to v. 1.8 and not trying 2 again until I see some positive comments in these forums.

[J. Young]

I'm also having this issue. I just noticed that 2.0.2 was released as a stable build and decided to come back to it after not having any luck with it in beta. I was hoping for a seamless Symless experience, but all I got was "There was a problem connecting to the auto-config service". I have tried on both a Windows 10 and OSX machine with the same results. Back to Synergy 1 until this gets resolved.

[J. Young]

From the other topic that shares this name, it was recommended to do a complete uninstall of Synergy and reinstall. I followed the documented procedure. This allowed my Windows machine to get past this error, but my OSX machine did not. Since I do not have another machine for testing, I couldn't verify if the software was in a working state or not.

[chuckb]

Similar problems here. Synergy 2 "stable" releases... aren't. Can't reliably connect, interface is useless, reinstalling doesn't fix anything. Also reverting to Synergy 1. And I just paid $29 for a second license - more fool me.

[GaryZheng]

4 hours ago, Wei Jin said:

synergy still can not connect to pubsub1.cloud.symless.com:443 even though I setup a VPN. But pinged pubsub1.cloud.symless.com with OK responses.

Pinged(icmp) ok dosen't mean any thing. synergy-service connects under tcp protocol, whitch GFW can easy block TCP traffic on port 443.

 

4 hours ago, Wei Jin said:

synergy still can not connect to pubsub1.cloud.symless.com:443 even though I setup a VPN. But pinged pubsub1.cloud.symless.com with OK responses.

Are you sure you are under a "Globle mode"? In my case, after proxy synergy-service, this app runs great.

[Heidi]

3 hours ago, VVE1505 said:

Even worse, there doesn't seem to be any resolution to all these threads I'm seeing in the forum. I did a wireshark capture and it looks like a session is established between my host and the 45.55.221.2 server and then just when data is being transferred back and forth, the server ends the connection.

It's an issue with the self-signed SSL certificate. Self-Signed certificates are not trusted by default. I believe Nick will need to install the the self-signed cert as a trusted server. Self-Signed certificates are vulnerable to man-in-the-middle attacks.

heidi@imladras$ openssl s_client -connect pubsub1.cloud.symless.com:443
CONNECTED(00000003)
depth=0 CN = 165.227.29.181
verify error:num=18:self signed certificate
verify return:1
depth=0 CN = 165.227.29.181
verify return:1
---
Certificate chain
 0 s:/CN=165.227.29.181
   i:/CN=165.227.29.181
---
Server certificate
-----BEGIN CERTIFICATE-----
MIICrjCCAZYCCQCYVdVnbUXWjzANBgkqhkiG9w0BAQsFADAZMRcwFQYDVQQDDA4x
NjUuMjI3LjI5LjE4MTAeFw0xNzA4MjExNTE0MTNaFw0xODA4MjExNTE0MTNaMBkx
FzAVBgNVBAMMDjE2NS4yMjcuMjkuMTgxMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAr4EOvxyXgzyiuhrlakCMUDtRnPvRwalNrPcPP7x1XSOsHOUkbl/W
/ufJsw2tSkatvkcCnyBN3Q48ovgaWtaGLDQ0pqTVl5gHuTggpQBSEbIBeCDdkJdA
xocNiWu6mKWB9ulWZ4BaXO0LObZ4tSHLZD6pDzbIeu8nkXCGQ2JF0+Ov/l4eY0SU
rgWezpmh2FdkSj4gNbJjeYVEUjTCWwMxZ3VCS3/IiQPB4sFAqq19o7bU2NFS29uD
bDDCsiFK+FJsg9wXjnmuE+GyF3g7u/dMAYecAMxE2BWAWbsiLMjdVHf47nsBdn2p
+yc5Wmioc+W2TlHWQFzsCKhb4XYvztYsaQIDAQABMA0GCSqGSIb3DQEBCwUAA4IB
AQAWW+CVmFNFSx7A+7WL+noyI1isYGbAuILD1Pvgw+iH/EIor5RSvR7VrHw4aei9
VCN5SD+tpxXEjUJhfKwWC6R/rKM/hoohoVjhmrFnFgTE8Vq/WrzYabc8PDAx63tJ
ttuSnZOPc7uS1eyOmwMgFCG3iDyiHNqVo2iVrIeKYvC6sOmskLjFH5U+l9YBaRQ+
/FwY/GjdrC0lUqMLA09tk+sIfCYuH8lWs4TBe/btspIrxl/7L0SwwHDkyCnvcO5d
Z3dgg+UZ7akAWVzhUKncvXwMoFCvArohLyX7SR6guurZSX+pTqTgJEpewoHrzGoA
7e3xS/BeA/TwqBEExt+R/vvf
-----END CERTIFICATE-----
subject=/CN=165.227.29.181
issuer=/CN=165.227.29.181
---
No client certificate CA names sent
Peer signing digest: SHA512
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 1331 bytes and written 269 bytes
Verification error: self signed certificate
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: 0232F82A9B3DE0A8217CD55ADD261BC20D3260241F9C23897C7B10FDF9ED2FE4
    Session-ID-ctx: 
    Master-Key: EDC60F370CA84E5AE6AE2136F019B2F3F0BA62332A9CF071831F4460D2EC96B973859086F92F8ACB143B77E7075F4982
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - 11 86 e9 61 d9 69 2c c6-8c 41 95 bf 98 24 33 67   ...a.i,..A...$3g
    0010 - 49 63 08 e3 f5 53 4b 3d-26 64 10 76 41 6e ce bc   Ic...SK=&d.vAn..
    0020 - a4 47 32 e3 a4 1c ec 59-19 e0 8e d7 4e 03 b3 6d   .G2....Y....N..m
    0030 - 3f ba 72 f1 53 72 f1 65-92 27 51 28 73 b6 80 aa   ?.r.Sr.e.'Q(s...
    0040 - 8d 98 cb 9e 74 9b cf 6d-c5 29 57 a9 18 4a f1 bc   ....t..m.)W..J..
    0050 - 04 fb 7e 22 5f 6b 30 8f-55 fd 9d 65 92 94 1b 7a   ..~"_k0.U..e...z
    0060 - a0 22 66 5a e5 33 63 bc-47 66 86 2a f1 4e 76 95   ."fZ.3c.Gf.*.Nv.
    0070 - 29 b6 d1 cf f5 d9 75 3a-14 b6 73 7b 45 0a d3 51   ).....u:..s{E..Q
    0080 - 24 6d 2d 24 38 6e 76 2c-a7 5d 41 5a 7f e6 90 5e   $m-$8nv,.]AZ...^
    0090 - 39 67 bc 36 71 72 72 9d-f9 bc 70 d1 18 68 ed 7e   9g.6qrr...p..h.~
    00a0 - 97 fc 5b 62 e8 b4 92 f2-20 2c d2 55 0a 0e b9 9e   ..[b.... ,.U....

    Start Time: 1511806093
    Timeout   : 7200 (sec)
    Verify return code: 18 (self signed certificate)
    Extended master secret: yes
---
closed

heidi@imladras$ gnutls-cli pubsub1.cloud.symless.com
Processed 151 CA certificate(s).
Resolving 'pubsub1.cloud.symless.com'...
Connecting to '45.55.221.2:443'...
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
 - subject `CN=165.227.29.181', issuer `CN=165.227.29.181', RSA key 2048 bits, signed using RSA-SHA256, activated `2017-08-21 15:14:13 UTC', expires `2018-08-21 15:14:13 UTC', SHA-1 fingerprint `d182bfab9f0239147939cf1f9ff1058e1c8f524c'
	Public Key ID:
		fbf3584762bd0b514d5940740bf3c205e85ae6f5
	Public key's random art:
		+--[ RSA 2048]----+
		|            .*=o*|
		|           .. ==.|
		|          .  o.o.|
		|           + +.  |
		|        S = = +  |
		|         o o + E |
		|        .   o o  |
		|         ..o o . |
		|          oo. .  |
		+-----------------+

- Status: The certificate is NOT trusted. The certificate issuer is unknown. The name in the certificate does not match the expected. 
*** PKI verification of server certificate failed...
*** Fatal error: Error in the certificate.
*** Handshake has failed
GnuTLS error: Error in the certificate.

 

http://gagravarr.org/writing/openssl-certs/errors.shtml

[JustDave]

I uninstalled the current version and installed 1.8, until this is resolved.

[bugfry]

Hi,

i just upgraded to version 2 and i'm not able to connect to the "cloud". can somone give me a hint how to solve this?

 

Platform:

arch linux - 4.13.12-1-ARCH

packet synergy2 2.0.2.stable~b1046+665fa610-1 (AUR)

systemctl

Nov 27 22:51:24 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:24] debug: retrying websocket connection now
Nov 27 22:51:24 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:24] debug: connecting websocket: pubsub1.cloud.symless.com:443
Nov 27 22:51:24 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:24] error: websocket handshake error 3: WebSocket Upgrade handshake failed
Nov 27 22:51:24 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:24] error: websocket handshake response 400: Bad Request
Nov 27 22:51:24 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:24] debug: clearing last profile snapshot
Nov 27 22:51:24 ikarus synergy-service[594]: [ Service ] [2017-11-27T22:51:24] debug: retrying websocket connection in 10s

config tool starting

"[ Config  ] " "[2017-11-27T23:04:14] debug: install dir: /usr/bin" 
"[ Config  ] " "[2017-11-27T23:04:14] info: log filename: /var/log/synergy/synergy-combined.log" 
QObject::startTimer: Timers cannot have negative intervals
"[ Config  ] " "[2017-11-27T23:04:14] debug: connecting to background service" 
"[ Config  ] " "[2017-11-27T23:04:14] debug: connected to background service" 
"[ Config  ] " "[2017-11-27T23:04:14] debug: sending uid to service: 1000" 
"[ Config  ] " "[2017-11-27T23:04:14] debug: saying hello to background service" 
qrc:/ActivationPage.qml:65:21: QML Image: Binding loop detected for property "sourceSize.height"
qrc:/ActivationPage.qml:65:21: QML Image: Error decoding: qrc:/res/image/symless-signin-button.svg: Unsupported image format
"" "[ Service ] [2017-11-27T23:04:14] debug: setting core uid from rpc: 1000" 
"" "[ Service ] [2017-11-27T23:04:14] debug: saying hello to config ui" 
"[ Config  ] " "[2017-11-27T23:04:14] debug: service cloud connection error" 
"" "[ Service ] [2017-11-27T23:04:14] debug: retrying websocket connection now" 
"" "[ Service ] [2017-11-27T23:04:14] debug: connecting websocket: pubsub1.cloud.symless.com:443" 
"" "[ Service ] [2017-11-27T23:04:15] error: websocket handshake error 3: WebSocket Upgrade handshake failed" 
"" "[ Service ] [2017-11-27T23:04:15] error: websocket handshake response 400: Bad Request" 
"" "[ Service ] [2017-11-27T23:04:15] debug: clearing last profile snapshot" 
"[ Config  ] " "[2017-11-27T23:04:15] debug: service cloud connection error" 
"" "[ Service ] [2017-11-27T23:04:15] debug: retrying websocket connection in 20s" 
"[ Config  ] " "[2017-11-27T23:04:15] debug: current version is update to date" 
"[ Config  ] " "[2017-11-27T23:04:15] debug: current version is update to date" 
QThreadStorage: Thread 0x7fe0bc003220 exited after QThreadStorage 7 destroyed

ping pubsub1.cloud.symless.com
PING pubsub.cloud.symless.com (45.55.221.2) 56(84) bytes of data.
64 bytes from 45.55.221.2 (45.55.221.2): icmp_seq=1 ttl=55 time=87.1 ms

 

[Andyroo]

I get the "problem connecting to the auto-config service" error on both my Windows PC and Mac. Nick, have you considered using a local config file? I don't understand what's the point of a cloud config service, especially when all the above users can't connect to it! Synergy just doesn't work. Sadly after my attempts to make one of the betas work, which failed, I was hoping for better with a "stable" release. Annoyingly I too now have to uninstall and reinstall an older version. Such a waste of time. :-(

[LiQing]

This is from Symless Team. Add an offline version in Synergy 2.1

[UltimateOutsider]

6 hours ago, bugfry said:

Hi,

i just upgraded to version 2 and i'm not able to connect to the "cloud". can somone give me a hint how to solve this?

 

Well, unlike every other internet application I use on Ubuntu, Synergy 2 doesn't seem capable of working through an internet proxy- at least not by using the system's proxy settings. (Perhaps there's a manual config file option you can tweak?) If you are behind a firewall, this is probably the problem. See this thread. I just uninstalled and went back to version 1.8.

14 minutes ago, LiQing said:

This is from Symless Team. Add an offline version in Synergy 2.1

In my case Synergy2 isn't explicitly being blocked by any firewall, the application is just not honoring my system's internet proxy settings. I am wondering whether they actually developed this tool without proxy support? Previous versions didn't need it, but now that you have to sign on to a cloud account...