Forgeon Docs

Documentation, guides, and patterns to help you build on Forgeon — from your first deploy to running serious infrastructure.

Troubleshooting index

Start here for common deployment, domain, and database issues.

Last updated: 2026-03-17
Last reviewed by: Compliance team

This index points to the most common failure modes and their fixes. Use the decision trees first, then jump into the relevant docs.

How to use this page

  1. Start from the decision tree matching your symptom.
  2. Copy exact error text from logs/UI before trying fixes.
  3. Apply one fix at a time to avoid masking root cause.
  4. Re-run deploy/test and confirm result before moving on.

Decision tree: deployment failures

flowchart TD
  A[Deploy failed] --> B{Error type?}
  B -->|Missing envs| C[Add env vars in Settings → Environments]
  B -->|Build failed| D[Check build logs and lockfiles]
  B -->|Runtime not reachable| E[Verify PORT and 0.0.0.0]
  C --> F[Redeploy]
  D --> F
  E --> F

Decision tree: domain issues

flowchart TD
  A[Domain not working] --> B{DNS updated?}
  B -->|No| C[Fix DNS records]
  B -->|Yes| D{SSL pending?}
  D -->|Yes| E[Wait for verification]
  D -->|No| F{Routing correct?}
  F -->|No| G[Check domain environment mapping]
  F -->|Yes| H[Check runtime status]

Decision tree: database failures

flowchart TD
  A[DB provisioning failed] --> B{Plan eligible?}
  B -->|No| C[Upgrade to Pro/Enterprise]
  B -->|Yes| D{Quota exceeded?}
  D -->|Yes| E[Reduce usage or increase quota]
  D -->|No| F[Retry provisioning]

Common error strings

  • missing required environment variables → add env vars for the target env
  • Quota limit exceeded → upgrade plan or reduce usage
  • Domain not found → ensure domain is attached to the correct environment
  • Plan quota exceeded → check tenant plan assignment and current usage counters
  • Too many requests (429) → backoff + retry; review edge limits/rate policy
  • SSL pending / HTTPS preparing → DNS verified but cert not active yet; recheck validation and listener

Evidence checklist before escalation

Capture these first:

  • Project ID and tenant ID
  • Domain affected (default/custom)
  • Deployment ID and commit SHA
  • UTC timestamp of failure
  • Exact error payload (code/message)
  • Current runtime state (running, idle, degraded, failed)

If you still need help

Send the evidence checklist above to support so triage can start immediately without back-and-forth.