Deployment troubleshooting
Find help with failed builds, page loading, domains and usage limits.
On this page
My deployment is blocked
Open the deployment logs and contact support with your project name and the displayed error. Builds blocked before they start do not use build minutes. Wait for the issue to be resolved before trying again.
The output has no index.html
Set the output folder to the directory containing your built frontend’s index.html. For ZIP uploads, place index.html at the archive root. For Next.js, enable static export and use out; do not upload the server build folder.
My page loads but its data does not
Check the browser’s Network and Console panels for failed API requests. Confirm that the API URL uses HTTPS and is reachable, and that your API allows the deployed domain in its CORS settings. Check your authentication and cookie configuration if requests return 401 or 403.
A relative URL such as /api/users points to your frontend’s own domain. Unless you separately provide that endpoint, use your externally hosted API’s URL. StaticWeb does not deploy backend endpoints alongside your frontend.
My traffic is paused
Check Analytics, Credits, and Plan review. Your bandwidth or available credit may be exhausted, or a project may be suspended. After topping up, upgrading, or changing your resource selection, allow a little time for the change to take effect. Contact support if the site remains unavailable.
Credit purchase succeeded but the balance is unchanged
Refresh Credits after your payment is confirmed. If the balance still has not updated, contact support with your receipt or order ID—not your card details.
Contact support
Use the Contact page and include your project name, deployment ID, relevant error, and approximate time. Remove passwords, tokens, private source files, and payment-card details from logs before sharing them.