Unable to delete files from trash
I recently migrated from an Ubuntu server to a TrueNAS system.
Everything appeared to be working fine at first, but I’ve noticed that I’m now unable to delete any files.
When I try deleting files from the web UI, I get the following error:
When attempting the same action from the mobile app, the deletion seems to succeed, but the assets still appear in the web UI afterward.
I’ve also attached the dataset ACL for reference.
29 Replies
:wave: Hey @Rafael Alexandre,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:I also tried a completely new install, to see if something got broken when switching systems, but the behavior persisted.
How are you connecting to immich?
Are you able to upload and delete new assets?
How did you apply the acl also? Did you apply it recursively? Or created the datasets then copied the data over?
I'm able to upload new assets and trash them. But when trying to remove from trash I get this error.
The data was copied first and the ACL was applied later recursively.
As Zeus asked, how are you connecting to Immich?
Sorry, I didn't quite get the question.
I'm running on a local machine and accessing through reverse proxy.
Tested on incognito without reverse proxy as requested and the behavior is still the same:
What browser are you using? And how does the picture reapear? When you refresh the page?
I just tried on my system and have the error too but it seem a bit different
Because the asset seem to be trashed (on my system)
Running some additional tests I noticed that the "Restore" button is not working as well.
The picture is only reappearing if I delete from the mobile device.
I did a test deleting from the Webui and had the same results as you. I can see it being removed from the file system.
But my main concern here was with the error on the web ui. If it is something that I did wrong on my migration from ubuntu to truenas.
No I don't think so, I have the same issue.
I'm also using TrueNAS, but installed the app through their catalog, so I'm not fully sure if that is TrueNAS related or a more "general" immich issue
Although restoring using the webUI works for me
To me restore is only working from the mobile app. 🤔
I’m less concerned now that I know the asset is actually being removed from the filesystem.
My main concern was just making sure the space gets freed up.
I haven't found any related issue on git, should I open one or having it open here is enough?
#23818
Seem to have been addressed?
https://github.com/immich-app/immich/pull/23594
[Pull Request] fix(web): "select all" button in trash and permanently deleted count (immich-app/immich#23594)
Should be in the next release (for the delete part)
That's cool! Thanks for the support 😄
I'll close this ticket
Well
Maybe for the restore part it's a different problem
I'm not fully certain, but it works on my system, so I wonder what is "wrong" on yours
It seems pretty similar to #23818
I'll wait for next release and if the behavior persists I can reopen here.
Yes that look the same, but you say that in your case it doesn't restore?
Or if you refresh the web page it is actually restored?
If the latter then you can close the ticket as it'll be fixed
Just tested, it restored the file, I just had to refresh the page
Thank you all for the support 😄
No problem!
This thread has been closed. To re-open, use the button below.
Btw
As you have the apps acl set on TrueNAS, you could run Immich as the apps user (568)
It currently run as root, which is fine, but it's just so you know
Thanks for the info. I'm still trying to understand how the acl works on truenas.
I'll probably tweak the values in the next days
I don't have a video guide that explains them that well, but the full name is Access Control List, so it is basically a list that specify who can do what on the dataset content
There is a default user/group owner, that you can choose which access they have (for your case these are root)
And you can add other users/groups to extend the access
That's huge simplification though, but for basic use it's "enough"