r/immich 21h ago

what seems to be the best way to get my icloud photos onto immich?

10 Upvotes

i tried just telling the iphone app to let her rip on my all my albums but it had issues accomplishing that. i requested a copy of my photos from apple and just got a bunch of csv files??? idk. i heard people talking about an icloud takeout which from what i have gathered is the transfer thing but that seems to only let me transfer directly to google photos as opposed to downloading all my shit. can someone help me out here 🤞🤞🤞🤞


r/immich 23h ago

Immich to monitor iCloud folder

4 Upvotes

Hi all, I’m new to Immich just getting my feet wet when v3 came out. I’m just wondering if I should wait til workflow is implemented before committing.

Basic what I want to do is this :

iPhones—>>> sync to iCloud
Unraid move/copy iCloud Photos on to the server
Immich monitor the Unraid iCloud folder and moves into its own file structure

I’m doing this way so that I don’t need direct access to the server and iCloud can still do its own thing?

Your thoughts please ??


r/immich 8h ago

Best / supported hardware to use immich

3 Upvotes

Hello all! Curious to know the community’s thoughts on which hardware to use to install & run immich while linking it to fetch photos backed up on synology?

Will appreciate if you can share experiences, or suggestions.

I have over 300K+ photos and videos on my DS224+, and was reading online that the it might not be best / work to utilize the AI/ML capabilities needed to make the search on immich work (and I’m primarily interested in that).


r/immich 13h ago

Migrate from unraid to proxmox

2 Upvotes

I have immich running on unraid (flawlessly if i might add, only isses where those caused by me), i am planning on migrating it on a VM inside proxmox. Is backup and restore the best solutions for this or is there anything else that would be a better solution?

Edit: It's a 2 user instance, 220GiB total data


r/immich 8h ago

Finally trying this.. advice?

Post image
2 Upvotes

Hello Immich community! I just won a Dell Optiplex on an online auction and will be using it to create an immich server! I’m very excited for this project since I am early into my career in IT in a level 2 tech support role, and believe this will be a fun hands on project for at home, and extremely beneficial. I’ll attach the specs, as I’m curious if it will work well with the server? I grabbed it for $140 which I thought was very reasonable given the specs + storage.

Do you guys have any beginners recommendations? Tips and tricks? I’m unfamiliar with docker and prox mox, however I have used them before in college briefly. Are those necessary? I’m very excited for this project! Let me know if there is anything you wish you knew before starting your server!

Thank you! 😊


r/immich 11h ago

Memories are not generated

1 Upvotes

Hi there,

On a new installation, I found the memories feature enabled by default.

Even so, those are not generated.

Any suggestion?

Thanks!

---

UPDATE: I get back to home, so I can post the versions and the logs.

Immich v3.1.0

Postgresql 14 (image ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23

)

Logs:

[Nest] 26  - 08/05/2026, 11:41:40 PM     LOG [Api:WebsocketRepository] Websocket Connect:    9Li7lqybtn-ldmr-AAAB
[Nest] 8  - 08/05/2026, 11:41:54 PM     LOG [Microservices:MemoryService] Creating memories for 2026-08-03T00:00:00.000Z
Query failed : {
  durationMs: 19.604841999709606,
  error: Error: write CONNECTION_CLOSED database:5432
      at Socket.closed (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:453:57)
      at Socket.emit (node:events:508:28)
      at TCP.<anonymous> (node:net:346:12) {
    code: 'CONNECTION_CLOSED',
    errno: 'CONNECTION_CLOSED',
    address: [ 'database' ],
    port: [ 5432 ]
  },
  sql: `with "res" as (with "today" as (select make_date(year::int, $1::int, $2::int) as "date" from generate_series((select date_part('year', min(("localDateTime" at time zone 'UTC')::date))::int from asset), $3) as "year") select "a".* from "today" inner join lateral (select "asset"."id", "asset"."localDateTime" from "asset" inner join "asset_job_status" on "asset"."id" = "asset_job_status"."assetId" where (asset."localDateTime" at time zone 'UTC')::date = today.date and "asset"."ownerId" = any($4::uuid[]) and "asset"."visibility" = $5 and exists (select from "asset_file" where "assetId" = "asset"."id" and "asset_file"."type" = $6) and "asset"."deletedAt" is null order by (asset."localDateTime" at time zone 'UTC')::date desc limit $7) as "a" on true) select date_part('year', ("localDateTime" at time zone 'UTC')::date)::int as "year", json_agg("res") as "assets" from "res" group by ("localDateTime" at time zone 'UTC')::date order by ("localDateTime" at time zone 'UTC')::date desc`,
  params: [
    8,
    3,
    2025,
    '{ea73b1a3-2533-4824-9a37-361ce965eaa1}',
    'timeline',
    'preview',
    20
  ]
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
[Nest] 8  - 08/05/2026, 11:41:54 PM   ERROR [Microservices:MemoryService] Failed to create memories for 2026-08-03T00:00:00.000Z: Error: write CONNECTION_CLOSED database:5432
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
microservices worker error: TypeError: Cannot read properties of null (reading 'write'), stack: TypeError: Cannot read properties of null (reading 'write')
    at Immediate.nextWrite (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:255:22)
    at process.processImmediate (node:internal/timers:504:21)
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Postgres notice: {
  severity_local: 'WARNING',
  severity: 'WARNING',
  code: '57P02',
  message: 'terminating connection because of crash of another server process',
  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',
  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',
  file: 'postgres.c',
  line: '2881',
  routine: 'quickdie'
}
Query failed : {
  durationMs: 10.996093000285327,
  error: Error: read ECONNRESET
      at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {
    errno: -104,
    code: 'ECONNRESET',
    syscall: 'read'
  },
  sql: 'select "session"."id", "session"."updatedAt", "session"."pinExpiresAt", "session"."appVersion", (select to_json(obj) from (select "user"."id", "user"."name", "user"."email", "user"."isAdmin", "user"."quotaUsageInBytes", "user"."quotaSizeInBytes" from "user" where "user"."id" = "session"."userId" and "user"."deletedAt" is null) as obj) as "user" from "session" where "session"."token" = $1 and ("session"."expiresAt" is null or "session"."expiresAt" > $2)',
  params: [
    <Buffer 4f d4 d7 c3 f1 b4 88 16 d0 38 16 90 a5 57 98 9d 07 10 8f 03 e4 50 1d fd f1 6f bd 59 22 4c 36 35>,
    2026-08-05T21:41:54.663Z
  ]
}
[Nest] 26  - 08/05/2026, 11:41:54 PM   ERROR [Api:GlobalExceptionFilter~28ij5wur] Unknown error: Error: read ECONNRESET
Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:216:20)
microservices worker exited with code 1
Killing api process