kamilosxd678

Only one computer present

15 posts in this topic

Hi,

I have just installed Synergy 2.0.0-beta4 and I have it opened on two different computers (which were previously connected via Synergy 1 and worked), but in the main Synergy 2 Window I can only see the computer that it is installed on. I have both installations connected to my account but I can't do anything. The new interface is too minimalistic for me :-( as I cannot do anything beside staring at it and hoping for it to work.

On the screenshot (you have to believe me :-)) Both names that I censored are the same.

 

Oh and of course - Both computers are working on Windows 10

Capture.PNG

Edited by kamilosxd678

Share this post


Link to post
Share on other sites

I'm having the same problem, my Win10 PC is seeing only itself, whilst my MacBook is seeing both itself and the Windows PC.

Share this post


Link to post
Share on other sites

Same here on Linux Manjaro & OSX

WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop" 
"[ Config  ] [2017-10-10T10:10:52] DEBUG: new added screen pos: 257 161"  

"[ Config  ] [2017-10-10T10:10:53] DEBUG: Profile ID: 5223 name: default"  

"[ Config  ] [2017-10-10T10:10:53] DEBUG: current version is update to date"  

"[ Config  ] [2017-10-10T10:10:53] DEBUG: requesting profile snapshot"  

"[ Config  ] [2017-10-10T10:11:06] ERROR: Reply status code: 400"  

"[ Config  ] [2017-10-10T10:11:06] ERROR: Reply error message: Invalid JSON request: bad numeric conversion: negative overflow"  

"[ Config  ] [2017-10-10T10:11:07] ERROR: Reply status code: 400"  

"[ Config  ] [2017-10-10T10:11:07] ERROR: Reply error message: Invalid JSON request: bad numeric conversion: negative overflow" 

 

Share this post


Link to post
Share on other sites

@Gelldur how did you get the logs? You are running synergy from console or is there a log file?

Share this post


Link to post
Share on other sites

Same here, on both systems, just one screen.

That is what I see in the bash output on that Linux Box.

[wamp_broker.cpp:149][process_publish_message] session [2257228500326156,default,open], event [2, 8463673705195253, {}, ["[2017-10-10T11:35:41] debug: websocket connect failed\n"], null]
[rawsocket_transport.cpp:39][send_message] sending message: event
[wamp_message_processor.cpp:47][process_message] processing message: publish
[wamp_broker.cpp:111][process_publish_message] session [7090515283965860,default,open], publish [586, {}, synergy.service.log, ["[2017-10-10T11:35:41] debug: retrying websocket connection in 3s\n"], null]
[wamp_broker.cpp:149][process_publish_message] session [2257228500326156,default,open], event [2, 7733118315066044, {}, ["[2017-10-10T11:35:41] debug: retrying websocket connection in 3s\n"], null]
[rawsocket_transport.cpp:39][send_message] sending message: event

 

Edited by MegaTraveller
Added Output

Share this post


Link to post
Share on other sites

FYI previous version of synergy 1.8 was working on same setup. So this isn't local network problem.

 

Edited by Gelldur

Share this post


Link to post
Share on other sites

To get to the logs - press your 'grave' key  ...  looks like this  `  - that's the one on LHS of no. 1 on top row of keyboard

Share this post


Link to post
Share on other sites

Turns out that on Windows, the log is written into %appdata%/../Local/Symless/Synergy/synergy.log

It says
 

Quote

[ Config  ] [2017-10-10T08:13:14] DEBUG: connecting to service
[ Config  ] [2017-10-10T08:13:14] DEBUG: connected to service
[ Config  ] [2017-10-10T08:13:15] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-10T08:13:16] DEBUG: Profile ID: 5146 name: default
[ Config  ] [2017-10-10T08:13:16] DEBUG: current version is update to date
[ Config  ] [2017-10-10T08:13:16] DEBUG: requesting profile snapshot
[ Service ] [2017-10-10T08:13:16] debug: connecting websocket
[ Service ] [2017-10-10T08:13:16] error: can't send profile snapshot, not yet received from cloud
[ Service ] [2017-10-10T08:13:37] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:13:37] debug: websocket connect failed
[ Service ] [2017-10-10T08:13:37] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:13:40] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:13:40] debug: connecting websocket
[ Service ] [2017-10-10T08:14:01] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:14:01] debug: websocket connect failed
[ Service ] [2017-10-10T08:14:01] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:14:04] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:14:04] debug: connecting websocket
[ Service ] [2017-10-10T08:14:25] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:14:25] debug: websocket connect failed
[ Service ] [2017-10-10T08:14:25] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:14:28] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:14:28] debug: connecting websocket
[ Service ] [2017-10-10T08:14:49] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:14:49] debug: websocket connect failed
[ Service ] [2017-10-10T08:14:49] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:14:52] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:14:52] debug: connecting websocket
[ Service ] [2017-10-10T08:15:13] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:15:13] debug: websocket connect failed
[ Service ] [2017-10-10T08:15:13] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:15:16] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:15:16] debug: connecting websocket
[ Service ] [2017-10-10T08:15:37] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:15:37] debug: websocket connect failed
[ Service ] [2017-10-10T08:15:37] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:15:40] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:15:40] debug: connecting websocket
[ Service ] [2017-10-10T08:16:01] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:16:01] debug: websocket connect failed
[ Service ] [2017-10-10T08:16:01] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:16:04] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:16:04] debug: connecting websocket
[ Service ] [2017-10-10T08:16:25] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:16:25] debug: websocket connect failed
[ Service ] [2017-10-10T08:16:25] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:16:28] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:16:28] debug: connecting websocket
[ Service ] [2017-10-10T08:16:49] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:16:49] debug: websocket connect failed
[ Service ] [2017-10-10T08:16:49] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:16:52] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:16:52] debug: connecting websocket
[ Service ] [2017-10-10T08:17:13] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:17:13] debug: websocket connect failed
[ Service ] [2017-10-10T08:17:13] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:17:16] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:17:16] debug: connecting websocket
[ Service ] [2017-10-10T08:17:37] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:17:37] debug: websocket connect failed
[ Service ] [2017-10-10T08:17:37] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:17:40] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:17:40] debug: connecting websocket
[ Service ] [2017-10-10T08:18:01] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:18:01] debug: websocket connect failed
[ Service ] [2017-10-10T08:18:01] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:18:04] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:18:04] debug: connecting websocket
[ Service ] [2017-10-10T08:18:25] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:18:25] debug: websocket connect failed
[ Service ] [2017-10-10T08:18:25] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:18:28] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:18:28] debug: connecting websocket
[ Service ] [2017-10-10T08:18:49] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-10T08:18:49] debug: websocket connect failed
[ Service ] [2017-10-10T08:18:49] debug: retrying websocket connection in 3s
[ Service ] [2017-10-10T08:18:52] debug: retrying websocket connection now
[ Service ] [2017-10-10T08:18:52] debug: connecting websocket


It may be a problem with proxies at my workplace, but they are configured in the system and I don't see any "configuration" button inside the new synergy

Share this post


Link to post
Share on other sites

Same here. Two Macs, same WiFi network, firewalls off on both. Is there a way to use a pre-configured config file like Synergy 1.x? 

The lack of discoverability of any setup or configuration for Synergy2 isn't very user friendly, even for beta testers.

 

Share this post


Link to post
Share on other sites

Sorry you guys are having such problems. Beta 4 is pretty bad, but there are those power users that have made it work for them. I'm not one of them, I had to step back to 1.8 in my system and wait anxiously for beta 5, promised to drop soon.

A good troubleshooting guide is one of the stickies at the top of this forum.  

If you are having issues with Win instances it almost always involves the firewall, check out this link: 

My own quick note... when you re-install on a Win, note that standard Win un-install leaves behind some files, notably under Users>>(your name)AppData>Synergy>...just delete that folder. Synergy version 1 used to leave behind:           Synergy.conf under AppData\Local\Symless\synergy.conf         that needs to go before reinstallation. I'm a fan of Revo Uninstaller that finds these left-behinds for you...there are other programs that do the same. But a little time and patience searching your HD will do the same.

If you just throw up your hands and want a refund, Symless is prompt to accommodate. But If you just let it ride, you have some financial consideration for the final product of version 2. But since you have an appreciation for what Synergy has done for you and can do in the future, I'd say think about just letting it ride until the next trial and error beta drops. or until the final polished product is marketed. BTW version 1 is going to be around for a very long time yet.

 

 

Share this post


Link to post
Share on other sites

Hmm maybe here is the issue that i have some settings from v1. I will check tomorrow. It would be nice still have Beta and stable app separated so when something isn't working I can switch. No I can only have 1 app.

Share this post


Link to post
Share on other sites

Yeah, I don't see a way to toggle back and forth. BTW on your first graphic, the gray image indicates it is not connected to another computer. Does the other machine look the same?  A connection would be shown by a green box...screen...monitor image. Did you say both computers have the same name? How did that work in version 1? I guess you could have entered the different IP addresses. In beta 4, the cloud auto-configure should have done so for you anyway.  In my setup, If I saw that image, I would thoroughly uninstall both sides, restart the machines and then reinstall. When they are first installed they reach out to the Symless cloud server and "handshake." the cloud matches the credentials from both and makes a connection. That can take a couple of minutes. If 5 minutes went by, something else is broke. Later on, or maybe next beta, the connection to the cloud isn't necessary over and over since it's only there to auto-configure. You're right, there is not much you can do with that UI in the beta 4 testing version. You can shift+~ and see the log. You can right-click on the log to send it to the forum, (let us know the link). You can also press F12 to force one side or the other to be the server. 

In Win > Win, check your Windows Firewall. One of the Stickies on this forum lists the 3 Synergy files that need to be permitted, both sides. You can turn off the Firewall briefly to troubleshoot, but I wouldn't leave mine off for any length of time.

Edited by KringleKrebs

Share this post


Link to post
Share on other sites

I've reverted back to 1.8 because it works within my corporate VPN but I note you say "Later on, or maybe next beta, the connection to the cloud isn't necessary over and over since it's only there to auto-configure" This gives me hope that the VPN issue will be overcome.

I have beta4 working on my company laptop (when not logged into the VPN) and my home Linux desktop and it seems much more responsive than 1.8 so I am not giving up hope!

Share this post


Link to post
Share on other sites

1.8.8 actually works while connected to my corporate VPN, even though it disallows split tunneling. I have no idea how Synergy manages to work (zeroconf? bluetooth?) but it does. 

As for following the troubleshooting... doing things like checking for the correct IP is useless, as there is no configuration option UI available in Synergy 2 to make those changes.

Edited by JasonG

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