#"Server is not reachable" from mobile app while browser works.

1 messages · Page 1 of 1 (latest)

abstract crystalBOT
#

:wave: Hey @frosty sky,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :ballot_box_with_check: I have reviewed Github for known issues.
  5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :ballot_box_with_check: I have 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)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

proper apex
#

in addition to everything the bot asks for, please post screenshots of the full URL you are using in the mobile web browser and the mobile app on the same device. internal IPs are not private so you do not need to censor them

#

are you using tailscale?

#

also, in the mobile browser, my guess is the protocol is HTTPS? please click to show the first few letters / why it has that exclamation mark

#

I feel like this is not tailscale but I don't understand your ip address

#

you should be using the local IP address for the immich machine, should start with 10. or 192. or 172.

frosty sky
#
  1. Is my IP from at&t.
#

Is like to use the app from my phone while not at home.

proper apex
#

I ran into this issue with someone else in #1304830232460656701 but AT&T has weird hairpin NAT setup so this will not work like you are hoping

#

you will need to do one of those options I mentioned towards the end, either get a new router basically or use tailscale or a VPS/VPN

solid aurora
#

And also, never ever expose an application publicly without a reverse proxy for https