- Synology cloud station drive folder permissions mac os#
- Synology cloud station drive folder permissions update#
- Synology cloud station drive folder permissions manual#
- Synology cloud station drive folder permissions password#
I went for btsync becuse it seems to be the best solution, the developpers deserve encouragement, it's light and independent and etc, but the manual is really bad, first syncing has to be done with a lot of care and problem apears by magic. I don't want to start over from scratch with the syno, re-instal the dsm and copy again my damn 800Go of datas I go back to btsync gui on the syno but no change, even after rebooting btsync I go to the volume where my shared folder is and I type
Synology cloud station drive folder permissions password#
Then entered my admin password to login as root and not admin (i read this is waht should be done on syno) I logged in in ssh with the following arguments i activated nfs file sharing and gave permission ta the client with the IP of the syno I gave read/write to the group my useb belongs from However i can still read/write the shared folder through the syno web gui, FTP and a file explorer on win (connect to a network drive) and mac (afp://) The btsync gui on the syno says "don't have permission."ītsync on the mac say "added" or "updated" when it send a file (wich actually doens't goes) Then problem start by their own, i know that's weired. With the same login/pass I coud read/write the shared folder through the syno web gui, FTP and a file explorer on win (connect to a network drive) and mac (afp://)
The user has read/write right over the shared folderįrom the mac i could sync toward the syno 100% sure Only one user of the syno use btsync, indeed My syno is configured manually, no use of EZ assistant etc. auto redirect http connection toward https Sorry can't find the english version but say: I followed this tutorial for security on internet I have only one user on the syno, and it has admin priviledges (and it it not the admin user of the system) I think I got you at first, but avoided a long message Please help, its getting on my nerve and if I don't find a relyable and enduring solution, I'll move back to at the end of the day more finished solution, cloudstation. Or if there is a trick related to the functioning of bt sync I also wonder if the problem could come from my fire wallĪnyway all this is un-understandable for me as it worked the day before and no settings change were done I wonder things like how can i create a group of user and user for btsync and giving it the right to read and write in my sync folders However now, maybe 24-48hours after the non-update update, the problem rise again.
Synology cloud station drive folder permissions update#
When I saw you released an update recently, I tried to do the update manually (on the synology), following the same tutorial mentionnend above, but it stays on 1.1.48 and say it's up to date.Īctually, the last non-update update solved the problem of permission I had. So how a hell btsync can say he don't have the rights, especially when it was working perfectly the day before. I actually don't like it but I can live with it for few days.
Synology cloud station drive folder permissions mac os#
I check in Mac os what were the permission for the folder and it is in read and write for everyone in the gui (which should mean chmod 777) However now, sync do not occur anymore and in the btsyn gui of the syno it says "don't have permission to write in selected folder" and this for all the synced folders. I then installed btsync on bot my mac and my pc and had a try, everything seemed to work as I feel (even if some few advanced features would be welcomed)įor a while, the bi-directional sync was working smoothly between the mac and the syno. As the repo did not had the laste version I upgradre manually btsync following the instruction on this post : I've recentely installed btsyns on my synology ds712+ using the syno community repo. I'm still new regarding btsync and synology and my skill in "network" and "shell" are limited but not null
0 kommentar(er)
