Nahian

Synergy will not connect on Mac (2 Workstations showing)

30 posts in this topic

My mac stopped connecting. It is showing two different Macbook pros and neither is connecting.

Screen Shot 2017-09-07 at 10.51.09 AM.png

Share this post


Link to post
Share on other sites

Hey, beta4 should fix this. It'll be out in a few days. Thanks for waiting!

Share this post


Link to post
Share on other sites

We're putting the finishing touches on now!

Share this post


Link to post
Share on other sites

Please release soon. I am struggling without synergy. I am addicted to your product :)

 

  • Like 1

Share this post


Link to post
Share on other sites

Hmm, upgrade handshake failed? That's a new one! Could you please send the logs for all 3 computers?

 

Share this post


Link to post
Share on other sites
[ 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?

Share this post


Link to post
Share on other sites

I have very same issue. It is not working between Mac and Windows.

  • Like 1

Share this post


Link to post
Share on other sites

@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 by Naidu

Share this post


Link to post
Share on other sites

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...

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

My mac will not connect so i have a different issue. 

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites

I restarted the computers completely several times. 10+ times since i started this thread. 

Share this post


Link to post
Share on other sites
14 minutes ago, Nahian said:

I restarted the computers completely several times. 10+ times since i started this thread. 

Can you send your logs?

Share this post


Link to post
Share on other sites

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.

  • Like 1

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