Broken LXC after upgrade from 2.2.3 to 2.3.x
I tried to upgrade to 2.3.x in a proxmox lxc - the web service is failing due to a missing corePlugin/manifest.json
Have been trying to run this down - and there is no /opt/immich/app/plugins directory at all
Any suggestions for trying to recover this, or building the missing files?
[Nest] 52205 - 11/20/2025, 10:16:19 AM LOG [Microservices:MetadataService] Initialized local reverse geocoder
Error: ENOENT: no such file or directory, open '/opt/immich/app/corePlugin/manifest.json'
at async open (node:internal/fs/promises:642:25)
at async Object.readFile (node:internal/fs/promises:1279:14)
at async PluginService.readAndValidateManifest (/opt/immich/app/dist/services/plugin.service.js:94:25)
at async PluginService.loadPluginsFromManifests (/opt/immich/app/dist/services/plugin.service.js:48:30)
at async PluginService.onBootstrap (/opt/immich/app/dist/services/plugin.service.js:30:9)
at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:91:13)
at async MicroservicesModule.onModuleInit (/opt/immich/app/dist/app.module.js:90:9)
at async callModuleInitHook (/opt/immich/app/nodemodules/.pnpm/@nestjs+core@11.1.8@nestjs+common@11.1.8_class-transformer@0.5.1_class-validator@0.14._a3ff1a5d48f77259e9f27c70f81ffd22/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9)
at async NestApplication.callInitHook (/opt/immich/app/nodemodules/.pnpm/@nestjs+core@11.1.8@nestjs+common@11.1.8_class-transformer@0.5.1_class-validator@0.14._a3ff1a5d48f77259e9f27c70f81ffd22/node_modules/@nestjs/core/nest-application-context.js:242:13)
at async NestApplication.init (/opt/immich/app/nodemodules/.pnpm/@nestjs+core@11.1.8@nestjs+common@11.1.8_class-transformer@0.5.1_class-validator@0.14._a3ff1a5d48f77259e9f27c70f81ffd22/node_modules/@nestjs/core/nest-application.js:103:9) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/opt/immich/app/corePlugin/manifest.json'
}
3 Replies
:wave: Hey @GeoffN,
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:We don't support the lxc install script, you'll have to ask the folks that made it