#Unable to connect to server after Upgrade to 1.85
1 messages · Page 1 of 1 (latest)
End of logs: https://basedbin.fly.dev/p/9vRYSf.txt
Phone ^
The last upgrades just worked with this method without any problems, I'm using the default docker-compose with adjusted .env
Any ideas?
did you pull it?
That error is coming from (what I think is) your reverse proxy?
try docker-compose pull then docker-compose down and finally docker-compose up
Yes, that was my procedure
Was also my first guess, but without it, it also doesn't let me connect to it
If you go to the api endpoint directly in the browser, what is the error?
throwing a 502, but not sure from which nginx
but im passing /api with nginx config:
client_max_body_size 50000M;
location /api {
# Compression
gzip_static on;
gzip_min_length 1000;
gzip_comp_level 2;
proxy_buffering off;
proxy_buffer_size 16k;
proxy_busy_buffers_size 24k;
proxy_buffers 64 4k;
proxy_force_ranges on;
proxy_http_version 1.1;
proxy_set_header Host $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;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
rewrite /api/(.*) /$1 break;
proxy_pass http://immich_server:3001;
}
It worked like this for some weeks now with 5 version upgrades, I dont know why it stopped working
I didnt miss anything in the release notes that shouldve changed things
can you access your instance over local IP?
Ahah, my nginx was still running; when I expose an port, then i can access immich again
Did some rewrite rules change with the upgrade?
no 🤔
hmmmm
Sorry for the noise, I restarted my entire Docker Stack and now I have a connection again
It seems strange, that I don't see anything in any log
Ah btw, is it save so skip version? So e.g. no im on 1.85 and i dont pull 1.86, but only upgrade to 1.90
Depends, if the mobile app auto update, it might not work with the version of your server
I set it to always ask me, I'm just not keen to always upgrade the server+app every time a new release comes out
Sometimes webservers cache DNS queries. If openresty was using an IP and on restart the IP changed it could lead to this situation.