this post was submitted on 03 Nov 2024
4 points (64.3% liked)

Selfhosted

40189 readers
786 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
4
Can't access immich on local network (lemmy.world)
submitted 1 week 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 1 week ago* (last edited 1 week 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 1 week ago

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

[–] OminousOrange@lemmy.ca 2 points 1 week 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 1 week 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 1 week 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 1 week ago

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

[–] just_another_person@lemmy.world 0 points 1 week ago

That's an IPv6 address forwarding to port 3001.