[BUG] Web UI Error After Update to 1.81.1

[jbdubbs]

The bug

Web UI fails to load after upgrade to 1.88.1 from 1.7x series.. Changes to docker-compose.yml were made as shown below. .env file is stock.

Error message displayed on port 2283:

{"message":"Cannot GET /","error":"Not Found","statusCode":404}

Mobile app works fine.

The OS that Immich Server is running on

Ubuntu Server 22.04

Version of Immich Server

1.88.1

Version of Immich Mobile App

1.88.1

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

version: "3.8"

#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

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
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - 2283:3001
    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
      - /etc/localtime:/etc/localtime:ro
    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:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303>
    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:80cc8518800438c684a53ed829c621c94afd1087aaeb59b0d4343ed3>
    restart: always

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

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./library

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secrets for postgres and typesense. You should change these to random passwords
TYPESENSE_API_KEY=some-random-text
DB_PASSWORD=postgres

# The values below this line do not need to be changed
###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich_redis

Reproduction steps

1.  Upgrade from 1.7x server version to 1.88.1
2.  Attempt to load web UI, fails
3.  Mobile iOS app works great
...

Additional information

No response

[alextran1502]

Did you pull the latest image? Can you provide the logs for the server container?

[jbdubbs]

I pulled the 1.88.1 image earlier today.

root@librephotos:/home/immich# docker ps
CONTAINER ID   IMAGE                                                COMMAND                  CREATED       STATUS       PORTS                                       NAMES
bbcb8a01c4ad   portainer/agent:latest                               "./agent"                2 hours ago   Up 2 hours   0.0.0.0:9001->9001/tcp                      portainer_agent
f6eed1c0b583   ghcr.io/immich-app/immich-server:release             "tini -- /bin/sh sta…"   3 hours ago   Up 3 hours   3001/tcp                                    immich_microservices
f4a0ee8e1690   ghcr.io/immich-app/immich-server:release             "tini -- /bin/sh sta…"   3 hours ago   Up 3 hours   0.0.0.0:2283->3001/tcp, :::2283->3001/tcp   immich_server
3119b11ea53b   postgres:14-alpine                                   "docker-entrypoint.s…"   3 hours ago   Up 3 hours   5432/tcp                                    immich_postgres
be5acd8f9f6a   ghcr.io/immich-app/immich-machine-learning:release   "tini -- ./start.sh"     3 hours ago   Up 3 hours                                               immich_machine_learning
5d080b2adc1b   redis:6.2-alpine                                     "docker-entrypoint.s…"   3 hours ago   Up 3 hours   6379/tcp                                    immich_redis
5c9d2ebe2cc7   typesense/typesense:0.24.1                           "/opt/typesense-serv…"   3 hours ago   Up 3 hours   8108/tcp                                    immich_typesense

Logs attached. Seems like I'm missing stuff from that log, but let me know how I can get what you need.

Thanks!
_immich_server_logs (1).txt

[alextran1502]

Look like your mount isn't working properly. Trying bring down the stack, pull again and bring it backup

[janstadt]

Im also seeing this issue. I see the typesense container constantly restarting which i believe is whats causing the server to not be able to fully start.

I came to this conclusion after seeing this in the server logs:

Request #1700617769052: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND typesense"
Request #1700617769052: Sleeping for 4s and then retrying request...

Logs from typesense container:

W20231122 01:59:13.196125   358 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:13.196133   358 node.cpp:497] node default_group:192.168.96.3:8107:8108 init_log_storage failed
E20231122 01:59:13.196138   358 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:13.196260   358 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:18.460539   358 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:18.460551   358 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:18.460557   358 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:18.460937   358 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:20.789126   358 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:20.789139   358 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:20.789144   358 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:20.789546   358 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:23.155570   357 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:23.155623   357 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:23.155647   357 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:23.156225   357 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:25.653314   358 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:25.653322   358 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:25.653326   358 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:25.653717   358 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:28.616863   357 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:28.616874   357 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:28.616880   357 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:28.617266   357 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:33.073171   358 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:33.073184   358 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:33.073190   358 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:33.073643   358 typesense_server_utils.cpp:302] Failed to start peering state
W20231122 01:59:40.735471   358 log.cpp:1017] open segment conflict, path: /data/state/log first_index: 203371
E20231122 01:59:40.735481   358 node.cpp:497] node default_group:192.168.96.7:8107:8108 init_log_storage failed
E20231122 01:59:40.735484   358 raft_server.cpp:121] Fail to init peering node
E20231122 01:59:40.735922   358 typesense_server_utils.cpp:302] Failed to start peering state

[janstadt]

Ok so i map my tsdata to a different location and when i updated things, i think the tsdata was either corrupted or doesnt work with the previous versions of stuff. I moved the directory and had the container create a new directory and it seems like the container isnt restarting any longer.

[jbdubbs]

Pulling again, which also upgraded to 1.88.2 has resolved this issue. Thanks!