Search the Community

Showing results for tags 'https'.

The search index is currently processing. Current results may not be complete.
  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. On Ubuntu Server 16.04.1 LTS (Xenial Xerus) I've installed Resilio Sync and started by: systemctl enable resilio-sync adjusted the /etc/resilio-sync/config.json file: { "listening_port" : 0, "storage_path" : "/var/lib/resilio-sync/", "pid_file" : "/var/run/resilio-sync/", "agree_to_EULA": "yes", "webui" : { "listen" : "", "login" : "xxx", "password_hash" : "xxx" } } restarted the service, and everything works fine, on URL http://196.168.666.666:999/gui. Next, I'm creating a certificate in /etc/resilio-sync/ folder: openssl req -x509 -nodes -days 9999 -newkey rsa:2048 -keyout sync.key -out sync.crt and updating config.json: { "listening_port" : 0, "storage_path" : "/var/lib/resilio-sync/", "pid_file" : "/var/run/resilio-sync/", "agree_to_EULA": "yes", "webui" : { "listen" : "", "login" : "xxx", "password_hash" : "xxx" ,"force_https" : true ,"ssl_certificate" : "/etc/resilio-sync/sync.crt" ,"ssl_private_key" : "/etc/resilio-sync/sync.key" } } Unfortunately, now when I access https://196.168.666.666:999/gui the connection fails. Any idea what may be wrong?
  2. I works behind proxy that allow connect only to 80 (http) and 443 (https) ports. I see that does not contain any tracker or relay with http (80) or https (443) ports. How can I connect to my shares at work with such proxy?
  3. Hi, I am running Sync on a NAS and on a Linux server. I would like to use a valid SSL certificate on both instances. Both systems have automated certificate renewal facilities, but of course they do not know anything about my running Sync instances and the certificate is owned by root in a different folder. First I thought, it might be a good idea to change certificate rights and to point sync.conf to the certificate - but this would yield a security issue. The next idea is to make a copy of the certificate into the folder, where the sync executable resides and to change the ownership. This can be done with a daily cron job. I presume that there is no option to get hold of the "original" certificate without having a security issue and that there is no clever built-in Let's Encrypt functionality in Sync? Any other suggestions?