• Content Count

  • Joined

  • Last visited

About sklus

  • Rank
    New User
  1. @Alex J thanks for your comment - I'll check out the site you quoted. @RomanZ thanks for the additional info. Unfortunately, I cannot access the config guide in the help center. It says I am not authorized to access that page. Regards, Sebastian
  2. Maybe this helps: This is what I figured out by myself so far. Any feedback or comments are appreciated. Regards, Sebastian
  3. Good afternoon everybody, I did not get it work through the repositories either, but however I managed it the following way: First some background info - I am running: Raspberry Pi (1) B+ Raspbian Jessie The steps I followed, gathered from different sites, in case it helps someone: I downloaded the latest version from the Resilio download page: wget Untar it into a directory of your choice mkdir btsync mv resilio-sync_arm.tar.gz btsync/ cd btsync tar -xvf resilio-sync_arm.tar.gz Execute the extracted file, enabling at the same time the web interface: sudo ./rslsync --webui.listen With this, I was able to access the Sync on the RPi via browser and its IP address ( or any other IP you assigned to your RPi). Now, I would appreciate, if anyone could provide me with some manuals or FAQ for this package. The main FAQ is based on package installation for Debian, but for the time being, this is not helping me. I would like to configure a storage path, restrict the IP access (if possible), etc. Any help is appreciated. Regards, Sebastian
  4. Hello @Helen, before trying to follow your latest instructions, just to comment on @brokenby2703 's latest post: I am having exactly the same problem, and exactly the same error messages. Checking your first step before executing it, my "" is currently linked to "/lib/". And "" is linked to "/lib/arm-linux-gnueabihf/". So if I executed your link, I would be replacing at least partially the existing links. And I suppost I should expect some consequences, right? Not sure if I should just do it Regards, Sebastian P.S.: I am also following core dump failure in raspberry pi - seems like it is related.