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
{{ message }}
Repository navigation
Parseable exits at startup when the OIDC provider is unreachable #1863
ParseableServer::start does connect_oidc(config).await?, so a discovery failure aborts the server. An identity provider outage, or simply starting Parseable before the provider (common in docker compose and Kubernetes), keeps Parseable down entirely, including ingestion and basic-auth logins that don't need OIDC. Under a restart policy it crash-loops until the provider is back.
Expected: Parseable starts and serves ingestion, queries and basic auth. It keeps retrying discovery in the background, and OIDC login starts working as soon as the provider answers. Until then, /api/v1/o/login returns a clear 503 rather than acting as if OIDC were not configured.
@stalingino thanks for reporting the issue, the server start and backgroup discovery is definitely right approach to this issue, will get back to you once done.
Activity
nikhilsinhaparseable commentedon Nov 19, 2026
@stalingino thanks for reporting the issue, the server start and backgroup discovery is definitely right approach to this issue, will get back to you once done.