#Files over 100MB fails

1 messages · Page 1 of 1 (latest)

amber herald
#

Hi, files over 100MB fails they get a Bad Gateway error.

I'm NOT using CF for Immich and the URL goes straight to my server.

How could i debug this issue ?

cosmic atlasBOT
#

:wave: Hey @amber herald,

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

#

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.

amber herald
#
  1. Docker Compose:
services:
  immich:
    image: 'ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}'
    restart: unless-stopped
    volumes:
      - 'immich-uploads:/usr/src/app/upload'
      - '/etc/localtime:/etc/localtime:ro'
    environment:
      SERVICE_URL_IMMICH_2283: 'https://immich.domain.com'
      DB_PASSWORD: '${SERVICE_PASSWORD_POSTGRES}'
      DB_USERNAME: '${SERVICE_USER_POSTGRES}'
      DB_DATABASE_NAME: '${DB_DATABASE_NAME:-immich}'
      TZ: '${TZ:-Europe/Amsterdam}'
    depends_on:
      redis:
        condition: service_healthy
      database:
        condition: service_healthy
    healthcheck:
      disable: false
    labels:
      - traefik.enable=true
      - traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https
      - traefik.http.routers.immich-http.entrypoints=http
      - traefik.http.routers.immich-http.rule=Host(`immich.mailodatacenter.com`)
      - traefik.http.routers.immich-http.middlewares=redirect-to-https
      - traefik.http.routers.immich-https.entrypoints=https
      - traefik.http.routers.immich-https.rule=Host(`immich.mailodatacenter.com`)
      - traefik.http.routers.immich-https.tls=true
      - traefik.http.routers.immich-https.tls.certresolver=letsencrypt
      - traefik.http.routers.immich-https.service=immich-service
      - traefik.http.services.immich-service.loadbalancer.server.port=2283
    networks:
      - immich-network
  immich-machine-learning:
    image: 'ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}'
    restart: unless-stopped
    volumes:
      - 'immich-model-cache:/cache'
    environment:
      TZ: '${TZ:-Europe/Amsterdam}'
    healthcheck:
      disable: false
    networks:
      - immich-network
  redis:
    image: 'redis:7.4-alpine'
    restart: unless-stopped
    healthcheck:
      test:
        - CMD
        - redis-cli
        - PING
      interval: 5s
      timeout: 10s
      retries: 20
    networks:
      - immich-network
  database:
    image: 'ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0'
    restart: unless-stopped
    environment:
      POSTGRES_PASSWORD: '${SERVICE_PASSWORD_POSTGRES}'
      POSTGRES_USER: '${SERVICE_USER_POSTGRES}'
      POSTGRES_DB: '${DB_DATABASE_NAME:-immich}'
      POSTGRES_INITDB_ARGS: '--data-checksums'
      DB_STORAGE_TYPE: '${DB_STORAGE_TYPE:-SSD}'
    volumes:
      - 'immich-postgres-data:/var/lib/postgresql/data'
    healthcheck:
      test:
        - CMD-SHELL
        - 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'
      interval: 5s
      timeout: 20s
      retries: 10
    networks:
      - immich-network
volumes:
  immich-uploads: null
  immich-model-cache: null
  immich-postgres-data: null
networks:
  immich-network: null
  1. Logs are uploaded

  2. No changes made (just installed it)

  3. Hardware / Software

HARDWARE:
Model:       HPE DL360 Gen9
IP:          192.168.1.199
CPU:         2× Xeon E5-2696 v4
Cores:       44 cores / 88 threads
RAM:         384 GB DDR4 ECC 2400Mhz
SSD1:        1x 4 TB NVME (3.7 TiB Usable)
RAID 1:      8×900 GB SAS RAID 6 (5.27 TiB Usable)

SOFTWARE:
OS: Ubuntu 24.04.4 LTS
Panel: Coolify
  1. Immich version
Server: v2.7.5
Mobile: v2.7.5
App: 2.7.4 build.3045
old rover
amber herald
#

without the port

old rover
#

lets try ip:port, just like #5 states, like you said you tried

amber herald
#

so it would be https://immich.domain.com:2283?

old rover
#

no. the actual ip address

amber herald
#

ah okay

jovial spindle
#

I see you are using traefik, did you set anything for the connection limits/timeouts? After how long does the upload fail? Resources to look into:

readTimeout https://doc.traefik.io/traefik/reference/install-configuration/entrypoints/#opt-transport-respondingTimeouts-readTimeout

buffering https://doc.traefik.io/traefik/reference/routing-configuration/http/middlewares/buffering/

amber herald
#

Right now i have set this inside the Traefik config:

      - '--entrypoints.https.transport.respondingTimeouts.readTimeout=0s'
      - '--entrypoints.https.transport.respondingTimeouts.writeTimeout=10m'
      - '--entrypoints.https.transport.respondingTimeouts.idleTimeout=10m'```
amber herald
#

Local from my internal IP it works flawless

#

No issues at all

#

Probably has something to do with the proxy

amber herald