Immich doesn't allow uploading specific media if it was previously uploaded and deleted from server
It seems that when I delete photos or videos from Immich itself either on the ios app or via the web ui (desktop) and then also from the trash; then there is no way to upload the same media back to that user account.
If I try to upload it back afterwards from the webui then it gets flagged as a duplicate and doesn't permit the upload.
If I click on the icon to in the error window which allows the opening of the original media in a new window then it just opens the usual gallery view when viewing a singular image saying error loading image (which I'd assume as the original is deleted).
Also clicking on the 3 dots and then download queues up a download but it remains at 0% as there is no original media as it was delted.
I remember fiddling around with it within the ios app at the start and the reuploaded media was blacklisted but after clearing the blacklist sometimes it would recognise the media under the backup section of the app and add to the total and remainder numbers but after running there'd be the cloud indicator on the thumbnails but when logging in to immich on my desktop none of the media are there. My guess is that it's being flagged as a duplicate and not actually uploaded similar to the behaviour when trying to upload from the webui from before.
I've had to temporarily create a new user, upload the troublesome media to that user and create a shared album as a temporary solution.
4 Replies
:wave: Hey @Capsized,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.If it’s in the trash it will still be flagged as a duplicate, yes
thx for the response but it's been deleted from the trash as-well so there's no way of restoring the media either
Is immich retaining the hashes or metadata despite deletion and if so is there a way to reset or clear this such that the previously deleted media as treated as new media which doesn't share this problem?
No. It’s probably still in the trash. You can query the database for the hash if you want to dig further