Selfhosted

61475 readers

688 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Can't access immich on local network (lemmy.world)

submitted 2 years ago by d00phy@lemmy.world to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

I've been banging my head on this for a few days now, and I can't figure this out. When I start up immich container, I see in docker ps:

CONTAINER ID   IMAGE                                                        COMMAND                  CREATED              STATUS                        PORTS                                                                                                             NAMES
1c496e061c5c   ghcr.io/immich-app/immich-server:release                     "tini -- /bin/bash s…"   About a minute ago   Up About a minute (healthy)   2283/tcp, 0.0.0.0:2284->3001/tcp, [::]:2283->3001/tcp                                                             immich

netstat shows that port 2283 is listening, but I cannot access http://IP_ADDRESS:2283 from Windows, Linux, or Mac host. If I SSH in and run a browser back through that, I can't access it via localhost. I even tried changing the port to 2284. I can see the change in netstat and docker ps outputs, but still no luck accessing it. I also can't telnet to either port on the host. I know Immich is up because it's accessible via the swag reverse proxy (I've also tried bringing it up w/ that disabled). I don't see anything in the logs of any of the immich containers or any of the host system logs when I try to access.

All of this came about because I ran into the Cloudflare upload size limit and it seems I can't get around it for the strangest reason!

top 7 comments

sorted by: hot top controversial new old

[–] roofuskit@lemmy.world 16 points 2 years ago* (last edited 2 years ago) (2 children)

Did you read breaking changes? The ports changed recently. Also looks like you're redirecting two ports to one.

[–] d00phy@lemmy.world 8 points 2 years ago

Damn! I missed that one. Working now. Thanks!

[–] OminousOrange@lemmy.ca 2 points 2 years ago

This is quite important with Immich. They're good at documenting their breaking changes, just gotta make sure you check the changelog before updating. Also best to avoid auto updating with Watchtower or similar to avoid surprises.

[–] wmellon@social.infernalerror.com 2 points 2 years ago

@d00phy@lemmy.world based on your output it looks like it’s listening to 2284 on IPv4 and it’s only listening to 2283 on IPv6

[–] StrawberryPigtails@lemmy.sdf.org 1 points 2 years ago (1 children)

If I reading your docker ps result correctly, you seem to be forwarding docker port 2283 to host port 3001.

Try http://ip_address:3001 , if that fails try https.

[–] d00phy@lemmy.world 1 points 2 years ago

Won’t connect on either port using http or https.

[–] just_another_person@lemmy.world 0 points 2 years ago

That's an IPv6 address forwarding to port 3001.