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 branch selected in Swebsy was created and contains your site files.

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.