Skip to content

Parseable exits at startup when the OIDC provider is unreachable #1863

Open

Description

@stalingino

/about output: version v3.2.7 (also on main at 0de90cf).

Description:

When OIDC is configured (P_OIDC_ISSUER, ...) and the provider's discovery document cannot be fetched at startup, Parseable exits:

Error: error sending request for url (https://idp.example.com/.well-known/openid-configuration)
    0: client error (Connect)
    1: tcp connect error
    2: Connection refused (os error 111)

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.

Activity

  1. nikhilsinhaparseable commented on Nov 19, 2026

    @nikhilsinhaparseable
    Member

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions