9 Replies
:wave: Hey @Warwolf,
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.Docker Documentation
Post-installation steps
Find the recommended Docker Engine post-installation steps for Linux users, including how to run Docker as a non-root user and more.
A group exists and the user is part of the group
What OS is this and are you using non root docker?
I am having the same issue.
As Warwolf posted, I have tried to upgrade immich - and have even used 'docker image prune' before trying -
unable to get image 'docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52': permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/images/docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52/json": dial unix /var/run/docker.sock: connect: permission denied
___
I ran this all with
sudo docker compose pull && docker compose up -d
I am a little confused at how and WHERE to update Authelia config:
token_endpoint_auth_method: "client_secret_post"
I have used the 1.132.1 docker-compose.yml and 1.132.2 - I did not do anything to the .env file as I have never had to - has this been modified?
this is not the same issue. you aren't running your second command as sudo. the && resets the context
otherwise, make a new thread
... I will try running both with sudo
what about authelia?
sudo on both helped!! Thanks!!
I am now on 1.132.3 - but I didn't do anything to authelia... so that must be addressed in the the docker-compose.yml?
I backed up
Purged
Got latest image
and restored
I have deleted and created a new group and added my user to it,
I'll test it on the the next release
don't hijack other's thread, if you are having any issue open a #help-desk-support