We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When PHOTOPRISM_SITE_URL is configured with a path prefix (e.g. "http://192.168.1.100:20800/photoprism"), the Kubernetes health probes fail because they are hardcoded to check the root path "/". The probes attempt to access "http://192.168.1.100:20800/" instead of "http://192.168.1.100:20800/photoprism", resulting in 404 errors and failed liveness checks.
PHOTOPRISM_SITE_URL
Health probes should respect the path prefix defined in PHOTOPRISM_SITE_URL and check the correct endpoint.
Health probes only check the root path "/", ignoring the configured path prefix, which causes 404 errors and failed health checks.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
When
PHOTOPRISM_SITE_URL
is configured with a path prefix (e.g. "http://192.168.1.100:20800/photoprism"), the Kubernetes health probes fail because they are hardcoded to check the root path "/". The probes attempt to access "http://192.168.1.100:20800/" instead of "http://192.168.1.100:20800/photoprism", resulting in 404 errors and failed liveness checks.Steps to Reproduce
PHOTOPRISM_SITE_URL
to "http://192.168.1.100:20800/photoprism"Expected Behavior
Health probes should respect the path prefix defined in
PHOTOPRISM_SITE_URL
and check the correct endpoint.Current Behavior
Health probes only check the root path "/", ignoring the configured path prefix, which causes 404 errors and failed health checks.
Environment
PHOTOPRISM_SITE_URL
with path prefixThe text was updated successfully, but these errors were encountered: