41 Replies
:wave: Hey @CON CAC,
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.I think i may have done something wrong in nginx
server {
server_name <immich.menace.supply>;
# allow large file uploads
client_max_body_size 50000M;
# Set headers
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# enable websockets: http://nginx.org/en/docs/http/websocket.html
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_redirect off;
# set timeout
proxy_read_timeout 600s;
proxy_send_timeout 600s;
send_timeout 600s;
location / {
proxy_pass http://192.168.1.12:2283;
}
}
are these settings correct?
Looks fine to me
weird
it says offline
And you can’t access it?
For the scheem try http
Then turn on enforce ssl
502
it just stays offline
hmm ill do more homework on it i suppose
everything looks normal
or correct
You can access locally, correct?
nah
i can not
i can not access immich.menace.supply
maybe something wrong on my end
I mean can you access the instance locally using the IP address?
yes
correct
this is
https://immich.menace.supplyChange https to http in the first tab mate
Immich (backend) does not support https
got it. thanks. will restart nginx
stilll off line
so odd
Well that was def one problem
Can you check the NPM logs
What changed to break it
Wait
Show the advanced tab please with screenshot
FYI @CON CAC
NPM doesn't need a lot of additional config
Yeah I’m wondering if they. Put the full config block in advanced
well
i just copied what was from the immich website
https://immich.app/docs/administration/reverse-proxy/
Yeah but that’s for Nginx not NPM
OHHH
Yes remove all that. Do it as @Mraedis showed
shoot ok
thank you
one sec
wow
lmaoooo
thank you
let me configure NPM
👍
NPM already has a bunch of additional config
client_max_body_size 50000M;
proxy_read-timeout 5m;
wait
if i add this, it goeso ff line
following this
You have a dash not an _
omg im so sorry
thank you
that worked!