Sync Does Not Have Permission To Access This Folder

[geransmith]

Snip from (my thread in the BTSync forums)[http://forum.bittorrent.com/topic/34641-sync-does-not-have-permission-to-access-this-folder/]:

I recently upgraded from 1.4 to 2.0 on my Debian server box. When attempting to recreate my 1.4 sync folder in 2.0, I am getting the error "Sync does not have permission to access this folder".

I double checked, and Sync does have permission for this folder. The daemon is running as the same user it was in 1.4. If I make a 1.4 style sync folder, it appears to have no issue reading the data and no error is thrown.

Unfortunately this is my "target" box for some one way syncing from a remote host, so I need to be able to add the key from my remote server. Even using the 1.4 style key, it throws permission errors.

After some troubleshooting with the btsync support team, we determined it was due to the "directory_root" property that is found in the debconf-default.conf file in the webui section. Removing this property fixed this error.

Here is what the support team said in regards to this property:

Check please your config. Most likely you'll find there "directory_root" (or "dir_whitelist") parameter.
This parameters specify the locations where Sync can create folders. Try to remove these parameters.

By the way, this is not and official repository and as I understand the repository maintainer included
this parameter in the default config.

[geransmith]

Another potential fix is to add this to the reconfigure options and specify what it is for. Maybe like, "Add the following folder(s) to the directory whitelist"

[bbrdaric]

Thanks @tehspaceg, I lost a few hours on that :(

[GregorioDiStefano]

Same here! This should be changed

[AleMunin]

Okay, I spent the last 2 hours trying to solve this problem on my linux mint and it went to the point of me unburying my github account.

This problem is still an issue and the suggested options didn't work or at least weren't very intuitive to a linux newbie like me.

I still didn't fix it, but would like to add that config.json and user_config.json do not have directory_root or the whitelist on its own anymore.

Edit: Okay, it just took me two more hours of trying several methods and none working, but here is what done it. Defaults will always go nuts due to permissions. What you can do, however, is go and change a folder's permission, things as root on the terminal.
Go to the folder.

Open properties, and change both owner and group to rslsync (why didn't you guys just name it resilio?). Or, if you prefer, open the folder in the terminal and go:

sudo chown -R rslsync $(pwd)

Ask people more experienced than me how do you print it when there are spaces on the name of the folder.

Oh, right, one of the reasons why it took me an hour of trying and searching blindly about permissions, is that apparently if you have an nfts folder, you can't chmod or chown. Interestingly enough I didn't get any error messages from it. Will go learn how to deal with that that next.

As a last thing, and I feel like it really should be visible, but then again it must have been obvious for people that are more experienced. It is that any changes you do you need to restart resilio.

service resilio-sync restart

Sounds dumb but a lot of the information on what code to use for both usernames and services are still under the bit torrent sync name and you don't find many guidelines on this, so I figured at least one person passing by here would need to know that before having a hard time hunting it down like I did.

The software is amazing, if the developer is seeing that I just would like to suggest some more guidelines on the install. And give more specific error messages, the permission thing led me a lot into android/mac problems that led me to several dead ends.

[asheroto]

Looks like this issue is still a thing in 2024...