BradA

Beta4, Two W10 machines won't connect

17 posts in this topic

Yesterday Installed B3 over 1.86 and due to expiry issues was not able to run.
This morning installed B4 over B3. Unable to connect.
Uninstalled B4 then reinstalled B4.
Neither machine will connect. Just gray icon in middle of each.

https://synergy-logs.symless.com/2017-09-14/183-2017-09-14T06-29-18.log

Logs show that the other computer "actively refused" the connection. 

Yes, both firewalls have been turned off and workstations rebooted.
Also FWIW, both firewalls had the Synergy2 Any/Any rule enabled.
 

Share this post


Link to post
Share on other sites
[ Service ] [2017-09-14T06:29:04] debug: connecting websocket
[ Service ] [2017-09-14T06:29:05] debug: tcp client connect error: No connection could be made because the target machine actively refused it
[ Service ] [2017-09-14T06:29:05] debug: websocket connect failed
[ Service ] [2017-09-14T06:29:05] debug: retrying websocket connection in 3s

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

Yes, I'm typing this on the workstation that provided that log. I saw the successful connection to the mothership's 'you can go back to the Synergy application' page when it validated.

Both workstations are showing that error, and both can successfully connect to the internet. 
And both computers can see each other, I downloaded B4 on this one and copied it directly over to the other one.

Share this post


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

Yes, both firewalls have been turned off and workstations rebooted.
Also FWIW, both firewalls had the Synergy2 Any/Any rule enabled.

That's the only steps I see in the guide.

Share this post


Link to post
Share on other sites

 

5 hours ago, Nick Bolton said:
[ Service ] [2017-09-14T06:29:04] debug: connecting websocket
[ Service ] [2017-09-14T06:29:05] debug: tcp client connect error: No connection could be made because the target machine actively refused it
[ Service ] [2017-09-14T06:29:05] debug: websocket connect failed
[ Service ] [2017-09-14T06:29:05] debug: retrying websocket connection in 3s

This indicates that the service can't talk to the cloud server. Does this computer have a working internet connection?

Too bad we don't know where that websocket is.
I thought you said in another post that it only phoned home once to verify serial number then would not do that again. Both of mine successfully did the validation. Why are they trying to phone home again?

Too bad we don't know what websocket it is trying to connect to. I'd like to see if there is something blocking it. (although my PC's firewall is Off)

 

  • Like 1

Share this post


Link to post
Share on other sites

I am experiencing the same issue. Is there anything I should/could try?

Share this post


Link to post
Share on other sites

Did the upgrade>now no communication between server and client:(  here's my error logs

[ Config ] [2017-09-14T15:50:03] INFO: log filename: C:/Users/ykiyomi-zonetech/AppData/Local/Symless/Synergy/synergy.log

[ Config ] [2017-09-14T15:50:03] DEBUG: connecting to service

[ Config ] [2017-09-14T15:50:03] DEBUG: connected to service

[ Config ] [2017-09-14T15:50:04] DEBUG: new added screen pos: 257 161

[ Config ] [2017-09-14T15:50:04] DEBUG: Profile ID: 127 name: default

[ Config ] [2017-09-14T15:50:04] DEBUG: current version is update to date

[ Config ] [2017-09-14T15:50:04] DEBUG: requesting profile snapshot

[ Service ] [2017-09-14T15:50:04] debug: connecting websocket

[ Service ] [2017-09-14T15:50:04] debug: tcp session ssl handshake error: The network connection was aborted by the local system

[ Service ] [2017-09-14T15:50:04] debug: websocket connect failed

[ Service ] [2017-09-14T15:50:04] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:50:04] error: can't send profile snapshot, not yet received from cloud

[ Service ] [2017-09-14T15:50:07] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:50:07] debug: connecting websocket

[ Service ] [2017-09-14T15:50:29] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:50:29] debug: websocket connect failed

[ Service ] [2017-09-14T15:50:29] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:50:32] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:50:32] debug: connecting websocket

[ Service ] [2017-09-14T15:50:53] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:50:53] debug: websocket connect failed

[ Service ] [2017-09-14T15:50:53] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:50:56] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:50:56] debug: connecting websocket

[ Service ] [2017-09-14T15:51:18] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:51:18] debug: websocket connect failed

[ Service ] [2017-09-14T15:51:18] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:51:21] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:51:21] debug: connecting websocket

[ Service ] [2017-09-14T15:51:42] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:51:42] debug: websocket connect failed

[ Service ] [2017-09-14T15:51:42] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:51:45] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:51:45] debug: connecting websocket

[ Service ] [2017-09-14T15:52:06] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:52:06] debug: websocket connect failed

[ Service ] [2017-09-14T15:52:06] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:52:09] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:52:09] debug: connecting websocket

[ Service ] [2017-09-14T15:52:31] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:52:31] debug: websocket connect failed

[ Service ] [2017-09-14T15:52:31] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:52:34] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:52:34] debug: connecting websocket

[ Service ] [2017-09-14T15:52:55] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:52:55] debug: websocket connect failed

[ Service ] [2017-09-14T15:52:55] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:52:58] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:52:58] debug: connecting websocket

[ Service ] [2017-09-14T15:53:19] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:53:19] debug: websocket connect failed

[ Service ] [2017-09-14T15:53:19] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:53:22] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:53:22] debug: connecting websocket

[ Service ] [2017-09-14T15:53:44] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:53:44] debug: websocket connect failed

[ Service ] [2017-09-14T15:53:44] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:53:47] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:53:47] debug: connecting websocket

[ Service ] [2017-09-14T15:54:08] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:54:08] debug: websocket connect failed

[ Service ] [2017-09-14T15:54:08] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:54:11] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:54:11] debug: connecting websocket

[ Service ] [2017-09-14T15:54:32] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:54:32] debug: websocket connect failed

[ Service ] [2017-09-14T15:54:32] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:54:35] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:54:35] debug: connecting websocket

[ Service ] [2017-09-14T15:54:57] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:54:57] debug: websocket connect failed

[ Service ] [2017-09-14T15:54:57] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:55:00] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:55:00] debug: connecting websocket

[ Config ] [2017-09-14T15:55:11] INFO: Sending log file...

[ Config ] [2017-09-14T15:55:12] INFO: Upload path: https://synergy-logs.symless.com/2017-09-14/132-2017-09-14T15-55-12.log

[ Service ] [2017-09-14T15:55:21] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:55:21] debug: websocket connect failed

[ Service ] [2017-09-14T15:55:21] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:55:24] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:55:24] debug: connecting websocket

[ Service ] [2017-09-14T15:55:46] debug: tcp session ssl handshake error: The semaphore timeout period has expired

[ Service ] [2017-09-14T15:55:46] debug: websocket connect failed

[ Service ] [2017-09-14T15:55:46] debug: retrying websocket connection in 3s

[ Service ] [2017-09-14T15:55:49] debug: retrying websocket connection now

[ Service ] [2017-09-14T15:55:49] debug: connecting websocket

Share this post


Link to post
Share on other sites
13 hours ago, BradA said:

I thought you said in another post that it only phoned home once to verify serial number

Actually no, it uses the WebSocket connection for initial configuration. Once this is done, you can go offline.

Share this post


Link to post
Share on other sites
10 hours ago, Von said:

[ Service ] [2017-09-14T15:50:29] debug: tcp session ssl handshake error: The semaphore timeout period has expired

Could be a bug. Are you seeing the same thing today?

Share this post


Link to post
Share on other sites

> debug: tcp client connect error: No connection could be made because the target machine actively refused it

Same issue for me it seems. All machines are behind the same corporate proxy, so anything going out of the network using weird ports (i.e. all but 80 or 443) or not leveraging the system-configured proxy would obviously fail.

Share this post


Link to post
Share on other sites
44 minutes ago, Christoph Rüegg said:

corporate proxy

Ah, we're fixing that in beta5.

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, Christoph Rüegg said:

using weird ports (i.e. all but 80 or 443)

I forgot to say, it was meant to use 443 (due to a bug, it isn't in beta4).

Share this post


Link to post
Share on other sites
1 hour ago, Nick Bolton said:

I forgot to say, it was meant to use 443 (due to a bug, it isn't in beta4).

So are you not using port 443 in this beta4? 

Share this post


Link to post
Share on other sites
6 hours ago, SystemsEngWookie said:

So are you not using port 443 in this beta4? 

Annoyingly, no. We should have fixed that for beta4.

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