Docker WebGUI Missing

[themushum]

I had to un-install Immich from my Unraid docker and re-install it. Since my many attempts to re-install it, I notice the WebGUI option is not available on the docker's list of options. I am at a loss to know how to fix it.

[CambridgeB]

I also have same issue.

[themushum]

Solution is to go to advanced tab in docker and add port in GUI section.

[crazywussian]

could we get a bit more detailed solution please?

[themushum]

This is in an UnRaid environment for context.

Go to the the Docker Tab.
Go to your Immich Docker.
Edit your Immich Docker.
Turn on Advanced View toggle upper right corner.
Scroll Down to WebUI:
Enter the following: http://[IP]:[PORT:8085]/ or whatever port you assigned to Immich in the initial setup. Entering IP is not necessary just the port number.
That's it. Once it recomposes, the WebUI option should now be available.

[crazywussian]

sadly, no dice

[23Reverend23]

I have the same issue with the WebUI. When I checked the log, it was caught in an endless loop while trying to start up, just kept repeating this over and over:

ImmichStartupError: Failed to write "<UPLOAD_LOCATION>/encoded-video/.immich - Please see https://docs.immich.app/administration/system-integrity#folder-checks for more information."
    at StorageService.verifyWriteAccess (/app/immich/server/dist/services/storage.service.js:154:19)
    at async /app/immich/server/dist/services/storage.service.js:57:21
    at async /app/immich/server/dist/repositories/database.repository.js:369:27
    at async /app/immich/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/kysely.js:535:20
    at async DefaultConnectionProvider.provideConnection (/app/immich/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
    at async /app/immich/server/dist/repositories/database.repository.js:366:13

Node.js v24.11.0
api worker exited with code 1
Missing history for endpoint: Retrieve auth status
(node:400) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Starting api worker
Missing history for endpoint: Retrieve auth status
(node:421) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[Nest] 421  - 12/15/2025, 12:19:56 AM     LOG [Api:WebsocketRepository] Initialized websocket server
[Nest] 421  - 12/15/2025, 12:19:56 AM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for clip_index of 0 rows
[Nest] 421  - 12/15/2025, 12:19:56 AM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for face_index of 0 rows
[Nest] 421  - 12/15/2025, 12:19:56 AM     LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{}}
[Nest] 421  - 12/15/2025, 12:19:56 AM     LOG [Api:StorageService] Writing initial mount file for the encoded-video folder
[Nest] 421  - 12/15/2025, 12:19:56 AM    WARN [Api:StorageService] Found existing mount file, skipping creation
[Nest] 421  - 12/15/2025, 12:19:56 AM   ERROR [Api:StorageService] Failed to write /photos/encoded-video/.immich: Error: EACCES: permission denied, open '/photos/encoded-video/.immich'
/app/immich/server/dist/services/storage.service.js:154
            throw new misc_1.ImmichStartupError(`Failed to write "${externalPath} - ${docsMessage}"`);

I think this is why it can't start the web UI. Does that look like what you are seeing on your end?

[themushum]

Looks like a permissions issue "Failed to write /photos/encoded-video/.immich: Error: EACCES: permission denied,"

By no means an expert, but what i did at one point was delete the entire docker, all the files in appdata related to it, deleted the previous installation as seen in Previous Apps left side, and basically left nothing behind so I could do a clean installation. I clicked on the Advanced tab on the far right and frankly, took more time and looked carefully at every entry I made. Making sure I had WebUI: filled out with http://[IP]:[PORT:8086]/ in my case. You do have to make sure the port is available and not used anywhere else. See Show Docker allocations. You likely already know most of this, but its how I managed to get it working.

[23Reverend23]

It does seem to be a permission problem, you're right. Crazy thing is, when I look in the /photos/encoded-video/ folder, the .immich file is there! Like, obviously you have the permission, my dude!

Complete clean reinstall, you say? Hmm. Does that mean that the problem is that it found a .immich file already there when it went to write it? It seems silly for it to say "I don't have permission to write this file" when it found the file already written, but I suppose weirder things have happened. I'll try to do a better job of erasing everything and do (yet) another reinstall. Wish me luck!

[23Reverend23]

Well! The good news is that cleaning up the /photos folder did in fact fix the permission problem. And so for the first time since I started this journey a few days ago, the Immich, Redis, and Postgres containers are all up and running!! Amazing. Also your directions to get the WebUI entry back on the container menu worked a treat, and I see it there.

The bad news is that when I click on WebUI, the new window just says "404 Error, nginx" Sigh. I'm guessing this is a separate issue now....

[themushum]

That error sounds familiar. Your connecting via http right? Not https. I relied on this video a bit.

https://www.youtube.com/watch?v=Od7Z4SgoAtc

[crazywussian]

Node.js v24.11.0
Missing history for endpoint: Retrieve auth status
(node:407) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
^

Error: connect ECONNREFUSED 127.0.0.1:5433
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 5433
}

here is my error log loop, thoughts?

[23Reverend23]

Hey, @themushum , just wanted to share my happy ending. That video you suggested was good, but AlienTech didn't have any troubles with no access on the WebUI, so no joy on that front. I did finally get the thing running, though! Wanna know how I did it? You'll laugh...

I deleted the Immich container, and re-installed it using the "noML" branch instead of the "Default" branch, and surprise surprise surprise it works now. No idea why that would make all the difference, but there it is.

[crazywussian]

ya, see i just tried that and i have the same issue persisting, no webui function...

[themushum]

Great news @23Reverend23 ! Of the top of my head, not familiar with the "noML" branch instead of the "Default" branch. I'll have to look into that for future reference. Immich works great. My wife has 49,649 pictures on it and she is still uploading from past years. 179 Gb.

@crazywussian address: '127.0.0.1',port: 5433 This is setup to your loopback address? I set the IP as the UnRaid server plus make sure I use a different port than the other docker containers. Again, no expert.

[23Reverend23]

That's right, you have to use your server's IP address, the one that starts with 192.168.... Also I think port 5433 is reserved for the postgres database. Your WebUI port of Immich is configured to 8080 by default. I've found that if 8080 is taken by some other application (Nextcloud famously requires port 8080) I like to use 8081, 8082 or like that. Just makes it easier to remember what ports are for what. Just like if I need another Postgres container, I'll give the new one port 5434 or 5435.