immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

ERR_SSL_PROTOCOL_ERROR downloading a bug album #4979

New Issue
Closed
opened 2026-02-05 11:02:09 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 11:02:09 +03:00
Owner
Copy Link

Originally created by @SchSeba on GitHub (Dec 19, 2024).

The bug

I am using immich-helm with ingress-nginx and when I try to deploy a big album I can see in the browser that it starts but after around 200M it stop and I get POST https://photos.sebasblog.com/api/download/archive net::ERR_SSL_PROTOCOL_ERROR 200 (OK)

When I use nodePort to access directly the immich server I am able to download the full album with no issue

The OS that Immich Server is running on

centos

Version of Immich Server

v1.123.0

Version of Immich Mobile App

none

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

server:
  enabled: true
  controller:
    replicas: 1
  image:
    repository: ghcr.io/immich-app/immich-server
    pullPolicy: IfNotPresent
  persistence:
    external-library:
      enabled: true
      type: pvc
      existingClaim: immich-external-library
      mountPath: /mnt
  ingress:
    main:
      enabled: true
      annotations:
        # proxy-body-size is set to 0 to remove the body limit on file uploads
        nginx.ingress.kubernetes.io/proxy-body-size: '0'
        # nginx.ingress.kubernetes.io/proxy-buffer-size: 256k
        # nginx.ingress.kubernetes.io/proxy-buffers-number: '100'
        nginx.ingress.kubernetes.io/proxy-max-temp-file-size: "0"
        nginx.ingress.kubernetes.io/proxy-connect-timeout: "600"
        nginx.ingress.kubernetes.io/proxy-send-timeout: "600"
        nginx.ingress.kubernetes.io/proxy-read-timeout: "600"
        nginx.ingress.kubernetes.io/proxy-request-buffering: "off"
        nginx.ingress.kubernetes.io/configuration-snippet: |
          # allow large file uploads
          #client_max_body_size 50000M;

          # Set headers
          # proxy_set_header Host              $http_host;
          # proxy_set_header X-Real-IP         $remote_addr;
          # proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
          # proxy_set_header X-Forwarded-Proto $scheme;

          # enable websockets: http://nginx.org/en/docs/http/websocket.html
          proxy_cache_bypass $http_upgrade;

          # set timeout
          send_timeout       600s;
        cert-manager.io/cluster-issuer: "letsencrypt-prod"
        kubernetes.io/ingress.class: nginx
      ingressClassName: nginx
      hosts:
        - host: photos.X.com
          paths:
            - path: "/"
      tls:
        - hosts:
          - photos.X.com
          secretName: immich-tls

Your .env content

None

Reproduction steps

1.try to download a big album 3Gi

Relevant log output

No response

Additional information

No response

Originally created by @SchSeba on GitHub (Dec 19, 2024). ### The bug I am using immich-helm with ingress-nginx and when I try to deploy a big album I can see in the browser that it starts but after around 200M it stop and I get `POST https://photos.sebasblog.com/api/download/archive net::ERR_SSL_PROTOCOL_ERROR 200 (OK)` When I use nodePort to access directly the immich server I am able to download the full album with no issue ### The OS that Immich Server is running on centos ### Version of Immich Server v1.123.0 ### Version of Immich Mobile App none ### Platform with the issue - [ ] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML server: enabled: true controller: replicas: 1 image: repository: ghcr.io/immich-app/immich-server pullPolicy: IfNotPresent persistence: external-library: enabled: true type: pvc existingClaim: immich-external-library mountPath: /mnt ingress: main: enabled: true annotations: # proxy-body-size is set to 0 to remove the body limit on file uploads nginx.ingress.kubernetes.io/proxy-body-size: '0' # nginx.ingress.kubernetes.io/proxy-buffer-size: 256k # nginx.ingress.kubernetes.io/proxy-buffers-number: '100' nginx.ingress.kubernetes.io/proxy-max-temp-file-size: "0" nginx.ingress.kubernetes.io/proxy-connect-timeout: "600" nginx.ingress.kubernetes.io/proxy-send-timeout: "600" nginx.ingress.kubernetes.io/proxy-read-timeout: "600" nginx.ingress.kubernetes.io/proxy-request-buffering: "off" nginx.ingress.kubernetes.io/configuration-snippet: | # allow large file uploads #client_max_body_size 50000M; # Set headers # proxy_set_header Host $http_host; # proxy_set_header X-Real-IP $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # proxy_set_header X-Forwarded-Proto $scheme; # enable websockets: http://nginx.org/en/docs/http/websocket.html proxy_cache_bypass $http_upgrade; # set timeout send_timeout 600s; cert-manager.io/cluster-issuer: "letsencrypt-prod" kubernetes.io/ingress.class: nginx ingressClassName: nginx hosts: - host: photos.X.com paths: - path: "/" tls: - hosts: - photos.X.com secretName: immich-tls ``` ### Your .env content ```Shell None ``` ### Reproduction steps 1.try to download a big album 3Gi ### Relevant log output _No response_ ### Additional information _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#4979
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?