Error loading image on brand new install
Hi, I've just setup a fresh install of Immich using the docker compose, .env and hwaccel file from the documentation. I have tried both with and without hwaccel and get the same issue.
The issue I am having is that every picture I upload show's the "Error loading image" text. I have tried regenerating thumbnails through the job in the admin panel, but that does not do anything. What does work is when I go to an individual picture, click the menu and then hit 'regenerate thumbnail'
In the docker logs I see a multiple errors for job handlers where it is unable to read the properties of 'replaceAll'
Hoping someone has some tips!
Here is the error log
20 Replies
:wave: Hey @mixu1308,
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_01GY0DAKGXDEHE263BCAYEGFJAChecklist
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.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
Hello, can you try remove the hardware accel, then bring the stack down then up again and try regenerating thumbnails?
Unfortunately that doesn't solve it
This is the logs right after I've uploaded 3 images
I've no regenerated the thumbnails in the jobs tab and that seems to work
can you remove this part and restart the stack?
docker compose down && docker compose upI use this for my reverse proxy, but I'll try it without 👍
looks like it creates issues with the server cannot communicate with Redis
You can use it for your proxy @mixu1308 but you need a proper internal network as well
ah yes you're right, that fully solves it
I use this so that in caddy I can address every container by their name, even when they're in different compose files, should I somehow pass the redis ip to the immich server?
I'm not too sure what the proper way of doing this is
usually you don't want to expose all the containers, for example database container is something you don't want to expose out side of the stack
so typically each application will get binded to a port, and you reverse proxy back to the server IP + port for different application
you make a good point, the only issue is that the docker IP's are dynamic from my understanding, so I can't put a container's IP in caddy and expect it not to change
or do you mean I should have caddy route the host's IP + binded port?
I think you have a misunderstanding here. For example your server is at 192.168.1.15
so on the server, you run multiple docker application
let's say immich and paperngx
immich is binded to port 2283, so you can access the app at http://192.168.1.15:2283
and paperngx is binded to port 8008, so you can access the app at http://192.168.1.15:8008
the server IP should be static so it will always be 192.168.1.15
you would reverse proxy
immich.domain.com back to http://192.168.1.15:2283/ and paperngx.domain.com back to http://192.168.1.15:8008ah ok, yeah I've been using caddy to reverse proxy to each container's own IP using the docker DNS resolution
I'll do it the way you recommend
Got cha, exposing all containers will cause conflict
because different application might use Redis as well and use the same defualt port
Thank you very much for you time and your help!
Really appreciate it!
No problem! Enjoy!
I was able to fix it as well by doing
REDIS_HOSTNAME=immich_redisGreat!