caezar
caezar
PostsComments
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
Here it uploads.
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
If I run the container in the kubernetes cluster and mount the drive on one of the nodes, I can get it to work. 
apiVersion: v1
kind: Pod
metadata:
  name: upload-cli-pod
  namespace: immich
spec:
  nodeName: <NODE_NAME>
  containers:
    - name: immich-cli
      image: "ghcr.io/immich-app/immich-cli:latest"
      args: ["upload", "/import" ]
      volumeMounts:
        - name: volume
          mountPath: /import
      env:
        - name: IMMICH_INSTANCE_URL
          value: "http://immich-server:2283"
        - name: IMMICH_API_KEY
          value: <API_KEY>
  volumes:
    - name: volume
      hostPath:
        path: <PATH_TO_IMAGES>
apiVersion: v1
kind: Pod
metadata:
  name: upload-cli-pod
  namespace: immich
spec:
  nodeName: <NODE_NAME>
  containers:
    - name: immich-cli
      image: "ghcr.io/immich-app/immich-cli:latest"
      args: ["upload", "/import" ]
      volumeMounts:
        - name: volume
          mountPath: /import
      env:
        - name: IMMICH_INSTANCE_URL
          value: "http://immich-server:2283"
        - name: IMMICH_API_KEY
          value: <API_KEY>
  volumes:
    - name: volume
      hostPath:
        path: <PATH_TO_IMAGES>
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
docker run -it -p 8000:8080 -v "$(pwd)":/import:ro -e IMMICH_INSTANCE_URL=http://localhost:8000/api -e IMMICH_API_KEY=<redacted> ghcr.io/immich-app/immich-cli:latest upload /import
node:internal/deps/undici/undici:13502
      Error.captureStackTrace(err);
            ^

TypeError: fetch failed
    at node:internal/deps/undici/undici:13502:13
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async p (file:///usr/src/app/dist/index.js:3135:12)
    at async e (file:///usr/src/app/dist/index.js:3087:16)
    at async Object.i [as fetchJson] (file:///usr/src/app/dist/index.js:3101:66)
    at async Object.y [as ok] (file:///usr/src/app/dist/index.js:3188:13)
    at async scan (file:///usr/src/app/dist/index.js:19616:28)
    at async upload (file:///usr/src/app/dist/index.js:19600:21) {
  [cause]: AggregateError [ECONNREFUSED]:
      at internalConnectMultiple (node:net:1139:18)
      at afterConnectMultiple (node:net:1712:7) {
    code: 'ECONNREFUSED',
    [errors]: [
      Error: connect ECONNREFUSED ::1:8000
          at createConnectionError (node:net:1675:14)
          at afterConnectMultiple (node:net:1705:16) {
        errno: -111,
        code: 'ECONNREFUSED',
        syscall: 'connect',
        address: '::1',
        port: 8000
      },
      Error: connect ECONNREFUSED 127.0.0.1:8000
          at createConnectionError (node:net:1675:14)
          at afterConnectMultiple (node:net:1705:16) {
        errno: -111,
        code: 'ECONNREFUSED',
        syscall: 'connect',
        address: '127.0.0.1',
        port: 8000
      }
    ]
  }
}

Node.js v22.14.0
docker run -it -p 8000:8080 -v "$(pwd)":/import:ro -e IMMICH_INSTANCE_URL=http://localhost:8000/api -e IMMICH_API_KEY=<redacted> ghcr.io/immich-app/immich-cli:latest upload /import
node:internal/deps/undici/undici:13502
      Error.captureStackTrace(err);
            ^

TypeError: fetch failed
    at node:internal/deps/undici/undici:13502:13
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async p (file:///usr/src/app/dist/index.js:3135:12)
    at async e (file:///usr/src/app/dist/index.js:3087:16)
    at async Object.i [as fetchJson] (file:///usr/src/app/dist/index.js:3101:66)
    at async Object.y [as ok] (file:///usr/src/app/dist/index.js:3188:13)
    at async scan (file:///usr/src/app/dist/index.js:19616:28)
    at async upload (file:///usr/src/app/dist/index.js:19600:21) {
  [cause]: AggregateError [ECONNREFUSED]:
      at internalConnectMultiple (node:net:1139:18)
      at afterConnectMultiple (node:net:1712:7) {
    code: 'ECONNREFUSED',
    [errors]: [
      Error: connect ECONNREFUSED ::1:8000
          at createConnectionError (node:net:1675:14)
          at afterConnectMultiple (node:net:1705:16) {
        errno: -111,
        code: 'ECONNREFUSED',
        syscall: 'connect',
        address: '::1',
        port: 8000
      },
      Error: connect ECONNREFUSED 127.0.0.1:8000
          at createConnectionError (node:net:1675:14)
          at afterConnectMultiple (node:net:1705:16) {
        errno: -111,
        code: 'ECONNREFUSED',
        syscall: 'connect',
        address: '127.0.0.1',
        port: 8000
      }
    ]
  }
}

Node.js v22.14.0
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
OK, I port forwarded to 8080 on my local machine and mapped it to 8080 on the docker container. Now I get an ECONNREFUSD, so I must be doing something wrong.
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
I can port forward the immich service and try connecting to localhost. Do you think that is it?
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
But I can increase, although I can upload images fine through the UI.
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
I'm not uploading videos
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
How do I try bypassing the ingress?
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: immich-ingress
  namespace: immich
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 50m
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
  ingressClassName: "nginx"
  tls:
  - hosts:
    - redacted
    secretName: immich-tls
  rules:
  - host: redacted
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: immich-server
            port:
              number: 2283
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: immich-ingress
  namespace: immich
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 50m
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
  ingressClassName: "nginx"
  tls:
  - hosts:
    - redacted
    secretName: immich-tls
  rules:
  - host: redacted
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: immich-server
            port:
              number: 2283
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
I'm running in kubernetes following the official chart, with a modified ingress.
22 replies
IImmich
Created by caezar on 4/11/2025 in #help-desk-support
TypeError: fetch failed on upload
env:
  REDIS_HOSTNAME: '{{ printf "%s-redis-master" .Release.Name }}'
  DB_HOSTNAME: "{{ .Values.postgresql.global.postgresql.auth.hostname }}"
  DB_USERNAME: "{{ .Values.postgresql.global.postgresql.auth.username }}"
  DB_DATABASE_NAME: "{{ .Values.postgresql.global.postgresql.auth.database }}"
  # -- You should provide your own secret outside of this helm-chart and use `postgresql.global.postgresql.auth.existingSecret` to provide credentials to the postgresql instance
  DB_PASSWORD: "{{ .Values.postgresql.global.postgresql.auth.password }}"
  IMMICH_MACHINE_LEARNING_URL: '{{ printf "http://%s-machine-learning:3003" .Release.Name }}'

image:
  tag: v1.131.3

immich:
  persistence:
    library:
      existingClaim: library-pvc

server:
  ingress:
    main:
      hosts:
        - host: redacted
          paths:
            - path: "/"

redis:
  enabled: true
  architecture: standalone
  auth:
    enabled: false

postgresql:
  primary:
    containerSecurityContext:
      readOnlyRootFilesystem: false
    initdb:
      scripts:
        create-extensions.sql: |
          CREATE EXTENSION cube;
          CREATE EXTENSION earthdistance;
          CREATE EXTENSION vectors;
  global:
    postgresql:
      auth:
        hostname: postgres-immich-service
        username: redacted
        database: immich
        password: redacted
env:
  REDIS_HOSTNAME: '{{ printf "%s-redis-master" .Release.Name }}'
  DB_HOSTNAME: "{{ .Values.postgresql.global.postgresql.auth.hostname }}"
  DB_USERNAME: "{{ .Values.postgresql.global.postgresql.auth.username }}"
  DB_DATABASE_NAME: "{{ .Values.postgresql.global.postgresql.auth.database }}"
  # -- You should provide your own secret outside of this helm-chart and use `postgresql.global.postgresql.auth.existingSecret` to provide credentials to the postgresql instance
  DB_PASSWORD: "{{ .Values.postgresql.global.postgresql.auth.password }}"
  IMMICH_MACHINE_LEARNING_URL: '{{ printf "http://%s-machine-learning:3003" .Release.Name }}'

image:
  tag: v1.131.3

immich:
  persistence:
    library:
      existingClaim: library-pvc

server:
  ingress:
    main:
      hosts:
        - host: redacted
          paths:
            - path: "/"

redis:
  enabled: true
  architecture: standalone
  auth:
    enabled: false

postgresql:
  primary:
    containerSecurityContext:
      readOnlyRootFilesystem: false
    initdb:
      scripts:
        create-extensions.sql: |
          CREATE EXTENSION cube;
          CREATE EXTENSION earthdistance;
          CREATE EXTENSION vectors;
  global:
    postgresql:
      auth:
        hostname: postgres-immich-service
        username: redacted
        database: immich
        password: redacted
22 replies