Access to Web UI returns "Unable to connect" After Upgrade to v1.26.1
Setup:
Immich running on a docker compose contrainer on a server machine within my LAN. The serve is on its on VLAN and all firewall rules have been configure to give access to that server. This setup has been working up until upgrade to v1.26.1. The only other docker compose contrainer running is Homarr which is accessible via the web UI on its dedicated port. Furthermore , on the same sever, I am running Unifi controller which is also accessible on its dedicated port
Usage:
When attempint to access Immich via <ip>:2283 I get a "Unable to connect" error. When attempting to access immich via mobile logs show the following
ApiExepction 400: Socket operation failed: GET /server/ping (Inner exeption: ClientExecptiuon with SocketExecption: Connection refused (OS Error: Connection regures, errno=61), address = <ip>, port = 53112, uri=https://<ip>:2283/api/server/ping)
General Question:
I don't think my issue is specific to this version of immich, it may be my set up. However, I cannot explain or understand why it was working before and now it does not. I am hoping for some guidance from the Immich team on things I should check.
Files:
Attached are docker-compose.yml, .env, and logs.6 Replies
:wave: Hey @kPee,
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. :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.
Please make sure you have read and followed the release notes: https://github.com/immich-app/immich/discussions?discussions_q=label%3Achangelog%3Abreaking-change+sort%3Adate_createdSuccessfully submitted, a tag has been added to inform contributors. :white_check_mark:
As bootz said above. YOu needed to read all release notes with breaking changes.
Your port mapping is wrong
2283:3001 -> 2283:2283
lol
I read that relase but only read the bottom half. Thanks.
This change worked. obviously.
This thread has been closed. To re-open, use the button below.