Troubleshooting
Troubleshooting
Find practical checks for domains, DNS, and static Site deployments.
Start by confirming that you selected the Organization that owns the resource. Most Cloud resources are Organization-owned, and access can differ between Organizations.
A domain registration is still processing
Domain availability is checked again when registration is committed. A submitted or paid request is not proof that the domain is already active. Open the domain in Cloud and follow the displayed status or next action.
DNS changes are not visible yet
Confirm that the domain uses Qwibik-managed DNS. If it uses custom nameservers, update records with the external DNS provider. For Qwibik-managed DNS, verify the record type, name, and content, then allow time for DNS propagation.
A Site build failed
Review the deployment's build stage and sanitized failure message. Confirm that the project uses a supported static build, that its package manager and lockfile are present, and that the configured output directory contains a root index.html file.
My Next.js site needs a server
Qwibik Sites supports Next.js static export only. Server-side rendering, server actions, API routes, and dynamic Node.js servers are not supported. Configure static export or use another deployment approach for server workloads.