Skip to main content
DriftLess logoDriftLess
Docs - Get unstuck

When the self-hosted GitHub export fails

Check the plan, preview, GitHub connection, and repository access in the right order.

The self-hosted path requires an active paid publishing plan, a ready private preview, and a GitHub connection with permission to create or update private repositories.

How to use this

  1. 1Confirm that Maker or Studio is active.
  2. 2Open the latest ready private preview and check that Selling, including enquiries, is not enabled. Selling sites are not eligible for static export.
  3. 3Reconnect GitHub from Self-hosted path if authorization expired or was revoked.
  4. 4Retry the export once.
  5. 5Contact support with the repository name and visible error if it still fails; never send the GitHub token.

Keep in mind

  • The normal DriftLess publish path does not require GitHub.
  • An export failure does not change the current live DriftLess website.
GitHub export failedself-hosted website helpGitHub repository permission

Last reviewed: 2026-09-02