Forgeon Docs

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

Runbooks

Step‑by‑step guides for common operational issues.

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

These runbooks are designed to resolve common problems without support.

Runbook: Deploy failed

  1. Open Deployments → Logs
  2. Identify the first failure line
  3. If missing envs → add env vars in Settings → Environments
  4. If build failed → verify lockfiles and build command
  5. Redeploy

Runbook: Preview URL loads but app errors

  1. Check Runtime logs
  2. Verify PORT usage and bind to 0.0.0.0
  3. Confirm start command is correct
  4. Restart runtime

Runbook: Custom domain not working

  1. Open Domains tab
  2. Verify domain is attached to correct environment
  3. Check DNS records and wait for propagation
  4. Confirm SSL status is Issued

Runbook: DB provisioning failed

  1. Check plan eligibility (Pro/Enterprise)
  2. Check quotas in Billing usage
  3. Retry provisioning from project banner
  4. If still failing, rotate admin credentials and retry

Runbook: Credits not applied to invoice

  1. Open Settings → Credits and confirm balance
  2. Check billing policy allows credits for plan charges
  3. Wait for next invoice cycle

Runbook: Marketplace payout delayed

  1. Open Marketplace → Payouts (seller) or Easy‑Forge (admin)
  2. Check payout profile status (complete + verified)
  3. Confirm payout is not paused by admin risk control
  4. Verify payout status logs and FX conversion rate

Runbook: Buildpacks build failed

  1. Open build logs and find the first buildpack error
  2. If stack mismatch → use supported builder image
  3. If buildpack missing → ensure buildpack image exists in registry
  4. Redeploy after adjusting buildpack config