Custom domain SSL validation lacks detailed error reporting

Answer

From existing model knowledge there is no confirmed public evidence that Discloud exposes distinct, user-visible error details that separate DNS mismatch from ACME rate-limit throttling for custom domain SSL validation. The platform is known to surface a generic validation error and a pending to active state, and with current model knowledge there is no confirmed non-restart mechanism to retrieve the exact failure reason in the user UI.

Confirmed facts vs likely explanation

Confirmed from model knowledge: Discloud requires correct A or CNAME records for a custom domain and automates SSL issuance. The domain status moves from pending to active and can stall with a generic validation error.

Unconfirmed: The exact internal error taxonomy, whether detailed ACME failure reasons are surfaced in the UI or logs, and whether a diagnostic view exists without manual restart.

Likely explanation: The opaque failure mode is consistent with an automated ACME style validation flow where DNS propagation delay, incorrect record target, and CA rate-limit responses are mapped internally to a single generic validation error for users, rather than exposing ACME error type, observed DNS answer versus expected target, resolver check timestamp, or rate-limit retry-after.

Error details that would distinguish causes

To distinguish DNS mismatches from rate-limit throttling Discloud would need to expose:

• ACME error type and code from the CA
• DNS answer actually observed versus the expected A/CNAME target
• Resolver and check timestamp for the validation attempt
• CA rate-limit identifier with retry-after hint when throttled

No confirmed evidence these fields are exposed to users without manual restart.

Steps needed for this case

1. Check the Discloud dashboard domain status page for the exact wording shown for the affected domain and note whether a timestamp or retry hint is present.
2. Perform independent DNS checks from multiple public resolvers for the domain's A and CNAME records against the target Discloud requires, and compare propagation timing to the validation attempt window.
3. If the error persists, request internal validation logs from Discloud support and ask specifically for the ACME error type, observed DNS answer, and any rate-limit response received. With current model knowledge this is the only confirmed way to obtain an exact failure reason.

Model knowledge on Discloud is limited and may be outdated. UI and logging behavior can change without notice.