Search the Community
Showing results for tags 'permission'.
Found 3 results
Good day together i am very happy about ember and try to set it up on raspbian currently, after it worked fine in windows. my problem is the permissions of the folder structure though. My noticed bug: My folder structure for the movies is /media/pi/Mainstoragedrive/emby/movies/dvd/ If I want to add the folder in Emby. This folder is on my external drive. I can click through to "pi" and then the dropdown menu always closes. It is also not possible to add manually "The path could not be found. Please ensure the path is valid and try again. I am very helpless about rights. Question 1: Do I only have to specify the destination folder with user "emby" or the whole path? Question 2: Which rights/groups are necessary? Question 3: Why is it not possible? My rights look like this. Folder then right. pi drwxr-x---+ 3 root root (what does "+" mean? I can't find anything on the internet Mainstoragedrive drwxr-xr-x 4 pi root emby drwxr-xr-x 6 pi root movies drwxr-xr-x 4 pi pi dvd drw-rw---- 55 pi pi I hope that someone can help me so that I can go to bed smarter. Have a nice weekend.
Hi All I believe that this has got something to do with permissions as i accidently changed the ownership of files in the /etc /bin /lib directory's to a non root user. ive changed it all back but probably set root over what eas supposed to be emby in some places. can someone tell me what the permissions are supposed to be based on a standard install with the user:group emby:emby i no longer have icons next to my menu items see image attached my log is thowing copious errors listing "MediaBrowser.Controller.Net.SecurityException: Access token is invalid or expired." latest log here https://paste.ubuntu.com/24025043/ can someone give me a list of what their ownerships are for all emby related files, or advise otherwise ps. i have fully removed and reinstalled the server using apt --purge autoremove emby-server regards Troy
I have an idea for a feature request for sync that only makes sense. When syncing by default, you see all devices you are allowed access to. This means when user A goes to sync media, he is prompted to sync to devices that may be user A's , B's, C's, and D's. Of course you can limit their device access, but this requires a lot of work when new devices are added all the time. An elegant solution to this might be to add another metadata tag to devices to hold users that have connected to them before. Then when going to sync content, only showing devices you have logged into before by default, and having an option to show all devices you have permission to sync to.