cguerra Posted August 25, 2017 Share Posted August 25, 2017 12 minutes ago, cguerra said: I am having the same exact issue all of a sudden, was presented with a signin and now signed in, after failing the first time, but now both boxes are black and not green as it used to be, came to the forums to see if others having an issue. Nothing in my environment has changed. Log: [ UI ] [2017-08-25T14:36:20] WARNNIG: no font file: Raleway.otf [ UI ] [2017-08-25T14:36:20] INFO: log filename: C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.log [ UI ] [2017-08-25T14:36:22] DEBUG: new added screen pos: 257 161 [ UI ] [2017-08-25T14:36:23] DEBUG: Profile ID: 56 name: default [ UI ] [2017-08-25T14:36:23] ERROR: Reply status code: 403 [ UI ] [2017-08-25T14:36:23] ERROR: Reply error message: Profile belongs to another user [ UI ] [2017-08-25T14:36:24] DEBUG: current version is update to date [ UI ] [2017-08-25T14:36:24] ERROR: Reply status code: 403 [ UI ] [2017-08-25T14:36:24] ERROR: Reply error message: Invalid session token [ UI ] [2017-08-25T14:37:18] DEBUG: new added screen pos: 257 161 [ UI ] [2017-08-25T14:37:18] DEBUG: Profile ID: 56 name: default [ UI ] [2017-08-25T14:37:19] INFO: write configuration file complete [Core] [2017-08-25T14:37:19] INFO: drag and drop enabled [Core] [2017-08-25T14:37:19] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T14:37:19] DEBUG: configuration read successfully [Core] [2017-08-25T14:37:19] DEBUG: screen shape: 0,0 1920x1080 [Core] [2017-08-25T14:37:19] DEBUG: window is 0x00010ace [Core] [2017-08-25T14:37:19] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T14:37:19] DEBUG: adopting new buffer [Core] [2017-08-25T14:37:19] DEBUG: opened display [Core] [2017-08-25T14:37:19] DEBUG: active sides: 8 [Core] [2017-08-25T14:37:19] DEBUG: active sides: 8 [Core] [2017-08-25T14:37:19] DEBUG: desk Default window is 0x00010ad6 [Core] [2017-08-25T14:37:19] DEBUG: switched to desk "Default" [Core] [2017-08-25T14:37:19] DEBUG: desktop is now accessible [Core] [2017-08-25T14:37:19] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T14:37:20] NOTE: started server, waiting for clients [Core] [2017-08-25T14:37:20] DEBUG: event queue is ready [Core] [2017-08-25T14:37:20] DEBUG: add pending events to buffer [Core] [2017-08-25T14:37:20] DEBUG: screen "cguerra-lpc" shape changed Link to comment Share on other sites More sharing options...
Guest Andrew Nelless Posted August 25, 2017 Share Posted August 25, 2017 We've changed the way updates work to make things more scaleable and temporarily broke beta3 status indication, it'll be fixed shortly The config reset and logout was deliberate because a large % of customers have zombie screens they can't remove. This won't be happening frequently, but we also needed to test what happens in the wild if we ever need to pull that trigger. Link to comment Share on other sites More sharing options...
jayvee Posted August 25, 2017 Share Posted August 25, 2017 40 minutes ago, cguerra said: I am having the same exact issue all of a sudden, was presented with a signin and now signed in, after failing the first time, but now both boxes are black and not green as it used to be, came to the forums to see if others having an issue. I'm in the same boat. Re-logged in and screens stay black. Win10x64 + MacOS 10.12.6 Link to comment Share on other sites More sharing options...
Guest Andrew Nelless Posted August 25, 2017 Share Posted August 25, 2017 7 minutes ago, jayvee said: I'm in the same boat. Re-logged in and screens stay black. Win10x64 + MacOS 10.12.6 How about now ? Link to comment Share on other sites More sharing options...
cguerra Posted August 25, 2017 Share Posted August 25, 2017 Still dead in the water.... Link to comment Share on other sites More sharing options...
Guest Andrew Nelless Posted August 25, 2017 Share Posted August 25, 2017 Tried messing with the screen layout? Any errors in the log? (press `) You might have to restart the program to green up again Link to comment Share on other sites More sharing options...
cguerra Posted August 25, 2017 Share Posted August 25, 2017 [Core] [2017-08-25T15:19:50] DEBUG: screen "cguerra-lpc" shape changed [ UI ] [2017-08-25T15:19:52] INFO: write configuration file complete [ UI ] [2017-08-25T15:19:52] ERROR: process exited with error code: 62097 [Core] [2017-08-25T15:19:52] INFO: drag and drop enabled [Core] [2017-08-25T15:19:52] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T15:19:52] DEBUG: configuration read successfully [Core] [2017-08-25T15:19:52] DEBUG: screen shape: 0,0 1920x1080 [Core] [2017-08-25T15:19:52] DEBUG: window is 0x00040cd6 [Core] [2017-08-25T15:19:52] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T15:19:52] DEBUG: adopting new buffer [Core] [2017-08-25T15:19:52] DEBUG: opened display [Core] [2017-08-25T15:19:52] DEBUG: active sides: 8 [Core] [2017-08-25T15:19:52] DEBUG: active sides: 8 [Core] [2017-08-25T15:19:52] DEBUG: desk Default window is 0x000a08b4 [Core] [2017-08-25T15:19:52] DEBUG: switched to desk "Default" [Core] [2017-08-25T15:19:52] DEBUG: desktop is now accessible [Core] [2017-08-25T15:19:52] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T15:19:52] NOTE: started server, waiting for clients [Core] [2017-08-25T15:19:52] DEBUG: event queue is ready [Core] [2017-08-25T15:19:52] DEBUG: add pending events to buffer [Core] [2017-08-25T15:19:52] DEBUG: screen "cguerra-lpc" shape changed [ UI ] [2017-08-25T15:19:55] INFO: write configuration file complete [ UI ] [2017-08-25T15:19:55] ERROR: process exited with error code: 62097 [Core] [2017-08-25T15:19:55] INFO: drag and drop enabled [Core] [2017-08-25T15:19:55] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T15:19:55] DEBUG: configuration read successfully [Core] [2017-08-25T15:19:55] DEBUG: screen shape: 0,0 1920x1080 [Core] [2017-08-25T15:19:55] DEBUG: window is 0x00050cca [Core] [2017-08-25T15:19:55] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T15:19:55] DEBUG: adopting new buffer [Core] [2017-08-25T15:19:55] DEBUG: opened display [Core] [2017-08-25T15:19:55] DEBUG: active sides: 0 [Core] [2017-08-25T15:19:55] DEBUG: active sides: 0 [Core] [2017-08-25T15:19:55] DEBUG: desk Default window is 0x00050cd6 [Core] [2017-08-25T15:19:55] DEBUG: switched to desk "Default" [Core] [2017-08-25T15:19:55] DEBUG: desktop is now accessible [Core] [2017-08-25T15:19:55] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T15:19:55] NOTE: started server, waiting for clients [Core] [2017-08-25T15:19:55] DEBUG: event queue is ready [Core] [2017-08-25T15:19:55] DEBUG: add pending events to buffer [Core] [2017-08-25T15:19:55] DEBUG: screen "cguerra-lpc" shape changed [ UI ] [2017-08-25T15:19:58] INFO: write configuration file complete [ UI ] [2017-08-25T15:19:58] ERROR: process exited with error code: 62097 [Core] [2017-08-25T15:19:59] INFO: drag and drop enabled [Core] [2017-08-25T15:19:59] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T15:19:59] DEBUG: configuration read successfully [Core] [2017-08-25T15:19:59] DEBUG: screen shape: 0,0 1920x1080 [Core] [2017-08-25T15:19:59] DEBUG: window is 0x000c08b4 [Core] [2017-08-25T15:19:59] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T15:19:59] DEBUG: adopting new buffer [Core] [2017-08-25T15:19:59] DEBUG: opened display [Core] [2017-08-25T15:19:59] DEBUG: active sides: 8 [Core] [2017-08-25T15:19:59] DEBUG: active sides: 8 [Core] [2017-08-25T15:19:59] DEBUG: desk Default window is 0x00060cca [Core] [2017-08-25T15:19:59] DEBUG: switched to desk "Default" [Core] [2017-08-25T15:19:59] DEBUG: desktop is now accessible [Core] [2017-08-25T15:19:59] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T15:19:59] NOTE: started server, waiting for clients [Core] [2017-08-25T15:19:59] DEBUG: event queue is ready [Core] [2017-08-25T15:19:59] DEBUG: add pending events to buffer [Core] [2017-08-25T15:19:59] DEBUG: screen "cguerra-lpc" shape changed [ UI ] [2017-08-25T15:20:01] INFO: write configuration file complete [ UI ] [2017-08-25T15:20:01] ERROR: process exited with error code: 62097 [Core] [2017-08-25T15:20:01] INFO: drag and drop enabled [Core] [2017-08-25T15:20:01] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T15:20:01] DEBUG: configuration read successfully [Core] [2017-08-25T15:20:01] DEBUG: screen shape: 0,0 1920x1080 [Core] [2017-08-25T15:20:01] DEBUG: window is 0x00070cd6 [Core] [2017-08-25T15:20:01] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T15:20:01] DEBUG: adopting new buffer [Core] [2017-08-25T15:20:01] DEBUG: opened display [Core] [2017-08-25T15:20:01] DEBUG: active sides: 0 [Core] [2017-08-25T15:20:01] DEBUG: active sides: 0 [Core] [2017-08-25T15:20:01] DEBUG: desk Default window is 0x000d08b4 [Core] [2017-08-25T15:20:01] DEBUG: switched to desk "Default" [Core] [2017-08-25T15:20:01] DEBUG: desktop is now accessible [Core] [2017-08-25T15:20:01] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T15:20:01] NOTE: started server, waiting for clients [Core] [2017-08-25T15:20:01] DEBUG: event queue is ready [Core] [2017-08-25T15:20:01] DEBUG: add pending events to buffer [Core] [2017-08-25T15:20:01] DEBUG: screen "cguerra-lpc" shape changed [ UI ] [2017-08-25T15:20:04] INFO: write configuration file complete [ UI ] [2017-08-25T15:20:04] ERROR: process exited with error code: 62097 [Core] [2017-08-25T15:20:04] INFO: drag and drop enabled [Core] [2017-08-25T15:20:04] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T15:20:04] DEBUG: configuration read successfully [Core] [2017-08-25T15:20:04] DEBUG: screen shape: 0,0 1920x1080 [Core] [2017-08-25T15:20:04] DEBUG: window is 0x00080cca [Core] [2017-08-25T15:20:04] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T15:20:04] DEBUG: adopting new buffer [Core] [2017-08-25T15:20:04] DEBUG: opened display [Core] [2017-08-25T15:20:04] DEBUG: active sides: 8 [Core] [2017-08-25T15:20:04] DEBUG: active sides: 8 [Core] [2017-08-25T15:20:04] DEBUG: desk Default window is 0x00080cd6 [Core] [2017-08-25T15:20:04] DEBUG: switched to desk "Default" [Core] [2017-08-25T15:20:05] DEBUG: desktop is now accessible [Core] [2017-08-25T15:20:05] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T15:20:05] NOTE: started server, waiting for clients [Core] [2017-08-25T15:20:05] DEBUG: event queue is ready [Core] [2017-08-25T15:20:05] DEBUG: add pending events to buffer [Core] [2017-08-25T15:20:05] DEBUG: screen "cguerra-lpc" shape changed Link to comment Share on other sites More sharing options...
Guest Andrew Nelless Posted August 25, 2017 Share Posted August 25, 2017 Looks completely normal. Try hitting F12 one machine What's the log like in the other machine ? Link to comment Share on other sites More sharing options...
cguerra Posted August 25, 2017 Share Posted August 25, 2017 Both my machines are still dark within the app on both sides. F12 does nothing, brief green but back to dark. Will have to reply from other machine the log, since I can't cut and paste across machines. Link to comment Share on other sites More sharing options...
cguerra Posted August 25, 2017 Share Posted August 25, 2017 [ UI ] [2017-08-25T15:24:04] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:07] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:07] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:10] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:10] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:13] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:13] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:16] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:16] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:19] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:19] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:22] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:22] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:25] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:25] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:28] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:28] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:31] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:31] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:34] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:34] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:37] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:37] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:40] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:40] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:43] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:43] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:46] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:46] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:49] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:49] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:52] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:52] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:55] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:55] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:24:58] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:24:58] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:01] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:01] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:04] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:04] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:07] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:07] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:10] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:10] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:13] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:13] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:16] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:16] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:19] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:19] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:21] DEBUG: claim to be server [ UI ] [2017-08-25T15:25:21] INFO: write configuration file complete [Core] [2017-08-25T15:25:21] INFO: drag and drop enabled [Core] [2017-08-25T15:25:21] DEBUG: opening configuration "C:/Users/cguerra/AppData/Local/Symless/Synergy/synergy.conf" [Core] [2017-08-25T15:25:21] DEBUG: configuration read successfully [Core] [2017-08-25T15:25:22] DEBUG: screen shape: -1920,0 3840x1080 (multi-monitor) [Core] [2017-08-25T15:25:22] DEBUG: window is 0x00070ab6 [Core] [2017-08-25T15:25:22] DEBUG: using desktop for drop target: C:\Users\cguerra\Desktop [Core] [2017-08-25T15:25:22] DEBUG: adopting new buffer [Core] [2017-08-25T15:25:22] DEBUG: opened display [Core] [2017-08-25T15:25:22] DEBUG: active sides: 10 [Core] [2017-08-25T15:25:22] DEBUG: active sides: 10 [Core] [2017-08-25T15:25:22] DEBUG: desk Default window is 0x000a0be4 [Core] [2017-08-25T15:25:22] DEBUG: switched to desk "Default" [Core] [2017-08-25T15:25:22] DEBUG: desktop is now accessible [Core] [2017-08-25T15:25:22] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [Core] [2017-08-25T15:25:22] NOTE: started server, waiting for clients [Core] [2017-08-25T15:25:22] DEBUG: event queue is ready [Core] [2017-08-25T15:25:22] DEBUG: add pending events to buffer [Core] [2017-08-25T15:25:22] DEBUG: screen "ideapad" shape changed [ UI ] [2017-08-25T15:25:22] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:22] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:25] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:25] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:28] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:28] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:31] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:31] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:34] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:34] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:37] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:37] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:40] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:40] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:43] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:43] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:46] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:46] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:49] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:49] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:52] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:52] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:55] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:55] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:25:58] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:25:58] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:26:01] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:26:01] DEBUG: retry in 3 seconds [ UI ] [2017-08-25T15:26:04] DEBUG: can not find any successful connectivity result for the server screen: 104 [ UI ] [2017-08-25T15:26:04] DEBUG: retry in 3 seconds Link to comment Share on other sites More sharing options...
cguerra Posted August 25, 2017 Share Posted August 25, 2017 My network is up and running and works fine, nothing in my network topology has changed, no firewalls enabled. Link to comment Share on other sites More sharing options...
Benjamin Jacob Posted August 25, 2017 Share Posted August 25, 2017 I have the same issue. Since the relogin issue my Win 10 and Mac clients will not go green. Link to comment Share on other sites More sharing options...
Guest Andrew Nelless Posted August 25, 2017 Share Posted August 25, 2017 What's happening now guys? Link to comment Share on other sites More sharing options...
cguerra Posted August 25, 2017 Share Posted August 25, 2017 Whatever magic u did - don't touch it....IT WORKS...thanks! Link to comment Share on other sites More sharing options...
Benjamin Jacob Posted August 25, 2017 Share Posted August 25, 2017 That worked. My computers switched positions, but easy to fix. Link to comment Share on other sites More sharing options...
jayvee Posted August 25, 2017 Share Posted August 25, 2017 34 minutes ago, Andrew Nelless said: How about now ? I'm up and working now! (Didn't change a thing)... so whatever you did, thanks! Link to comment Share on other sites More sharing options...
tzucker Posted August 28, 2017 Author Share Posted August 28, 2017 I am now getting a connectivity problem. I added a third computer when the first two were working and now the server can't find the other two. If I turn off synergy on the third machine. I just get constant errors while synergy is trying to connect. I sent the logs from the 2 machines. Link to comment Share on other sites More sharing options...
tzucker Posted August 28, 2017 Author Share Posted August 28, 2017 Code snippet from server: [ UI ] [2017-08-28T13:15:40] DEBUG: claim to be server [ UI ] [2017-08-28T13:15:40] DEBUG: can not find any successful connectivity result for the server screen: 381 [ UI ] [2017-08-28T13:15:40] DEBUG: retry in 3 seconds [ UI ] [2017-08-28T13:15:42] DEBUG: can not find any successful connectivity result for the server screen: 381 [ UI ] [2017-08-28T13:15:42] DEBUG: retry in 3 seconds [ UI ] [2017-08-28T13:15:43] DEBUG: can not find any successful connectivity result for the server screen: 29 [ UI ] [2017-08-28T13:15:43] DEBUG: retry in 3 seconds [ UI ] [2017-08-28T13:15:43] DEBUG: can not find any successful connectivity result for the server screen: 381 [ UI ] [2017-08-28T13:15:43] DEBUG: retry in 3 seconds [ UI ] [2017-08-28T13:15:45] DEBUG: can not find any successful connectivity result for the server screen: 381 [ UI ] [2017-08-28T13:15:45] DEBUG: retry in 3 seconds [ UI ] [2017-08-28T13:15:46] DEBUG: can not find any successful connectivity result for the server screen: 29 [ UI ] [2017-08-28T13:15:46] DEBUG: retry in 3 seconds end of snippet I assume that screen 29 is the second machine (since I saw that error previously) and that 381 is the third computer. To confuse things, Machine 1 - server has 2 displays, machine 2 has 2 displays and machine 3 has one display. Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 31, 2017 Synergy Team Share Posted August 31, 2017 On 8/28/2017 at 6:18 PM, tzucker said: I assume that screen 29 is the second machine (since I saw that error previously) and that 381 is the third computer. To confuse things, Machine 1 - server has 2 displays, machine 2 has 2 displays and machine 3 has one display. Looks like a connectivity issue, we'll address this in beta5. Link to comment Share on other sites More sharing options...
nick152 Posted December 1, 2019 Share Posted December 1, 2019 i seem to be having this same problem. i successfully login and when go back to application it asks to sign in again. i recently bought a new computer and trying to get synergy on it... Link to comment Share on other sites More sharing options...
notafurry Posted December 2, 2019 Share Posted December 2, 2019 On 11/30/2019 at 5:17 PM, nick152 said: i seem to be having this same problem. i successfully login and when go back to application it asks to sign in again. i recently bought a new computer and trying to get synergy on it... Logged in to my (existing, working) Linux box; there's a config file, .config/Symless/Synergy.conf. Has five lines, four of which are profileID, screenID, userID (all with numeric values) and userToken (with a long string, possibly a hash value.) Moved over to the new Windows 10 box. Disabled Synergy and shut down the helper. Next, opened RegEdit, searched for Symless and then Synergy, found a registry key with the same four names for key values. I left the screenID set to the default but changed the other three to match the values from the Linux box. Rebooted, opened Synergy, all working normally. Something's b0rked in the registration process, but if you've got one working system it should be possible to find the values you need to get it working. Link to comment Share on other sites More sharing options...
pippin Posted December 6, 2019 Share Posted December 6, 2019 (edited) It's the same error.. please check your sign server https://v1.api.cloud.symless.com/login/with-symless?code=def5020078d659ad1956068487bd8b7a94992e1d3e2c64135217a196496e35a2d0d9977c0e1e46a8652777fdde5cdc4775e76a8e8eb3700c30531ce8b0fc755926b07f9a35f2e0fc1608a338dc41c94543b1a07f275647be7e71a1f06f1adbb66a91a5f3082339378ee4cc492fe7df9fbbf7664fe24a99eb20d8cc730f2fa6aafa8f1b53a491e2928f46a718055f51f420b57be3775044061614b4981d8941c6b421fe6fa20fd0547952d6f996a9d38b4a3eac5cb5abdead8e148e91bda9655e3ae62ebec19e748598cf9822d4cd2efc5b3977a31142c968aaebedca5363f8a8a7f1d007770ddb085d943e06c7e0df5597b8989c73c487484a2a4ba89ad24084089b80a60b3aa5d1044d612e0196d301d745f3bbd277124d0485a9c12869cc255d54ecffa154552160ca1147d1707c39aa705c56af6e66dd4b65bec9fbe103d270d8d983ddb9cbb70486000a140e200289be0e9f43e9db1502f67b19d6d6e360f27b34154e9a57bef6ed0d401e4520591a8a012b0f66bfb6bed19e1ae4&state=2hpAiVg0hxHwcmOzqbvDnHK2 synergy-service.log [ Service ] [2019-12-03T04:55:50] debug: retrying websocket connection now [ Service ] [2019-12-03T04:55:50] debug: connecting websocket: pubsub1.cloud.symless.com:443 [ Service ] [2019-12-03T04:55:51] error: websocket handshake error 3: WebSocket upgrade handshake failed [ Service ] [2019-12-03T04:55:51] error: websocket handshake response 400: Bad Request Edited December 6, 2019 by pippin Link to comment Share on other sites More sharing options...
Fory Posted December 11, 2019 Share Posted December 11, 2019 I am having the same issue with Mac OS. Can you give me the workaround? Link to comment Share on other sites More sharing options...
TonyChong Posted December 13, 2019 Share Posted December 13, 2019 Same Problem on Windows 10, December 2019 nothing around this problem, I already try so many things, copy register from the regedit, configs, ETC, Nothing work, and when it work it has the same name of the secondary PC which where I take the keys, How many day we should wait for fix this problem. I almost crying T_T Link to comment Share on other sites More sharing options...
tzucker Posted December 16, 2019 Author Share Posted December 16, 2019 I have almost given up. I am using TeamViewer instead. Link to comment Share on other sites More sharing options...
Recommended Posts