tomspark wrote:
That 403 is almost always FileBrowser's own per-user permission setting, not anything actually broken. By default a freshly-added FileBrowser user can browse and download but isn't allowed to delete. Quick fix: log in as the admin account, go to Settings - User Management, click the user you're signed in as, and tick 'Delete' (and 'Modify' while you're there) in its permissions list, then Save. Try the delete again and it should go through. If you're already the admin and Delete is already enabled, then it's a file-ownership thing instead — the files were created by another part of SparkBox under a different owner, so FileBrowser can't remove them. If that's the case, just say so and I'll give you a one-line fix. Which one is it?
tomspark wrote:
Then it's the file-ownership one — those files were created by the download apps under a different owner than FileBrowser runs as, so FileBrowser isn't allowed to remove them. This hands them to the right owner (and won't affect anything else, since all the apps share the same user). One line over SSH: sudo chown -R 1000:1000 "$(grep -E '^MEDIAROOT=' /opt/sparkbox/.env | cut -d= -f2-)" That re-owns your media/downloads folder to the user FileBrowser runs as. Give it a few seconds, then try the delete again — it'll go through. (If it prints an error about an empty path, tell me and I'll grab your exact folder location.) And thanks — glad the quick replies help!