#Unable to access the webapp

1 messages · Page 1 of 1 (latest)

strong yacht
#

After the last server update I have been unable to access the webapp. It's suck at the loading animation (image attached below). I have tried-

  1. Using different browsers with all extensions turned off
  2. accessing it on my phone
  3. Restarting my server with docker compose up -d --force-recreate
  4. Ran the docker container without any custom networks (as attached below)
  5. Accessing the webapp inside a browser running locally on the server.

The android app can connect to the server and works fine.

My setup:

I run immich on a remote server and access it over tailscale. I do not use reverse-proxies and access the webapp over plain http.
Immich files are stored inside a veracrypt container.

df -h output:

Filesystem              Size  Used Avail Use% Mounted on
udev                     16G     0   16G   0% /dev
tmpfs                   3.2G  2.1M  3.2G   1% /run
/dev/sda1               237G  206G   22G  91% /
tmpfs                    16G     0   16G   0% /dev/shm
tmpfs                   5.0M     0  5.0M   0% /run/lock
/dev/sda15              124M   12M  113M  10% /boot/efi
tmpfs                   3.2G  4.0K  3.2G   1% /run/user/1000
/dev/mapper/veracrypt1   98G   91G  2.4G  98% /home/cat/media/photos_enc
bold pollenBOT
#

:wave: Hey @strong yacht,

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 immich.

References

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :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 -l and df -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.

bold pollenBOT
little oyster
#

Please provide some logs. Server and potentially also take a look into browser logs.

strong yacht
#

docker logs immich_machine_learning

[05/09/26 15:22:28] INFO     Starting gunicorn 25.1.0
[05/09/26 15:22:28] INFO     Listening at: http://[::]:3003 (23)
[05/09/26 15:22:28] INFO     Using worker: immich_ml.config.CustomUvicornWorker
[05/09/26 15:22:28] INFO     Control socket listening at /usr/src/gunicorn.ctl
[05/09/26 15:22:28] INFO     Booting worker with pid: 40
[05/09/26 15:22:30] INFO     Started server process [40]
[05/09/26 15:22:30] INFO     Waiting for application startup.
[05/09/26 15:22:30] INFO     Created in-memory cache with unloading after 300s
                             of inactivity.
[05/09/26 15:22:30] INFO     Initialized request thread pool with 16 threads.
[05/09/26 15:22:30] INFO     Application startup complete.
#

docker logs immich_postgres

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2026-05-09 15:22:26.926 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2026-05-09 15:22:26.927 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2026-05-09 15:22:26.955 UTC [1] LOG:  starting PostgreSQL 14.19 (Debian 14.19-1.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
2026-05-09 15:22:26.955 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2026-05-09 15:22:26.955 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2026-05-09 15:22:26.959 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-05-09 15:22:26.966 UTC [32] LOG:  database system was shut down at 2026-05-09 15:22:17 UTC
2026-05-09 15:22:26.975 UTC [1] LOG:  database system is ready to accept connections
#

docker logs redis

1:M 09 May 2026 15:22:26.771 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause
failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 09 May 2026 15:22:26.771 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
1:M 09 May 2026 15:22:26.771 * Valkey version=8.1.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:M 09 May 2026 15:22:26.771 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf
1:M 09 May 2026 15:22:26.771 * Increased maximum number of open files to 10032 (it was originally set to 1024).
1:M 09 May 2026 15:22:26.771 * monotonic clock: POSIX clock_gettime
1:M 09 May 2026 15:22:26.772 * Running mode=standalone, port=6379.
1:M 09 May 2026 15:22:26.772 * Server initialized
1:M 09 May 2026 15:22:26.772 * Ready to accept connections tcp
1:M 09 May 2026 15:27:27.079 * 100 changes in 300 seconds. Saving...
1:M 09 May 2026 15:27:27.080 * Background saving started by pid 75
75:C 09 May 2026 15:27:27.086 * DB saved on disk
75:C 09 May 2026 15:27:27.086 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 09 May 2026 15:27:27.180 * Background saving terminated with success
weak swan
#

Have you tried a browser on your phone @strong yacht ?

weak swan
#

and that doesn't or does work...?

strong yacht