Diagnose a BlinkHost problem safely

Start with the boundary

Ask which surface is failing: browser preview, build, deployment, production request, backend module, database binding, custom domain, or telemetry query. Preview and production are different runtimes; a failure in one does not prove a failure in the other.

Record the exact visible state, operation, UTC time, project ID, release ID where available, region, browser and version, and the first useful error. Check the smallest relevant log or diagnostic window. Never include passwords, cookies, authorization headers, tokens, secret values, connection strings, payment details, or customer data.

Recover without hiding the cause

1. Preserve unsaved work and copy the relevant diagnostic.
2. Check whether the operation is still visibly progressing.
3. Retry a safe read or preview restart only after identifying its state.
4. Do not repeatedly submit deployments, payments, policy publications, or other mutations after an ambiguous response.
5. Use the relevant troubleshooting guide below.

Choose the relevant guide

• WebContainer preview
• Deployments and production releases
• Backend modules
• Databases and bindings
• Custom domains and DNS
• Logs, analytics, and runtime policies

Escalate a production blocker to support@blinkhost.me with the evidence above and the business impact. Send sensitive material only through a separately approved secure channel when support explicitly requests it.