Importing older immich library in new install

I used immich a few months ago on my PC, but after deciding to change hardware I copied the whole immich-app folder containing the uploads and the db folders to another drive, and deleted everything else including the docker containers. After installing the current version of immich and changing the UPLOAD_LOCATION and the DB_DATA_LOCATION to my old folders and the DB_USERNAME and DB_PASSWORD to my old user in the .env file it gave me this error:
ERROR [Microservices:DatabaseRepository] Migrations failed: Error: Invalid upgrade path. For more information, see https://immich.app/errors#typeorm-upgrade⁠
ERROR [Microservices:DatabaseRepository] Migrations failed: Error: Invalid upgrade path. For more information, see https://immich.app/errors#typeorm-upgrade⁠
So I've installed 2 older version (first v1.130.1, roughly from the same time period I first installed it and then v1.132.0), and I can access the web interface and view my photos, but it disconnects from time to time and the redis container gives me these errors:
Error: connect ETIMEDOUT
at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41)
at Object.onceWrapper (node:events:632:28)
at Socket.emit (node:events:518:28)
at Socket._onTimeout (node:net:609:8)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect'
}
Error: connect ETIMEDOUT
at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41)
at Object.onceWrapper (node:events:632:28)
at Socket.emit (node:events:518:28)
at Socket._onTimeout (node:net:609:8)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect'
}
Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'redis'
}
Error: getaddrinfo ENOTFOUND redis
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'redis'
}
missing 'error' handler on this Redis client
missing 'error' handler on this Redis client
5 Replies
Immich
Immich5w ago
:wave: Hey @skylinefx, 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.
skylinefx
skylinefxOP5w ago
This also appears in the logs
1:C 04 Sep 2025 12:28:19.235 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 12:28:19.235 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 12:28:19.235 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 12:28:19.235 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 12:28:19.236 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 12:28:19.236 # Server initialized
1:M 04 Sep 2025 12:28:19.237 # Can't handle RDB format version 11
1:M 04 Sep 2025 12:28:19.237 # Fatal error loading the DB: Invalid argument. Exiting.
1:C 04 Sep 2025 12:28:19.235 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 12:28:19.235 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 12:28:19.235 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 12:28:19.235 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 12:28:19.236 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 12:28:19.236 # Server initialized
1:M 04 Sep 2025 12:28:19.237 # Can't handle RDB format version 11
1:M 04 Sep 2025 12:28:19.237 # Fatal error loading the DB: Invalid argument. Exiting.
bo0tzz
bo0tzz5w ago
Try deleting the redis container & its data volume, then starting things back up
skylinefx
skylinefxOP5w ago
It worked, thank you very much!
Immich
Immich5w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?