Immich•2mo ago

401 error :(

Invalid user token (401)

Stacktrace
Error: Error: 401
at Object.xe [as ok] (http://10.52.52.181:2283/_app/immutable/chunks/CF_UN3Of.js:1:2725)
at async #a (http://10.52.52.181:2283/_app/immutable/chunks/OwiETBYY.js:1:647)
at async u.init (http://10.52.52.181:2283/_app/immutable/chunks/OwiETBYY.js:1:253)
at async p (http://10.52.52.181:2283/_app/immutable/nodes/5.B2HU6t7k.js:1:156)
at async Ve (http://10.52.52.181:2283/_app/immutable/chunks/DROl9vJf.js:1:14614)

Log:

[Nest] 34 - 11/20/2025, 10:35:14 PM ERROR [Api:WebsocketRepository] Websocket connection error: UnauthorizedException: Invalid user token
UnauthorizedException: Invalid user token
at AuthService.validateSession (/usr/src/app/server/dist/services/auth.service.js:381:15)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async AuthService.authenticate (/usr/src/app/server/dist/services/auth.service.js:126:25)
at async WebsocketRepository.handleConnection (/usr/src/app/server/dist/repositories/websocket.repository.js:43:26)

Immich•11/20/25, 10:41 PM

:wave: Hey @JLO,

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

Container Logs:
```
docker compose logs
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
docker ps -a
```
docs
Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA

Immich•11/20/25, 10:41 PM

Checklist

I have...

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

/close

command, and re-open it later if needed.

JLOOP•11/20/25, 10:42 PM

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F2B8ED04-4E92-4C6D-A7BD-0F215F676665

Device Start End Sectors Size Type
/dev/vda1 34 1465147391 1465147358 698.6G Linux filesystem

Disk /dev/sda: 100 GiB, 107374182400 bytes, 209715200 sectors
Disk model: QEMU HARDDISK
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8A11DBB9-FCA3-44CE-B6D8-BBFD65568D12

Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 209713151 209709056 100G Linux filesystem

JLOOP•11/20/25, 11:02 PM

immich@Immich:/data/immich$ docker compose up -d
yaml: line 64: did not find expected key

Alex Tran•11/21/25, 12:12 AM

what is the content of your docker-compose and .env look like?

JLOOP•11/21/25, 12:24 AM

immich_docker_compose.html2.64KB

JLOOP•11/21/25, 12:24 AM

immich_env.html1.06KB

JLOOP•11/21/25, 12:25 AM

I chose to use an external hdd for upload and ssd for db and thumb nails

JLOOP•11/21/25, 12:26 AM

When i rebooted i received the error message

Alex Tran•11/21/25, 1:11 AM

Can you show the logs when you run

docker compose up

docker compose up

JLOOP•11/21/25, 3:07 AM

how do i do that? I sumitted the logs for the immich_Server

JLOOP•11/21/25, 3:18 AM

man now it switched from using the mounted drive to the proxmox drive.

Alex Tran•11/21/25, 3:58 AM

hmm seems like there are problem with your overall setup, probably good to outline how are you running the services

JLOOP•11/21/25, 4:20 AM

I have an interal hdd that i passed through to the immich vm which is running ubuntu server

JLOOP•11/21/25, 4:20 AM

and then i followed this guide to mount the hdd

JLOOP•11/21/25, 4:20 AM

https://hakedev.substack.com/p/proxmox-pass-hdd-to-container?r=2t6qg6&utm_campaign=post&utm_medium=web&triedRedirect=true

Proxmox - Pass HDD to Container

The first thing you want to do is create a mount point for your drive using the drives UUID.

JLOOP•11/21/25, 4:21 AM

the guide is for containers but i modifed the one command line to reflect that difference

JLOOP•11/21/25, 4:21 AM

it worked well and the i rebooted the vm and then everything fell apart

JLOOP•11/21/25, 4:21 AM

I can delete the vm and start fresh since this is a frsh install

JLOOP•11/21/25, 4:22 AM

Docker install: https://docs.docker.com/engine/install/ubuntu/#installation-methods

JLOOP•11/21/25, 4:23 AM

immich install:https://docs.immich.app/install/docker-compose/

Alex Tran•11/21/25, 4:33 AM

Alright so you are using proxmox?

JLOOP•11/21/25, 4:39 AM

yes I am using promox 9.1

JLOOP•11/21/25, 4:39 AM

fresh install this afternoon.

Alex Tran•11/21/25, 5:07 AM

do you mount your NAS via proxmox interface?

JLOOP•11/21/25, 5:12 AM

its just drive attached to my mobo that i passthrough using the qm command in proxmox

Alex Tran•11/21/25, 5:17 AM

MOBO?

JLOOP•11/21/25, 5:27 AM

motherboard

Alex Tran•11/21/25, 5:29 AM

USB drive?

JLOOP•11/21/25, 5:36 AM

sata

JLOOP•11/21/25, 5:36 AM

its an internal drive

Alex Tran•11/21/25, 5:36 AM

okay, so does your proxmox mount it as a storage space?

Alex Tran•11/21/25, 5:37 AM

something like. this?

JLOOP•11/21/25, 5:37 AM

JLOOP•11/21/25, 5:38 AM

promox just passes the phyiscal disk through to the vm

Mraedis•11/21/25, 8:14 AM

Is your fstab properly done @JLO ?

Mraedis•11/21/25, 8:17 AM

This might interest you https://davejansen.com/systemctl-delay-start-docker-service-until-mounts-available/

Dave Jansen

Delayed starting of Docker service until expected mounts are available

(Or for any other systemctl controlled service, for that matter)

If you've ever run into the situation where you reboot your computer (or virtual machine) and the Docker service kicked in a bit too fast, even before some of your fstab defined mounts are fully available, you might've noticed that