[BUG] .jpe extension doesn't get uploaded #1426

Closed
opened 2026-02-05 01:46:21 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @phamduyphat on GitHub (Oct 6, 2023).

The bug

jpeg images ending with '.jpe' extension fails to upload with Bad request error

The OS that Immich Server is running on

OMV

Version of Immich Server

1.81.0

Version of Immich Mobile App

1.79.0 build.119

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "immich" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - stack.env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.yml
    #   service: hwaccel
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - stack.env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - stack.env
    restart: always

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release}
    env_file:
      - stack.env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
      # remove this to get debug messages
      - GLOG_minloglevel=1
    volumes:
      - tsdata:/data
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441
    env_file:
      - stack.env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

UPLOAD_LOCATION=/STUFF/Immich
IMMICH_VERSION=release
TYPESENSE_API_KEY=###########
DB_PASSWORD=########
DB_HOSTNAME=immich_postgres
DB_USERNAME=########
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=immich_redis
TYPESENSE_ENABLED=false

Reproduction steps

1. Deploy server + mobile app
2. select file ending with .jpe and backup
3. A red Failed(1) appears near the backup button when backup is finished

Additional information

It's probably just an extension logic issue :)

Originally created by @phamduyphat on GitHub (Oct 6, 2023). ### The bug jpeg images ending with '.jpe' extension fails to upload with Bad request error ### The OS that Immich Server is running on OMV ### Version of Immich Server 1.81.0 ### Version of Immich Mobile App 1.79.0 build.119 ### Platform with the issue - [ ] Server - [ ] Web - [X] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "immich" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - stack.env depends_on: - redis - database - typesense restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} # extends: # file: hwaccel.yml # service: hwaccel command: [ "start.sh", "microservices" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - stack.env depends_on: - redis - database - typesense restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} volumes: - model-cache:/cache env_file: - stack.env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release} env_file: - stack.env restart: always typesense: container_name: immich_typesense image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data # remove this to get debug messages - GLOG_minloglevel=1 volumes: - tsdata:/data restart: always redis: container_name: immich_redis image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3 restart: always database: container_name: immich_postgres image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441 env_file: - stack.env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release} environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 depends_on: - immich-server - immich-web restart: always volumes: pgdata: model-cache: tsdata: ``` ### Your .env content ```Shell UPLOAD_LOCATION=/STUFF/Immich IMMICH_VERSION=release TYPESENSE_API_KEY=########### DB_PASSWORD=######## DB_HOSTNAME=immich_postgres DB_USERNAME=######## DB_DATABASE_NAME=immich REDIS_HOSTNAME=immich_redis TYPESENSE_ENABLED=false ``` ### Reproduction steps ```bash 1. Deploy server + mobile app 2. select file ending with .jpe and backup 3. A red Failed(1) appears near the backup button when backup is finished ``` ### Additional information It's probably just an extension logic issue :)
OVERLORD added the format label 2026-02-05 01:46:21 +03:00
Author
Owner

@alextran1502 commented on GitHub (Oct 6, 2023):

Do you have a sample file can be used for testing?

@alextran1502 commented on GitHub (Oct 6, 2023): Do you have a sample file can be used for testing?
Author
Owner

@phamduyphat commented on GitHub (Oct 7, 2023):

https://drive.google.com/file/d/1B1oqWqcDrkNgcI0J5E5Z6aWKC6ZzisGg/view?usp=sharing @alextran1502 pretty much any .jpe file would do

@phamduyphat commented on GitHub (Oct 7, 2023): https://drive.google.com/file/d/1B1oqWqcDrkNgcI0J5E5Z6aWKC6ZzisGg/view?usp=sharing @alextran1502 pretty much any .jpe file would do
Author
Owner

@jrasm91 commented on GitHub (Oct 7, 2023):

This has already been implemented, tested, and merged. Will be available next release.

@jrasm91 commented on GitHub (Oct 7, 2023): This has already been implemented, tested, and merged. Will be available next release.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#1426