Immich v1.135.0 - POTENTIAL BREAKING CHANGE #5264
Replies: 4 comments 9 replies
-
|
While 1.135.0 is all good - DO NOT UPDATE TO 1.135.1 - their attempt to handle the issue with vchord breaks our install. Looking into it! |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate the warning. Just to note, I updated to 1.135.0 prior to this warning and noticed that it broke 'SYMLINKS', I had to run those commands again to get it working. |
Beta Was this translation helpful? Give feedback.
-
|
@oerix That's odd. Can you provide your and do |
Beta Was this translation helpful? Give feedback.
-
|
@vhsdream It's basically the same setup from our conversation here. The media location stayed the same |
Beta Was this translation helpful? Give feedback.
-
|
Also, just tested the update from 1.135.0 - 1.135.2 and from 1.135.0 - 1.135.2 and they went OK, aside from my typo in the update script causing the DB to be reindexed unnecessarily. |
Beta Was this translation helpful? Give feedback.
-
|
You think 1.135.2 is running? The version is currently still fixed. Shall we change it back to the latest? |
Beta Was this translation helpful? Give feedback.
-
|
@MickLesk OK I will unpin. Side note, I think I've found a bug in the fetch_and_deploy_gh_release function, at least when it comes to updating Immich that way. |
Beta Was this translation helpful? Give feedback.
-
|
And what? |
Beta Was this translation helpful? Give feedback.
-
|
So I think that the arguments are parsed improperly - since the way immich is deployed it gets put into As I understand it, 'mode', 'version' and 'target' have default values if not specified: 'tarball', 'latest', and '/opt/$app', respectively. But using Similar thing happens if you specify only mode (version uses target value): Or version (mode uses version value, and version uses target value): I'm still specifying the arguments in order, but if I don't specify an empty value for mode or version (or an explicit), then the defaults don't get applied. Edit to add an example with blank arguments (which works): |
Beta Was this translation helpful? Give feedback.
-
Immich Upgrade Recovery Guide - Complete Troubleshooting DocumentationDate: 2025-08-06 📋 Problem SummaryAfter upgrading Immich using the Proxmox LXC community scripts, the application failed to start properly with multiple critical errors:
🔍 Initial DiagnosisStep 1: Analyzed Startup Script
Step 2: Directory Structure Assessment
Step 3: Referenced GitHub Discussion
🛠️ Resolution ProcessPhase 1: Backend Server RecoveryIssue: Node.js Build Dependencies Missing
Solution: Install System Dependenciesapt update && apt install -y pkg-config libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev
Issue: Missing Server Build Artifacts
Solution: Rebuild Server from Sourcecd /opt/immich/source/server
npm ci # Install dependencies (2m)
npm run build # Compile TypeScript (1m)
Issue: Incorrect Application Structure
Solution: Copy Build Artifacts to Runtime Locationcp -r /opt/immich/source/server/dist /opt/immich/app/
cp -r /opt/immich/source/server/node_modules /opt/immich/app/
cp /opt/immich/source/server/package.json /opt/immich/app/
Issue: Package.json Path Issues
Solution: Copy Package.json to Multiple Locationscp /opt/immich/source/server/package.json /opt/immich/
Phase 2: Geodata and Resource RecoveryIssue: Reverse Geocoding Failure
Solution: Copy and Symlink Geodatacp -r /opt/immich/source/server/resources /opt/immich/app/
mkdir -p /build && ln -sf /opt/immich/geodata /build/geodata
Phase 3: Frontend RecoveryIssue: Blank Page in Browser
Solution 1: Build TypeScript SDK Dependencycd /opt/immich/source/open-api/typescript-sdk
npm ci # Install SDK dependencies
npm run build # Build TypeScript SDK
Solution 2: Build Web Frontendcd /opt/immich/source/web
npm ci # Install web dependencies (2m)
npm run build # Build Svelte/Vite frontend (1m 37s)
Solution 3: Deploy Frontend Filesmkdir -p /build/www
cp -r /opt/immich/source/web/build/* /build/www/
Phase 4: Process Management and StartupIssue: Port Conflicts
Solution: Clean Process Management# Find processes using port 2283
netstat -tlnp | grep :2283
# Kill specific process
kill -9 23468
# Verify port is free
netstat -tlnp | grep :2283 # Should return nothing
Issue: Script Selection
Solution: Use Proper Startup Scriptcd /opt/immich
nohup ./start.sh > /tmp/immich-start.log 2>&1 &
🎯 Final VerificationBackend Verificationcurl -s -w "HTTP Status: %{http_code}\nResponse Time: %{time_total}s\n" http://127.0.0.1:2283/api/server-info/ping
Frontend Verificationcurl -s -w "HTTP Status: %{http_code}\nContent Length: %{size_download} bytes\n" http://127.0.0.1:2283
Service Status
📊 Summary of Changes MadeFiles Created/Modified:
System Commands Used:
|
Beta Was this translation helpful? Give feedback.
-
|
isnt better to create an new guide? this may be lost here |
Beta Was this translation helpful? Give feedback.
-
|
Apologies, i am new to GitHub etiquette, would i create a new discussion? |
Beta Was this translation helpful? Give feedback.
-
|
yeah, here: https://github.com/community-scripts/ProxmoxVE/discussions/new?category=guides or if you cannot reach this -> https://github.com/community-scripts/ProxmoxVE/discussions/new?category=general and i move it after creation in correct category |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hot new Immich just dropped, but don't update yet!
Please see #5025 for essential information about the changes. Only when the PR is merged is it OK to run the update. But it's not without risk.
Beta Was this translation helpful? Give feedback.
All reactions