GitHub Pages "Get Pages site failed" (Pages not enabled)

By Kaveh Alemi·Latchkey

The configure-pages action queries the Pages site for the repository. If Pages is disabled, or its source is not set to GitHub Actions, the lookup fails before any artifact is built. This is a settings issue, not a flake.

What this error means

The actions/configure-pages step fails reporting it could not get the Pages site, often with a 404 from the Pages API.

Error: Get Pages site failed. Please verify that the repository has Pages enabled
and configured to build using GitHub Actions. (HttpError: Not Found)

Common causes

Pages disabled for the repository

No Pages site exists yet, so the API returns 404 when the action looks it up.

Source not set to GitHub Actions

Pages is set to deploy from a branch instead of from GitHub Actions, so the Actions build path is not configured.

How to fix it

Enable Pages with the Actions source

1. In Settings > Pages, set Build and deployment Source to GitHub Actions.
2. Or let configure-pages enable it by setting enablement: true (requires pages: write).
3. Re-run the workflow once Pages is enabled.

- uses: actions/configure-pages@v5
  with:
    enablement: true

How to prevent it

• Set the Pages source to GitHub Actions before running the deploy workflow.
• Grant pages: write and id-token: write on the deploy job.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions