Probo domain verification is not working on this template.

Getting these error logs even with the TXT record in place for my domain.

{
  "message": "cannot verify domain",
  "attributes": {
    "time": "2026-02-18T17:44:29.539729176Z",
    "name": "probod.iam.saml-domain-verifier",
    "version": "0.124.0",
    "environment": "prod",
    "config_id": "S139j1LbAAEAKgAAAZxX3eLkgAshzdaG",
    "error": "cannot find TXT record for \"my-domain\"",
    "trace_id": "873774623403611d3707a384837532b2",
    "span_id": "509eee8017b4e9c3",
    "level": "error"
  }
}

Hey, not too familiar with Probo, can you tell me where that TXT record verification is happening?

The verification is happening in this container https://github.com/getprobo/probo/pkgs/container/probo which is part of the template. It asks to add the TXT record in the DNS management and I already did that but the validation does not work.

I was inquiring about where specifically in the Probo interface it requests that information or is that in the Railway dashboard?

Settings page: /organizations/1234560789/settings/saml-sso

How can I contribute to this template? The latest Probo version requires the https:// in front of the API_CORS_ALLOWED_ORIGINS variable

I can confirm that this is still the case and the template needs updating still.

It now also requires the env OAUTH2_SERVER_SIGNING_KEY to be added and have a generated key set in value - REF: https://www.probo.com/docs/configuration/environment-variables#oauth2-server

I managed to force domain validation running this query directly in the database: UPDATE iam_saml_configurations SET domain_verified_at = NOW();