Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.well-known/immich is not respected #16531

Closed
1 of 3 tasks
waclaw66 opened this issue Mar 3, 2025 · 0 comments · Fixed by #16577
Closed
1 of 3 tasks

.well-known/immich is not respected #16531

waclaw66 opened this issue Mar 3, 2025 · 0 comments · Fixed by #16577

Comments

@waclaw66
Copy link
Contributor

waclaw66 commented Mar 3, 2025

The bug

Lets have immich host immich.example.com, when user enters host address to mobile client like example.com then mobile app has to check /.well-known/immich first for API endpoint and then /api/server/ping.
Mobile app currently doesn't check /.well-know/immich first and accesses https://example.com/api/server/ping directly, it obviously fails because API endpoint is https://immich.example.com/api/.

The problem is within resolveEndpoint function, that check availability first and then reads API endpoint, that's wrong, it has to in the opposite.

Future<String> resolveEndpoint(String serverUrl) async {

#3279 has broken .well-known functionality

@ddshd @alextran1502

The OS that Immich Server is running on

Fedora 41

Version of Immich Server

v1.128.0

Version of Immich Mobile App

v1.128.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

not relevant

Your .env content

not relevant

Reproduction steps

...

Relevant log output

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant