Common deployment errors

Last reviewed: September 27, 2026

Start with the message in “Deploy”. Open the log when available and identify the stage that stopped. Do not repeat deployment while an operation is still running.

Missing button or status loading failure

1
Check your account and role
Deployment requires a signed-in owner. If you are an editor or viewer, ask the owner to deploy. Complete registration if you are using a guest account.
2
Retry loading the status
For a status loading error, click “Try again” and wait. Failure to read status does not mean your website is unpublished.
3
Read any availability message
If deployment is not configured, contact support. If Codey is working or the result is being reviewed, wait until it finishes and reopen “Deploy”.

Unavailable or invalid name

1
Correct the name
Use 4–63 lowercase Latin letters, numbers, or hyphens, with no leading or trailing hyphen.
2
Choose an alternative
If taken or reserved, enter another name and wait for “Available”, then “Confirm & deploy”. After it is fixed, connect your own domain if you need a different address.

Deployment blocked by a critical finding

1
Read the report
Review the critical finding, its description, and the suggested fix below the blocking message. Clicking “Deploy” again will not resolve it.
2
Open “Security”
Use “Fix with Codey” when findings are shown. “Solve with Codey” in the deployment panel appears for a failed deployment; it may be absent when a scan blocks the attempt before a new deployment starts.
3
Wait for the fix, then deploy
If no fix button is available, give Codey the finding description without any secret value. Wait for the task, test the preview, then deploy again to rerun the gate.

Build or startup failure

1
Open the log
In “Deploy”, open the deployment log and click “Refresh”. Find the first clear error, such as a missing file, missing setting, or conflicting page routes.
2
Use “Solve with Codey”
When available, click it to send the error and available log to a repair task. Otherwise, describe the message to Codey in chat.
3
Test the result, then redeploy
Wait for the repair and test the preview. If a secret is missing, add it in “Secrets”. Redeploy after saving. If the same error repeats, give support its description and attempt time after removing sensitive values.

Preview works but live data differs

1
Check which database is involved
Preview and the data editor use development, while the published website uses production. Test rows are not automatically transferred just by deploying.
2
Check database setup and schema
Open “Database” and wait for the ready message. If a risky schema change blocks deployment, open the schema updates section and review its impact before confirming anything.
3
Ask for a specific fix
Tell Codey which page or operation fails on the published website. For an imported project, complete its required database migration step. See Your database and Schema updates.

The domain does not open

1
Test the subdomain
Open the project subdomain first. If it also fails, check deployment status and logs before changing DNS.
2
Check your domain records
Show the domain records again in the domains section. Match the full TXT name and value, then match the A or CNAME routing value shown.
3
Wait and verify again
Allow minutes to hours for DNS propagation, then click “Verify”. Ownership verification alone does not mean activation completed. Contact support if no routing address can be resolved or the failure persists.

Hosting stopped or balance blocks deployment

1
Read the stop reason
Open hosting coverage in “Deploy”. Check whether the owner stopped it, the balance caused suspension, or a deletion request is pending.
2
Address the cause
If a balance settlement dialog appears, follow it to billing. Review any deletion request in project settings. Changing a tier alone does not restart the website.
3
Resume and check
After resolving the cause, click “Restart” for a stopped website, wait for the result, and open its link. If the error remains, read the current status before another attempt.