You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The bug
Lets have immich host
immich.example.com
, when user enters host address to mobile client likeexample.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 accesseshttps://example.com/api/server/ping
directly, it obviously fails because API endpoint ishttps://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.immich/mobile/lib/services/api.service.dart
Line 86 in 9b842d4
#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
Your docker-compose.yml content
not relevant
Your .env content
Reproduction steps
...
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: