11 Replies
Immich
Immich•4w ago
:wave: Hey @yesnt, 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.
shenlong-tanwen
shenlong-tanwen•4w ago
Do you have a lot of assets on the device?
yesnt
yesntOP•4w ago
About 4.5k, do I need to rehash them?
shenlong-tanwen
shenlong-tanwen•4w ago
If not, we can fix this by resetting the DB which would rehash them 😅 Although, this issue is not exactly related to local assets
yesnt
yesntOP•4w ago
I'll reset the db later. What do you mean by this?
shenlong-tanwen
shenlong-tanwen•4w ago
The issue is not related to local assets, but resetting the DB would lose all the hash information of your local assets on the device and the app would rehash them
Alex Tran
Alex Tran•4w ago
this is Android so rehash should be fast
yesnt
yesntOP•4w ago
What could've caused this issue with the hashes? Or would I need logs of the exact moment it broke to find out?
Alex Tran
Alex Tran•4w ago
this is the issue with probably moving between version of the non-beta > beta local database migration issue it looks like
shenlong-tanwen
shenlong-tanwen•4w ago
@yesnt Did the reset fix the issue you've been facing?
yesnt
yesntOP•4w ago
My bad, I got busy. Yes, no assets remaining and no errors in logs

Did you find this page helpful?