Skip to content
Swebsy · docs

Deployment errors

GitHub Pages errors

Section titled “GitHub Pages errors”

”Permission denied” / 403

Section titled “”Permission denied” / 403”

Your personal access token doesn’t have repo scope. On GitHub:

  1. Go to Settings → Developer settings → Personal access tokens.
  2. Create a new token with the repo scope checked.
  3. Update the token in Swebsy → Settings → Deployment.

”Repository not found” / 404

Section titled “”Repository not found” / 404”
  • Check that the repository name matches the owner/repo format exactly (case-sensitive).
  • If the repository is private, ensure your token has access to private repos.

Site is blank or shows a 404 after deploy

Section titled “Site is blank or shows a 404 after deploy”
  • GitHub Pages can take 1–3 minutes to activate on first deploy.
  • Check the Actions tab in your repository — GitHub may have a Pages deployment in progress.
  • Verify that the gh-pages branch was created and contains your site files.

Cloudflare Pages errors

Section titled “Cloudflare Pages errors”

”Authentication error” / 401

Section titled “”Authentication error” / 401”

Your API token has expired or lacks the required permission:

  1. Go to Cloudflare → My Profile → API Tokens.
  2. Create a new token with Account → Cloudflare Pages → Edit permission.
  3. Paste it into Swebsy → Settings → Deployment → Cloudflare Pages.

”Project not found”

Section titled “”Project not found””

Swebsy creates the project on first deploy. If the project name in Swebsy differs from an existing project, a second project is created. Check your Cloudflare dashboard and delete the duplicate, or align the project names.

Deploy times out

Section titled “Deploy times out”

Very large sites can exceed Cloudflare’s Direct Upload time limits. Try:

  • Reducing image sizes (compress before uploading)
  • Removing unused pages and assets

General export errors

Section titled “General export errors”

Export hangs indefinitely

Section titled “Export hangs indefinitely”

Tailwind compilation is CPU-intensive. On older hardware, a large site may take 30–60 seconds. Wait for the modal to resolve. If it never resolves, reload and try again.

Zip file is empty

Section titled “Zip file is empty”

This is rare and usually indicates a memory issue in the browser. Reload Swebsy and retry the export. If it recurs, export the backup JSON first, then retry.