• Content Count

  • Joined

  • Last visited

  • Days Won


About jdrch

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    Quad Cities
  • Interests

Recent Profile Visitors

567 profile views
  1. Is this the reason Sync keeps crashing on my 19.04 PC? Also, any idea when this fix will be added to the repository build?
  2. Odd problem I've been having on my Note9 running Android 8.1 for a while now: Sync will often say it's connected to all the peers for all its folders, and even be responsive to touch input, BUT no syncing actually occurs. The only solution I've found so far is to kill the app, clear the cache, and restart it. None of my other Android devices have this issue, and yes, it happens even with battery optimization disabled for Sync. Any ideas?
  3. I bigger question is when Synology will issue proper speculative execution vulnerability patches but I digress ...
  4. I always just download the Windows build directly from the forum link and go from there. I suspect the reason it installs in that way is to allow access to the folders of other (non-admin) users so it can sync them too. Personally I run Sync as a service (protected by a pretty strong password) which avoids the permissions problem (my antivirus as the same privileges so running as SYSTEM doesn't bother me.)
  5. NAS has never been a use case for me. And for that I always thought it was accessed by opening the NAS' desktop UI and then launching Sync from there.
  6. I didn't mean it's a security risk. It's actually convenient because it means you can admin Sync from any device on the same LAN, which is neat. Plenty of other apps allow this: Pi-hole, UniFi Controller; your router, modem, and AP, etc.
  7. A couple things seem to be amiss with the Installing Sync Package on Linux documentation. 1a) Under the For arm64 architecture heading sudo dpkg --add-architecture armhf Why would users have to add armhf to dpkg if they're on arm64 AND an arm64 package exists? 1b) I'm pretty sure the instruction: is wrong and should be: for the same reason as 1a). The commands as written in the documentation tell users to force apt to install packages their system literally doesn't support. Installing an armhf package without the associated dependencies and environment configuration will result in errors and Sync quite literally failing to run. 2) I'm not sure about the Raspberry Pi 1, but the Raspberry Pi 3 Model B+ is an armhf device, which means none of the current commands specific to the Raspberry Pi 1 apply, and all of the current commands for arm64 apply. In other words, the instructions should be: Hope the above gets updated and this helps anyone else who might be confused.
  8. You're right. The reason was actually something very stupid on my end: I had originally installed from the repository and then updated via a standalone package. I think this created a separate Sync instance with a default configuration. Also, this was on Linux on DeX on my Snapdragon Note9, which may have added another wrinkle to things. The interesting thing about this is apparently doing the reverse (installing from the .deb and then adding the repository) on armhf (Raspberry Pi 3 Model B+) doesn't result in duplicate installations. Running sudo apt-get update after adding the repository does in fact check the repository, but does not return an update.
  9. I think that might have been it! It was definitely rslsync in the previous version.
  10. Not sure why I never thought of this before, but I don't recall seeing anyone else talk about it, or reading it in the documentation. Additionally, a Google search turned up nothing. You can access Sync's Web UI running on any machine on your LAN by entering ThatMachinesIPaddress:8888/gui. As a corollary to this: if you use Sync as a service do set a UI password, otherwise you run the risk of giving anyone (including malicious apps) access to your config and files, which is really bad.
  11. Which build platform is this? I tried updating on Ubuntu ARM64 last night and although the installation completed, it blew away my config. Might this be related?
  12. PSA for those who're trying to update using the .deb and .rpm files: the official download links haven't been updated yet. Find your download URL using the following format: https://download-cdn.resilio.com/MajorVersionNumber/Debian/resilio-sync_MajorVersionumber-Revision_Platform.deb So, for example, for armhf, the URL would be: https://download-cdn.resilio.com/2.6.2/Debian/resilio-sync_2.6.2-1_armhf.deb Hope this helps everyone.
  13. End goal: enable Sync to start under my account on macOS bootup even when no users are logged in. I assume the process to make this happen is to follow these official instructions for doing so with a Sync running under a separate resiliosync user account and change all instances of "resiliosync" in the instructions to my username instead. And yes, I'm aware of the permissions limitations of running Sync under my account only; but I'm not concerned about them as my account will be the only one on that Mac anyway. Is that how to do it?
  14. UPDATE: Instructions here https://help.resilio.com/hc/en-us/articles/207293730-Launching-Sync-on-Mac-without-user-logged-in Might be getting my 1st Mac via a Mac Mini. I'd like to run Resilio Sync on it, and it would be nice if I could configure Sync to run on device startup as it does on my Windows PCs (where it runs as a service) so Sync always works regardless of whether I'm logged in. Is that possible in macOS?
  15. @thinkmac I've literally never had a Sync installation (note the emphasis) issue, so I'm really out of my depth here. Per a quick Google search, try running the installer as administrator.