#Auto start after reboot?
1 messages · Page 1 of 1 (latest)
:wave: Hey @solemn sail,
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
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker ps -adocs - 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...
- :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
- :blue_square: read applicable release notes.
- :blue_square: reviewed the FAQs for known issues.
- :blue_square: reviewed Github for known issues.
- :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
- :blue_square: uploaded the relevant information (see below).
- :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 -landdf -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.
Hey,
Yes that should be possible. Can you check if the docker/podman service is enabled?
For podman: sudo systemctl status podman
For docker: sudo systemctl status docker
In this output you should see disabled or enabled.
When it is disabled its easy to solve using sudo systemctl enable podman or sudo systemctl enable docker
If it is already enabled we will have to think of something else.
Can you see if the service is enabled and let me know?
Also I would invest in a UPS. Random shutdowns on databases are very hard and can cause a lot of corruption
That seemed to fix it!
Yeah unfortunately that just bit me in the butt, it crashed while I was skimming through the settings on the site, and now after starting the docker, the website is no more. Can't access it through my local network, I'll have to mess around with it more/reinstall it tomorrow. Just glad my images are safe on an external drive lol