-
[Plugin] Simple Custom WebUI CSS Plugin for Unraid 7.2+
Hey @Victor90 been running this one daily for a while now and it's beautiful. But I am wondering is there a way to fix the GPU plugin icons? As it's the only real missing piece for the dashboard.
-
[Plugin] Appdata Cleanup Plus
The old version was a much better no frills plugin....
-
[Plugin] Appdata Cleanup Plus
-
SMB permission issue only on newly created Lidarr folders
One more question that i've noticed. For deleted Lidarr folders they get deleted via the recycling bin option to another directory which are kept there for 7 days. These have no write permissions and I am unable to delete them manually. The folders Lidarr are creating are functioning as normal, but the ones being deleted to another path have no permissions. I do not see anything in Lidarr specifically regarding read/write permissions for deleted folders.
-
[Support] binhex - SABnzbd
Clicking the purge history button then clicking purge completed does nothing. Nothing in that purge history dialog box functions. I need to click Multi-operations then select all then delete them that way. This stopped working a few months ago. Is there a fix or just a bug with the latest container update?
-
SMB permission issue only on newly created Lidarr folders
Ha. Yeah i just did it again saved changes got a new artist created via Lidarr and permissions are ok now. I never needed to change this setting in the past. I wonder why it's required now all of a sudden?
-
SMB permission issue only on newly created Lidarr folders
Would I add this as a variable in the container template?
-
SMB permission issue only on newly created Lidarr folders
Interesting! I might try and go back to an older linuxserver lidarr version and see if this fixes it.
-
SMB permission issue only on newly created Lidarr folders
Ok i ran this. As i ran new permissions everything was shown as drwxrwxrwx which is correct. I then added a new artist via Lidarr re-ran the command for the artist directory and that newly created folder shows drwxr-xr-x
-
SMB permission issue only on newly created Lidarr folders
Here are my diagnostic logs. areslab-diagnostics-20260107-2141.zip
-
SMB permission issue only on newly created Lidarr folders
Here are my SMB settings in unraid. Nothing I do allows write permissions on newly created folders from Lidarr.
-
SMB permission issue only on newly created Lidarr folders
I did try this option, unfortunately it still gave me 'You do not have permission to perform this action' when accessing it via SMB. I can obviously edit/delete the folder and it's contents via Krusader/Terminal. I am just not able to via Windows. All of my other shares are fine. It's just whatever Lidarr creates I no longer have write permissions until I run New Permissions. Then obviously once a new folder/files are created by Lidarr I run into the same problem. It only just started maybe a week or so ago. Only noticed it by accident as I went to edit some music files manually which I do sometimes.
-
SMB permission issue only on newly created Lidarr folders
Sure thing here you go. Command execution docker run -d --name='lidarr' --net='darknight' --ip='172.18.0.7' --pids-limit 2048 -e TZ="Australia/Brisbane" -e HOST_OS="Unraid" -e HOST_HOSTNAME="AresLab" -e HOST_CONTAINERNAME="lidarr" -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8686]/system/status' -l net.unraid.docker.icon='' -p '8686:8686/tcp' -v '/mnt/user/data/':'/data':'rw' -v '/mnt/user/appdata/lidarr':'/config':'rw' 'lscr.io/linuxserver/lidarr:nightly' 9633f52520ef551fae03c47ca4c7303a8276b418659fa7600031b62936b635db The command finished successfully!
-
SMB permission issue only on newly created Lidarr folders
Yes downloaders are the same across all the AARs. Deluge and SABnzb are the only two clients I use.
-
SMB permission issue only on newly created Lidarr folders
Hey guys, I’ve been running the linuxserver/lidarr container on Unraid for a long time with no problems. Over the last week or two, any new artist folders that Lidarr creates under /media/data/music/artists end up with incorrect permissions. Because of this, I can’t write to, edit, or delete those folders/files via SMB — I get permission denied errors. Just to list the issues Only affects folders created by Lidarr. Older artist folders work fine Sonarr/Radarr using similar paths are unaffected No Unraid, SMB, or Docker permission changes were made the issue appeared suddenly, so I’m wondering if a recent Lidarr/container update changed something (UMASK-related?) For now I have to manually fix permissions after folders are created, which will obviously allow me to edit/delete etc etc. Any ideas what could be causing this or what I should check? I'm kind of at my wits end trying stuff so thought I'd reach out today. I am starting to think its an SMB setting? No other directory is affected, it's just folders created by Lidarr. If i run new safe permissions I can then obviously edit/delete those files from Windows file explorer. If you guys need logs please let me know which you need and I will upload them.