[BUG] Partner Sharing + Facial Recognition in partner's photos #863

Closed
opened 2026-02-04 23:07:01 +03:00 by OVERLORD · 13 comments
Owner

Originally created by @Snyaify on GitHub (May 19, 2023).

The bug

We select a partner with whom we have common access in the gallery. We select in his gallery any photo in which there is a person (recognized). Then we click on the "Additional Information" button, and instead of previewing a person there will be an empty place, when we try to click on a person we get an error :
Error - Something went wrong
Bad Request (400 - Bad Request)

The OS that Immich Server is running on

Docker

Version of Immich Server

v1.56.1

Version of Immich Mobile App

v1.56.1

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:release
    entrypoint: ["/bin/sh", "./start-server.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:release
    entrypoint: ["/bin/sh", "./start-microservices.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

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

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:release
    entrypoint: ["/bin/sh", "./entrypoint.sh"]
    env_file:
      - .env
    restart: always
    
  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.0
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    logging:
      driver: none
    volumes:
      - tsdata:/data
    restart: always

#   redis:
#     container_name: immich_redis
#     image: redis:6.2
#     restart: always

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

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

volumes:
  pgdata:
  model-cache:
  tsdata:
  
networks:
  default:
      name: ipv6
      external: true

Your .env content

###################################################################################
# Database
###################################################################################

DB_HOSTNAME=*******
DB_USERNAME=*******
DB_PASSWORD=*******
DB_DATABASE_NAME=*******

# Optional Database settings:
DB_PORT=5432

###################################################################################
# Redis
###################################################################################

REDIS_HOSTNAME=Redis

# REDIS_URL will be used to pass custom options to ioredis.
# Example for Sentinel
# {"sentinels":[{"host":"redis-sentinel-node-0","port":26379},{"host":"redis-sentinel-node-1","port":26379},{"host":"redis-sentinel-node-2","port":26379}],"name":"redis-sentinel"}
# REDIS_URL=ioredis://eyJzZW50aW5lbHMiOlt7Imhvc3QiOiJyZWRpcy1zZW50aW5lbDEiLCJwb3J0IjoyNjM3OX0seyJob3N0IjoicmVkaXMtc2VudGluZWwyIiwicG9ydCI6MjYzNzl9XSwibmFtZSI6Im15bWFzdGVyIn0=

# Optional Redis settings:

# Note: these parameters are not automatically passed to the Redis Container
# to do so, please edit the docker-compose.yml file as well. Redis is not configured
# via environment variables, only redis.conf or the command line

# REDIS_PORT=6379
# REDIS_DBINDEX=0
# REDIS_USERNAME=
# REDIS_PASSWORD=
# REDIS_SOCKET=

###################################################################################
# Upload File Location
#
# This is the location where uploaded files are stored.
###################################################################################

UPLOAD_LOCATION=/mnt/user/photo/immich/

###################################################################################
# Typesense
###################################################################################
TYPESENSE_API_KEY=7b30e649-3084-4305-90df-7e9696397c70
# TYPESENSE_ENABLED=false
# TYPESENSE_URL uses base64 encoding for the nodes json.
# Example JSON that was used:
# [
#      { 'host': 'typesense-1.example.net', 'port': '443', 'protocol': 'https' },
#      { 'host': 'typesense-2.example.net', 'port': '443', 'protocol': 'https' },
#      { 'host': 'typesense-3.example.net', 'port': '443', 'protocol': 'https' },
#  ]
# TYPESENSE_URL=ha://WwogICAgeyAnaG9zdCc6ICd0eXBlc2Vuc2UtMS5leGFtcGxlLm5ldCcsICdwb3J0JzogJzQ0MycsICdwcm90b2NvbCc6ICdodHRwcycgfSwKICAgIHsgJ2hvc3QnOiAndHlwZXNlbnNlLTIuZXhhbXBsZS5uZXQnLCAncG9ydCc6ICc0NDMnLCAncHJvdG9jb2wnOiAnaHR0cHMnIH0sCiAgICB7ICdob3N0JzogJ3R5cGVzZW5zZS0zLmV4YW1wbGUubmV0JywgJ3BvcnQnOiAnNDQzJywgJ3Byb3RvY29sJzogJ2h0dHBzJyB9LApd

###################################################################################
# Reverse Geocoding
#
# Reverse geocoding is done locally which has a small impact on memory usage
# This memory usage can be altered by changing the REVERSE_GEOCODING_PRECISION variable
# This ranges from 0-3 with 3 being the most precise
# 3 - Cities > 500 population: ~200MB RAM
# 2 - Cities > 1000 population: ~150MB RAM
# 1 - Cities > 5000 population: ~80MB RAM
# 0 - Cities > 15000 population: ~40MB RAM
####################################################################################

# DISABLE_REVERSE_GEOCODING=false
# REVERSE_GEOCODING_PRECISION=3

####################################################################################
# WEB - Optional
#
# Custom message on the login page, should be written in HTML form.
# For example:
# PUBLIC_LOGIN_PAGE_MESSAGE="This is a demo instance of Immich.<br><br>Email: <i>demo@demo.de</i><br>Password: <i>demo</i>"
####################################################################################

PUBLIC_LOGIN_PAGE_MESSAGE=

####################################################################################
# Alternative Service Addresses - Optional
#
# This is an advanced feature for users who may be running their immich services on different hosts.
# It will not change which address or port that services bind to within their containers, but it will change where other services look for their peers.
# Note: immich-microservices is bound to 3002, but no references are made
####################################################################################

IMMICH_WEB_URL=http://immich-web:3000
IMMICH_SERVER_URL=http://immich-server:3001
IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003


####################################################################################
# Alternative API's External Address - Optional
#
# This is an advanced feature used to control the public server endpoint returned to clients during Well-known discovery.
# You should only use this if you want mobile apps to access the immich API over a custom URL. Do not include trailing slash.
# NOTE: At this time, the web app will not be affected by this setting and will continue to use the relative path: /api
# Examples: http://localhost:3001, http://immich-api.example.com, etc
####################################################################################

#IMMICH_API_URL_EXTERNAL=http://localhost:3001

Reproduction steps

1. Open immich web gallery
2. Select "Sharing"
3. Select Partner
4. Open photo with some person
5. Click on info button
6. When you hover over Person, it seems that there is an empty place, if we press there we get:

🚨 Error - Something went wrong
Bad Request (400 - Bad Request)
...

Additional information

No response

Originally created by @Snyaify on GitHub (May 19, 2023). ### The bug We select a partner with whom we have common access in the gallery. We select in his gallery any photo in which there is a person (recognized). Then we click on the "Additional Information" button, and instead of previewing a person there will be an empty place, when we try to click on a person we get an error : Error - Something went wrong Bad Request (400 - Bad Request) ### The OS that Immich Server is running on Docker ### Version of Immich Server v1.56.1 ### Version of Immich Mobile App v1.56.1 ### Platform with the issue - [ ] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:release entrypoint: ["/bin/sh", "./start-server.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:release entrypoint: ["/bin/sh", "./start-microservices.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:release volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload - model-cache:/cache env_file: - .env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:release entrypoint: ["/bin/sh", "./entrypoint.sh"] env_file: - .env restart: always typesense: container_name: immich_typesense image: typesense/typesense:0.24.0 environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data logging: driver: none volumes: - tsdata:/data restart: always # redis: # container_name: immich_redis # image: redis:6.2 # restart: always database: container_name: immich_postgres image: postgres:14 env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} PG_DATA: /var/lib/postgresql/data volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: ghcr.io/immich-app/immich-proxy:release environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 logging: driver: none depends_on: - immich-server restart: always volumes: pgdata: model-cache: tsdata: networks: default: name: ipv6 external: true ``` ### Your .env content ```Shell ################################################################################### # Database ################################################################################### DB_HOSTNAME=******* DB_USERNAME=******* DB_PASSWORD=******* DB_DATABASE_NAME=******* # Optional Database settings: DB_PORT=5432 ################################################################################### # Redis ################################################################################### REDIS_HOSTNAME=Redis # REDIS_URL will be used to pass custom options to ioredis. # Example for Sentinel # {"sentinels":[{"host":"redis-sentinel-node-0","port":26379},{"host":"redis-sentinel-node-1","port":26379},{"host":"redis-sentinel-node-2","port":26379}],"name":"redis-sentinel"} # REDIS_URL=ioredis://eyJzZW50aW5lbHMiOlt7Imhvc3QiOiJyZWRpcy1zZW50aW5lbDEiLCJwb3J0IjoyNjM3OX0seyJob3N0IjoicmVkaXMtc2VudGluZWwyIiwicG9ydCI6MjYzNzl9XSwibmFtZSI6Im15bWFzdGVyIn0= # Optional Redis settings: # Note: these parameters are not automatically passed to the Redis Container # to do so, please edit the docker-compose.yml file as well. Redis is not configured # via environment variables, only redis.conf or the command line # REDIS_PORT=6379 # REDIS_DBINDEX=0 # REDIS_USERNAME= # REDIS_PASSWORD= # REDIS_SOCKET= ################################################################################### # Upload File Location # # This is the location where uploaded files are stored. ################################################################################### UPLOAD_LOCATION=/mnt/user/photo/immich/ ################################################################################### # Typesense ################################################################################### TYPESENSE_API_KEY=7b30e649-3084-4305-90df-7e9696397c70 # TYPESENSE_ENABLED=false # TYPESENSE_URL uses base64 encoding for the nodes json. # Example JSON that was used: # [ # { 'host': 'typesense-1.example.net', 'port': '443', 'protocol': 'https' }, # { 'host': 'typesense-2.example.net', 'port': '443', 'protocol': 'https' }, # { 'host': 'typesense-3.example.net', 'port': '443', 'protocol': 'https' }, # ] # TYPESENSE_URL=ha://WwogICAgeyAnaG9zdCc6ICd0eXBlc2Vuc2UtMS5leGFtcGxlLm5ldCcsICdwb3J0JzogJzQ0MycsICdwcm90b2NvbCc6ICdodHRwcycgfSwKICAgIHsgJ2hvc3QnOiAndHlwZXNlbnNlLTIuZXhhbXBsZS5uZXQnLCAncG9ydCc6ICc0NDMnLCAncHJvdG9jb2wnOiAnaHR0cHMnIH0sCiAgICB7ICdob3N0JzogJ3R5cGVzZW5zZS0zLmV4YW1wbGUubmV0JywgJ3BvcnQnOiAnNDQzJywgJ3Byb3RvY29sJzogJ2h0dHBzJyB9LApd ################################################################################### # Reverse Geocoding # # Reverse geocoding is done locally which has a small impact on memory usage # This memory usage can be altered by changing the REVERSE_GEOCODING_PRECISION variable # This ranges from 0-3 with 3 being the most precise # 3 - Cities > 500 population: ~200MB RAM # 2 - Cities > 1000 population: ~150MB RAM # 1 - Cities > 5000 population: ~80MB RAM # 0 - Cities > 15000 population: ~40MB RAM #################################################################################### # DISABLE_REVERSE_GEOCODING=false # REVERSE_GEOCODING_PRECISION=3 #################################################################################### # WEB - Optional # # Custom message on the login page, should be written in HTML form. # For example: # PUBLIC_LOGIN_PAGE_MESSAGE="This is a demo instance of Immich.<br><br>Email: <i>demo@demo.de</i><br>Password: <i>demo</i>" #################################################################################### PUBLIC_LOGIN_PAGE_MESSAGE= #################################################################################### # Alternative Service Addresses - Optional # # This is an advanced feature for users who may be running their immich services on different hosts. # It will not change which address or port that services bind to within their containers, but it will change where other services look for their peers. # Note: immich-microservices is bound to 3002, but no references are made #################################################################################### IMMICH_WEB_URL=http://immich-web:3000 IMMICH_SERVER_URL=http://immich-server:3001 IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003 #################################################################################### # Alternative API's External Address - Optional # # This is an advanced feature used to control the public server endpoint returned to clients during Well-known discovery. # You should only use this if you want mobile apps to access the immich API over a custom URL. Do not include trailing slash. # NOTE: At this time, the web app will not be affected by this setting and will continue to use the relative path: /api # Examples: http://localhost:3001, http://immich-api.example.com, etc #################################################################################### #IMMICH_API_URL_EXTERNAL=http://localhost:3001 ``` ### Reproduction steps ```bash 1. Open immich web gallery 2. Select "Sharing" 3. Select Partner 4. Open photo with some person 5. Click on info button 6. When you hover over Person, it seems that there is an empty place, if we press there we get: 🚨 Error - Something went wrong Bad Request (400 - Bad Request) ... ``` ### Additional information _No response_
OVERLORD added the 🖥️web label 2026-02-04 23:07:01 +03:00
Author
Owner

@michelheusschen commented on GitHub (May 19, 2023):

Confirmed, this is a permission issue likely caused by facial recognition and partner sharing being added in quick succession

@michelheusschen commented on GitHub (May 19, 2023): Confirmed, this is a permission issue likely caused by facial recognition and partner sharing being added in quick succession
Author
Owner

@mrijke commented on GitHub (May 21, 2023):

FWIW, the same also happens with Shared albums.

@mrijke commented on GitHub (May 21, 2023): FWIW, the same also happens with Shared albums.
Author
Owner

@jrasm91 commented on GitHub (May 21, 2023):

I think this would be a problem for all places and times you can view an asset detail, while not being the owner. So, shared links, shared albums, partner view, etc.

@jrasm91 commented on GitHub (May 21, 2023): I think this would be a problem for all places and times you can view an asset detail, while not being the owner. So, shared links, shared albums, partner view, etc.
Author
Owner

@alextran1502 commented on GitHub (Nov 1, 2023):

Hello is this issue still relevance? if not, can you help me close it?

@alextran1502 commented on GitHub (Nov 1, 2023): Hello is this issue still relevance? if not, can you help me close it?
Author
Owner

@jhf2442 commented on GitHub (Dec 31, 2023):

Hi, issue is still of relevance ! See Feature requests #5089 and #6024 -> please reopen !

@jhf2442 commented on GitHub (Dec 31, 2023): Hi, issue is still of relevance ! See Feature requests #5089 and #6024 -> please reopen !
Author
Owner

@chpeer commented on GitHub (Jan 5, 2024):

+1 it would be amazing to see this feature requests implemented!

@chpeer commented on GitHub (Jan 5, 2024): +1 it would be amazing to see this feature requests implemented!
Author
Owner

@TheGreyDiamond commented on GitHub (May 25, 2024):

Is this still an issue or already fixed?

@TheGreyDiamond commented on GitHub (May 25, 2024): Is this still an issue or already fixed?
Author
Owner

@jhf2442 commented on GitHub (May 25, 2024):

still an open topic unfortunately

@jhf2442 commented on GitHub (May 25, 2024): still an open topic unfortunately
Author
Owner

@TheGreyDiamond commented on GitHub (May 25, 2024):

Ah damn, credential sharing it is I guess 😅

@TheGreyDiamond commented on GitHub (May 25, 2024): Ah damn, credential sharing it is I guess 😅
Author
Owner

@davidvv commented on GitHub (Mar 29, 2025):

This topic seems to be closed as fixed but I am still having the issue. I cannot see faces on shared libraries. I would actually expect even the names to be shared. Most the pictures my wife and I take involve all of us. I dont think we have to tag the same people on both our libraries, there should be at least an option for it to share all that metadata between libraries

@davidvv commented on GitHub (Mar 29, 2025): This topic seems to be closed as fixed but I am still having the issue. I cannot see faces on shared libraries. I would actually expect even the names to be shared. Most the pictures my wife and I take involve all of us. I dont think we have to tag the same people on both our libraries, there should be at least an option for it to share all that metadata between libraries
Author
Owner

@glebskvor-boop commented on GitHub (Aug 30, 2025):

Sharing metadata between users would be a big step in the development of this project. Otherwise, the server (or manually the user) has to process the same thing X number of times.

@glebskvor-boop commented on GitHub (Aug 30, 2025): Sharing metadata between users would be a big step in the development of this project. Otherwise, the server (or manually the user) has to process the same thing X number of times.
Author
Owner

@ti-guru commented on GitHub (Sep 9, 2025):

Chiming in here; just set up immich with a huge external lib with 41 000 images from the past 20 years and sharing this with my partner. Would be great to share meta data such as faces, so we don't need to redo the face tagging (currently >2k faces).

@ti-guru commented on GitHub (Sep 9, 2025): Chiming in here; just set up immich with a huge external lib with 41 000 images from the past 20 years and sharing this with my partner. Would be great to share meta data such as faces, so we don't need to redo the face tagging (currently >2k faces).
Author
Owner

@jrasm91 commented on GitHub (Sep 9, 2025):

This issue was about a specific http request returning 400, which was not intended. It is intended to not share faces or people so that is working as designed.

There is a separate issue for the feature request to expand sharing to include people and faces (#12614).

@jrasm91 commented on GitHub (Sep 9, 2025): This issue was about a specific http request returning 400, which was not intended. It is intended to not share faces or people so that is working as designed. There is a separate issue for the feature request to expand sharing to include people and faces (#12614).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#863