Jack Martin 2 Posted December 7, 2017 Share Posted December 7, 2017 I'm from China, Synergy 2: There was a problem connecting to the auto-config service. Retry. After RETRY many times, RETRY of course does nothing. https://synergy-logs.symless.com/1e36fe18a8416e9903085488d94b5e97/logs/13861-2017-12-07T14-56-24.log [ Service ] [2017-12-07T14:53:41] debug: retrying websocket connection now [ Service ] [2017-12-07T14:53:41] debug: connecting websocket: pubsub1.cloud.symless.com:443 [ Config ] [2017-12-07T14:53:42] debug: service cloud connection error from log I found Synergy 2 need to connect to pubsub1.cloud.symless.com:443 and just using cmd&telnet give a shot visit from local network, connection failed and try vpn to US. connection established Synergy 2 online now. How can I have it in China? Need u help. Link to post Share on other sites
Sasasu 0 Posted December 7, 2017 Share Posted December 7, 2017 Yes, see here chinese-internet-blocks-auto-config-server I have a question, why I must connect to pubsub1 using a self-signed certificate? or why I must connect a public server? Link to post Share on other sites
Jack Martin 2 Posted December 8, 2017 Author Share Posted December 8, 2017 (edited) @Nick Bolton What we do now? and What u can do? Edited December 8, 2017 by Jack Martin Link to post Share on other sites
Jack Martin 2 Posted December 12, 2017 Author Share Posted December 12, 2017 @Nick Bolton ??? do say something. Link to post Share on other sites
kiki 1 Posted December 13, 2017 Share Posted December 13, 2017 gone back to 1.8 Link to post Share on other sites
stuart macmillan 23 Posted December 13, 2017 Share Posted December 13, 2017 Have you logged a call with Symless? This is a user supported forum so you might not get a answer here. https://symless.com/contact/customer-support Link to post Share on other sites
Jack Martin 2 Posted December 13, 2017 Author Share Posted December 13, 2017 1 minute ago, stuart macmillan said: Have you logged a call with Symless? This is a user supported forum so you might not get a answer here. https://symless.com/contact/customer-support I just write a mail to the support team. Thanks @stuart macmillan Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted January 3, 2018 Synergy Team Share Posted January 3, 2018 On 12/12/2017 at 1:25 AM, Jack Martin said: @Nick Bolton ??? do say something. This will most likely be fixed in 2.1. Until then you could either take a refund or use Synergy 1. Link to post Share on other sites
bogdan 0 Posted January 3, 2018 Share Posted January 3, 2018 [ Service ] [2018-01-03T17:23:03] debug: connecting websocket: pubsub1.cloud.symless.com:443 [ Service ] [2018-01-03T17:23:03] error: websocket handshake error 3: WebSocket upgrade handshake failed [ Service ] [2018-01-03T17:23:03] error: websocket handshake response 400: Bad Request I'm getting a different error myself, but related to pubsub1.cloud.symless.com:443 It seems like someone didn't mind buying a SSL certificate? Link to post Share on other sites
Daniel Garcia 7 Posted January 3, 2018 Share Posted January 3, 2018 It's 2017, who self signs certificates anymore? And gets the hostname wrong in the process? 1 Link to post Share on other sites
bogdan 0 Posted January 3, 2018 Share Posted January 3, 2018 It's 2018 for 3 days now. Link to post Share on other sites
Daniel Garcia 7 Posted January 3, 2018 Share Posted January 3, 2018 True - though the cert was signed/created in 2017: Common name: pubsub.cloud.symless.comOrganization: Symless Org. Unit: Synergy CloudValid from December 30, 2017 to December 20, 2019Serial Number: 10342277146623780660 (0x8f872644e526a734)Signature Algorithm: sha256WithRSAEncryptionIssuer: pubsub.cloud.symless.com Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted January 4, 2018 Synergy Team Share Posted January 4, 2018 Try now. Link to post Share on other sites
Sasasu 0 Posted January 4, 2018 Share Posted January 4, 2018 (edited) 1 hour ago, Nick Bolton said: Try now. I am in tianjin, which is a province of China. I connect auto config server successful. but pc1 has 3 ip, 10.0.x.x (vpn), 172.17.0.1(docker), 192.50.x.x pc2 has 1 ip, 192.50.x.x when pc1 as server pc2 will connect 10.0.x.x and 172.17.0.1, will nerver connect 192.50.x.x I think I can fix this problem by myself, let me have a try. Edited January 4, 2018 by Sasasu fix typo Link to post Share on other sites
bogdan 0 Posted January 4, 2018 Share Posted January 4, 2018 3 hours ago, Nick Bolton said: Try now. Hello Nick, Myself I'm getting: [ Service ] [2018-01-04T14:46:10] debug: connecting websocket: pubsub1.cloud.symless.com:443 [ Service ] [2018-01-04T14:46:11] error: websocket handshake error 3: WebSocket upgrade handshake failed [ Service ] [2018-01-04T14:46:11] error: websocket handshake response 400: Bad Request Also, I tried to submit a support ticket but it doesn't work. The submit button simply does nothing. I attached a screenshot from the browser's console. Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted January 4, 2018 Synergy Team Share Posted January 4, 2018 5 hours ago, Sasasu said: pc1 has 3 ip, 10.0.x.x (vpn), 172.17.0.1(docker), 192.50.x.x pc2 has 1 ip, 192.50.x.x The auto connect feature connects to all available IPs, so it should work (it won't matter that you have a 10.x address). Try restarting the background service after enabling/disabling VPN. Link to post Share on other sites
Jack Martin 2 Posted January 5, 2018 Author Share Posted January 5, 2018 @Nick Bolton Oh yeah! EVERYTHING goes well then!!! Thanks so much. Link to post Share on other sites
Jack Martin 2 Posted January 5, 2018 Author Share Posted January 5, 2018 16 hours ago, bogdan said: Hello Nick, Myself I'm getting: pubsub1.cloud.symless.com:443 Also, I tried to submit a support ticket but it doesn't work. The submit button simply does nothing. I attached a screenshot from the browser's console. 尝试下 telnet 下服务器 看看是否有回应 telnet pubsub1.cloud.symless.com 443 如果能连接 按几下回车会显示 如下类似的日志 Quote HTTP/1.1 400 Bad Request Server: nginx Date: Fri, 05 Jan 2018 05:31:09 GMT Content-Type: text/html Content-Length: 166 Connection: close <html> <head><title>400 Bad Request</title></head> <body bgcolor="white"> <center><h1>400 Bad Request</h1></center> <hr><center>nginx</center> </body> </html> 如果连接不上 那就只能 查看你的网络了(我在长春 目前连接正常) If you ar not Chinese, please check you network to pubsub1.cloud.symless.com on port 443 in your cmd type telnet pubsub1.cloud.symless.com 443 type enter key and wait for telnet report Link to post Share on other sites
bogdan 0 Posted January 5, 2018 Share Posted January 5, 2018 Sorry, I'm not Chinese. I was just getting a similar error. telnet pubsub1.cloud.symless.com 443 Trying 45.55.221.2... Connected to pubsub.cloud.symless.com. Escape character is '^]'. Connection closed by foreign host. Link to post Share on other sites
eth0 15 Posted January 5, 2018 Share Posted January 5, 2018 Better yet: use the curl utility: curl -i https://pubsub1.cloud.symless.com It should respond with something like this: HTTP/1.1 200 OK Server: nginx Date: Fri, 05 Jan 2018 11:38:20 GMT Content-Type: text/html Content-Length: 612 Last-Modified: Tue, 11 Jul 2017 13:18:32 GMT Connection: keep-alive ETag: "5964d028-264" Strict-Transport-Security: max-age=31536000 Accept-Ranges: bytes <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/">nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/">nginx.com</a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html> Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted January 26, 2018 Synergy Team Share Posted January 26, 2018 We're planning on creating a cloud infrastructure inside the Great Firewall of China, but the Chinese government are making this difficult for us. Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now