eltopo

Members
  • Posts

    191
  • Joined

  • Last visited

  • Days Won

    2

Recent Profile Visitors

1,445 profile views

eltopo's Achievements

Advanced Member

Advanced Member (3/3)

  1. Resilio Sync 3 for Windows only supports 64-bit systems (of Windows 7 and later), so if your Windows 10 is 64-bit you'll be able to install/upgrade to 3.0, if your Windows 10 is 32-bit you have to stay with 2.8. I have an older Raspberry Pi (32-bit) still running Resilio Sync 2.8, it seems working with other 3.0 clients without issues.
  2. Except you need license for 2.x clients to use Pro features, otherwise 2.8 clients synchronize data with 3.0 ones just fine. I hope RSL stays this way for a while, since 32-bit devices just can't upgrade to 3.0.
  3. RSL itself could be improved by displaying some human readable message and solution, like "Your license key file is corrupt or invalid. Please download again. (error SE_INVALID_PARAMETER)", instead of just "SE_INVALID_PARAMETER", which might be good enough for software developers but not great for normal users. It also helps to avoid corrupt files with a zip file for delivering license.
  4. It would be much easier for you to use DSM7's reverse proxy to handle https:// protocol while RSL is running http only mode: 1. set up a domain name, e.g., myrsl.myname.com, for your DSM/RSL and let DSM get/renew LE certificate for that domain name; 2. set up a reverse proxy rule: https://myrsl.myname.com --> http://localhost:8888 (RSL's port)
  5. Check the log (using systemctl status / journalctl) and find out the reason why resilio sync service failed to start. If you are using USB device(s) as resilio sync's storage, you may need to wait the drive(s) get fully mounted before starting the service. If you are sure that after 1 minute the service can be started successfully, you can use a systemd timer unit for resilio sync's service with OnBootSec=60 see: systemd.timer By the way, executing "systemctl start" as a cron job is NOT the right place to properly start a systemd service.
  6. Default folder location: the default folder for shared folders File download location: the default folder for shared single files (see Sharing single file – Resilio Sync)
  7. Don't do this. Not only you changed everything to be executable (when most of them are not supposed to be), but also you gave every user in your system permissions to access everyone else's files. It's also very hard to recover your system back to its original state if you issued chmod -R fixed_number Learn to use chmod -R a+rw, chmod -R og-w instead. Just use your user (i.e., login: echo $(whoami)) to run RSL, and all files RSL creates/updates will be owned by that user. If you use systemd to manage RSL, change User=/Group= lines in its service file; Or simply write a bash script to start RSL then run it as your user.
  8. Yes, Resilio Sync sends broadcast to find peers in LAN by default. Make sure your device's firewall does not block multicast packets.
  9. Looks like all 32bit NASes are deprecated and have to stay with 2.x, from 3.0 change log: Resilio Sync 3.0 change log – Sync
  10. @Helen Thanks for your reply.
  11. The article is quite misleading to current users. I have several questions regarding Resilio Sync 3.0: 1. Do current Sync 2.x Pro users get Resilo Sync 3.0 Pro with old licenses, or our licenses simply expire / become obsolete, and everybody should get the new "free license" for the now free "Resilio Sync 3.0"? 2. Is the new "free license" a trial, or it's perpetual? 3. Will there be Resilio Sync 3.0 Free and (paid) Pro, or just one free edition Resilio sync 3.0? 4. Are Sync for Desktop apps only available for 64-bit platforms? if this is true, it practically retires lots of embedded Linux devices.
  12. It's year 2024, and you should use reverse proxy to deal with https, instead of mucking around with your web server (rsl in your case). caddy also automatically renews your Let's encrypt certificates. Since you are trying to use Let's Encrypt, caddy on your Linux server is the easiest way to go. Let caddy handle all https access + certificate management, while your rslsync just runs local-http only. If you can run caddy on your NAS, do it too. If you can't, then just use your Linux server to redirect access to your NAS. via secure tunnel.
  13. chmod 777 is almost never a good solution, you might not fully fix your current permission problems, and you would introduce more security issues. Use ps -ef to find out which user is running rslsync, then sudo chown -R <theuser:thegroup> to the problematic folders, and restart rslsync.
  14. Sounds like you might want to check unison for your cases, I think it's a better solution than Resiio Sync. With Resilio Sync Pro, you can sync with a local folder (including a mounted usb external drive): Sharing a folder locally – Sync (resilio.com) I didn't use this feature so I don't know if you need to pause syncing before dismounting usb external drives.
  15. Android clients are set to turn on "Selective sync" for folders by default, unless you turn it off to synchronize certain folders or turn on "Keep synced" for files. Check your folders/files' info (tap on the ⓘ button).