Unable to access WebUI after setting up on UnRaid
Hi, absolute beginner with servers and Immich. I did a fresh install of the container, no upgrades or anything like that. I have another container already using port 8080. Despite this, I cannot for the life of me access the WebUI after changing the port to 6161. What else do I need to be able to see the WebUI?
32 Replies
:wave: Hey @Clean Sweep Clear,
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 docs
- Container Status: 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
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. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.I'm not sure how to obtain my docker compose from UnRaid, but here's a screenshot of what I tried to change to access the WebUI:
You probably changed the port internally too, it doesn't work that way.
You need to change only the host port, the container port has to remain at 2883 if you're not changing it in the env file
If you want to change the container port to 6161 too instead of mapping it 6161->2883 you can use the
IMMICH_PORT environment variable https://immich.app/docs/install/environment-variables/The internal port change was more out of desperation. Technically the container worked just changing the regular port (the WebUI variable at the bottom) but the WebUI would refuse connection every time.
#unraid might have straightforward answers, I am not familiar with the config options that are unraid-specific 🙂
the WebUI: parameter looks odd to me though
I'd expect it to be
http://[IP]:[PORT]Try to add the env
SERVER_PORT=6161There's already a server port under 2283, should I have the WebUI and Server_Port match?
You should change the 2283 to 6161 for that one
Like this?
Sounds good
Darn, no luck. Connection's still refusing.
what's the docker logs?
It looks like everything's working. It's just the WebUI not playing nice.
you need to change the container port to 6161 too
or revert SERVER_PORT to 8080
ah the 8080 is not some unchangable value, that's just the default? 😄
wondered why it was greyed out
yep that's the default for the AIO
Yeah, the container port is unchangable. I'd have to remove that port and then re-add it under 6161 if I want to change it (though I assume that's unadvisable)
UnRaid is a bit fickle, I tried using Docker Compose but it refused to continue for whatever reason, so I decided to revert back to installing via Community Applications
then the best solution would be to revert
SERVER_PORT to 8080 (or delete that env)
then on unraid check if curl http://localhost:6161 works
maybe a server-client connection error? 🤷♂️I'm thinking maybe it just doesn't like me using my own redis container, but who knows at this point. I reverted everything save for the port being 6161, so let me see if it works
Both http and https failed to connect.
there's no https built-in
if you see immich mapping the api routes in the docker logs, it's not an immich issue
I figured it had something to do with my setup. I'll try to go the docker compose route, maybe I'll have less issues there.
hey everybody ... im here because i have quite the same problem .... from one day to another my immich is out of reachability ....
it worked for months ... now i have problems with accessing
mein problem is this ...
[Nest] 776 - 04/08/2025, 5:13:17 PM LOG [Api:Bootstrap] Immich Server is listening on http://127.0.0.1:4646 [v1.131.3] [production]
but it was always ip:4642
this is what i have as the docker i configured
.
and if i want to open the webui its open the 8080 port which isnt configured anywhere
so please can someone help me ??? 😄
Hi, this honestly isn’t really an immich issue. If you get stuck on a specific issue you could ask in #unraid
You may also want to reach out to unraid support as it’s an issue with their product
In your case, you changed
SERVER_PORT but not Container Port