#Files over 100MB fails
1 messages · Page 1 of 1 (latest)
: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
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker ps -adocs - 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...
- :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: read applicable release notes.
- :ballot_box_with_check: reviewed the FAQs for known issues.
- :ballot_box_with_check: reviewed Github for known issues.
- :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: uploaded the relevant information (see below).
- :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 -landdf -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.
This sounds like it could be a reverse proxy issue. Here's a link to the relevant documentation page: https://immich.app/docs/administration/reverse-proxy
- 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
-
Logs are uploaded
-
No changes made (just installed it)
-
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
- Immich version
Server: v2.7.5
Mobile: v2.7.5
App: 2.7.4 build.3045
what is the url you are using when connecting to immich?
https://immich.mailodatacenter.com
without the port
lets try ip:port, just like #5 states, like you said you tried
so it would be https://immich.domain.com:2283?
no. the actual ip address
ah okay
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:
buffering https://doc.traefik.io/traefik/reference/routing-configuration/http/middlewares/buffering/
The HTTP buffering middleware in Traefik Proxy limits the size of requests that can be forwarded to Services. Read the technical documentation.
For routing and load balancing in Traefik Proxy, EntryPoints define which port will receive packets and whether they are TCP or UDP. Read the technical documentation.
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'```
Local from my internal IP it works flawless
No issues at all
Probably has something to do with the proxy
I have set the read timeout to 600s, and the same applies to idle and write.
I have not set anything for maxRequestBodyBytes.