Nahian 5 Posted September 7, 2017 Share Posted September 7, 2017 My mac stopped connecting. It is showing two different Macbook pros and neither is connecting. Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 7, 2017 Synergy Team Share Posted September 7, 2017 Hey, beta4 should fix this. It'll be out in a few days. Thanks for waiting! Link to post Share on other sites
Nahian 5 Posted September 12, 2017 Author Share Posted September 12, 2017 Hi @Nick Bolton Are you going to release beta 4 today? Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 12, 2017 Synergy Team Share Posted September 12, 2017 We're putting the finishing touches on now! Link to post Share on other sites
Nahian 5 Posted September 13, 2017 Author Share Posted September 13, 2017 Please release soon. I am struggling without synergy. I am addicted to your product  1 Link to post Share on other sites
Nahian 5 Posted September 13, 2017 Author Share Posted September 13, 2017 @Nick Bolton Still having issues even with beta 4. I just sent logs using the console Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 14, 2017 Synergy Team Share Posted September 14, 2017 Hmm, upgrade handshake failed? That's a new one! Could you please send the logs for all 3 computers? Â Link to post Share on other sites
Sartorum 0 Posted September 14, 2017 Share Posted September 14, 2017 @Nick Bolton, Hi! I have the same problem described by @Nahian, but none of my machines are green and all are sending the same debug log message. The log for my mac can be found here:Â https://synergy-logs.symless.com/2017-09-14/80-2017-09-14T07-16-26.log Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 14, 2017 Synergy Team Share Posted September 14, 2017 [ Service ] [2017-09-14T07:14:48] debug: connecting websocket [ Service ] [2017-09-14T07:16:03] debug: tcp client connect error: Operation timed out [ Service ] [2017-09-14T07:16:03] debug: websocket connect failed [ Service ] [2017-09-14T07:16:03] debug: retrying websocket connection in 3s [ Service ] [2017-09-14T07:16:06] debug: retrying websocket connection now [ Service ] [2017-09-14T07:16:06] debug: connecting websocket This indicates that the service can't talk to the cloud server. Does this computer have a working internet connection? Link to post Share on other sites
Nahian 5 Posted September 14, 2017 Author Share Posted September 14, 2017 @Nick Bolton yes, i have internet connection and am connected to many applications Link to post Share on other sites
Nahian 5 Posted September 14, 2017 Author Share Posted September 14, 2017 https://synergy-logs.symless.com/2017-09-14/134-2017-09-14T09-09-31.log Link to post Share on other sites
filemoon 3 Posted September 14, 2017 Share Posted September 14, 2017 I have very same issue. It is not working between Mac and Windows. 1 Link to post Share on other sites
Naidu 3 Posted September 14, 2017 Share Posted September 14, 2017 (edited) @Nick Bolton I have the same issue between Mac and windows: https://synergy-logs.symless.com/2017-09-14/24-2017-09-14T10-04-08.log . Windows show connected but Mac can't seem to connect.  [ Service ] [2017-09-14T09:59:13] debug: profile screen test result changed, screenId=22 success=``->`` failed=``->`192.168.1.17` [ Service ] [2017-09-14T09:59:13] debug: handling new report from connectivity tester, screenId=22 successfulIp= lastServerId=22 [ Service ] [2017-09-14T09:59:13] debug: finished connectivity test  Edited September 14, 2017 by Naidu Link to post Share on other sites
Naidu 3 Posted September 14, 2017 Share Posted September 14, 2017 Another log:Â https://synergy-logs.symless.com/2017-09-14/24-2017-09-14T10-32-33.log [ Service ] [2017-09-14T10:30:24] debug: profile screen test result changed, screenId=22 success=``->`` failed=``->`192.168.1.17` [ Service ] [2017-09-14T10:30:24] debug: handling new report from connectivity tester, screenId=22 successfulIp= lastServerId=22 [ Service ] [2017-09-14T10:30:24] debug: finished connectivity test [ Service ] [2017-09-14T10:31:36] debug: tcp client connect error: Operation timed out [ Service ] [2017-09-14T10:31:36] debug: connectivity test failed for 192.168.1.17:24810 [ Config ] [2017-09-14T10:32:32] INFO: Sending log file... Â Link to post Share on other sites
Naidu 3 Posted September 14, 2017 Share Posted September 14, 2017 It seems like I was able to make it work by opening ports on my windows machine. I am not sure why it didn't auto open required ports in windows firewall. Link to post Share on other sites
Nahian 5 Posted September 20, 2017 Author Share Posted September 20, 2017 @Nick Bolton any updates on this? It is still not working for me. Link to post Share on other sites
filemoon 3 Posted September 20, 2017 Share Posted September 20, 2017 I was able to fix this when windows firewall was edited (24810 port - inbound rule). I don't think Synergy 2.0 is ready for usage. Link to post Share on other sites
Nahian 5 Posted September 20, 2017 Author Share Posted September 20, 2017 My mac will not connect so i have a different issue. Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 20, 2017 Synergy Team Share Posted September 20, 2017 11 minutes ago, Nahian said: @Nick Bolton any updates on this? It is still not working for me. How many times did you try restarting services on all of the computers? Link to post Share on other sites
Nahian 5 Posted September 20, 2017 Author Share Posted September 20, 2017 I restarted the computers completely several times. 10+ times since i started this thread. Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 20, 2017 Synergy Team Share Posted September 20, 2017 14 minutes ago, Nahian said: I restarted the computers completely several times. 10+ times since i started this thread. Can you send your logs? Link to post Share on other sites
Nahian 5 Posted September 20, 2017 Author Share Posted September 20, 2017 @Nick Bolton from the mac https://synergy-logs.symless.com/2017-09-20/134-2017-09-20T15-44-04.log  Link to post Share on other sites
Nahian 5 Posted September 20, 2017 Author Share Posted September 20, 2017 @Nick Bolton from the windows machine https://synergy-logs.symless.com/2017-09-20/134-2017-09-20T15-46-05.log  Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted September 21, 2017 Synergy Team Share Posted September 21, 2017 Looks like the Mac is the issue: [ Service ] [2017-09-20T15:43:23] debug: connecting websocket [ Service ] [2017-09-20T15:43:23] warning: tcp client already in connecting We're fixing that in beta5. 1 Link to post Share on other sites
Popular Post Nahian 5 Posted September 21, 2017 Author Popular Post Share Posted September 21, 2017 when is beta 5 due out? 6 minutes ago, Nick Bolton said: Looks like the Mac is the issue: [ Service ] [2017-09-20T15:43:23] debug: connecting websocket [ Service ] [2017-09-20T15:43:23] warning: tcp client already in connecting We're fixing that in beta5. Â 2 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