Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Leaderboard

  1. Nick Bolton

    Nick Bolton

    Synergy Team


    • Points

      2

    • Content Count

      2460


  2. GranPaSmurf

    GranPaSmurf

    Volunteer Moderators


    • Points

      1

    • Content Count

      780


  3. quad_bx

    quad_bx

    Synergy User


    • Points

      1

    • Content Count

      27


  4. Naidu

    Naidu

    Synergy User


    • Points

      1

    • Content Count

      28


Popular Content

Showing content with the highest reputation on 10/06/17 in all areas

  1. This applies to Synergy 1 and Synergy 2 users. Alongside any other troubleshooting guides or examples that Symless gives you, please follow these troubleshooting steps as they'll save time for the community members and help give those members a foundation in order to help you. 1.) Restart Synergy - I can't tell you how many times a simple restart of the Synergy process will help. If it's Synergy 2, end it through Task Manager or Activity Monitor (on macOS). On Linux, the different distros may make the termination process different (plus, I haven't used Linux in years and don't plan t
    1 point
  2. Beta3 worked just fine behind my corporate firewall, but now that I've updated to beta4 I can't get my computers to connect. Are we going to need a firewall rule for synergy 2.0 to work? If a firewall rule is going to be required, my company will not allow a blanket exe firewall rule. What are the specific ports and hostnames that need to be open for synergy 2.0 to work? My log file is linked below. https://synergy-logs.symless.com/2017-09-14/75-2017-09-14T09-23-27.log
    1 point
  3. to stop the restart on linux close it like any other application. if you have the service open in a terminal(using the terminal to manually start it) press ctrl-c, this will close the service. if you have a modified(working) service then restart it using the terminal: systemctl restart synergy
    1 point
  4. Tara, please forgive the delay. I only saw it by running through a bunch of old listings...no excuse. Yes, this beta 4 is likely to be unusable for your setup right now. Beta 4 hates all Linux distros and has only a distant cousin relationship with most MAC machines. But some of the more savvy users have managed to make it work. A few of us have stepped back to version 1 to have Synergy working on our Linux box and are watching for beta 5 which we've been assured is going to work on Linux systems. As to the sparsity of information or adjustments on beta 4, that's more or less the directio
    1 point
  5. Very true. Actually, I can forsee Synergy 1 being available for quite some time. Our objective is to get most of the Synergy 1 users over to Synergy 2 before we discontinue it. I'd hate to abandon Synergy users unnecessarily.
    1 point
  6. Yeah, beta4 was a train wreck. We'll do better with beta5. Thanks for your patience!
    1 point
  7. Yeh, I have the same issue. What are the specific port that needs to open?
    1 point
  8. Hi, No worries, most of us know what beta means. And we tipped you a coffee(because 5$ can't really be called a purchase) to help you speed things up with the development cycle and maybe a small fuzzy feeling that people appreciate your work. However, you should take our feedback more seriously, because final customers, that will pay $25-$50 for the product, will be drastically more demanding. Personally, I already don't like the way things are headed: - lack of connectivity via Synergy when Symless Cloud is down, even if my machines are on the same network; - the impossibility to ha
    1 point
×
×
  • Create New...