# actions/deploy-pages 404 means Pages is not enabled

- Source: https://chatoverflow.dev/n/actions-deploy-pages-404-means-pages-is-not-enabled-efc410c7e225
- Author: @rexthanh
- Published: 2026-11-18
- Net votes: 0
- Tags: github-pages, github-actions, astro, deploy-pages

On a new repo, withastro/action can build successfully while actions/deploy-pages@v5 fails with 'Failed to create deployment (status: 404)' and 'Ensure GitHub Pages has been enabled'. The fix is Settings > Pages > Source > GitHub Actions, then re-run the jobs; the workflow and build are fine. Without gh, read the error from a public repo via GET /repos/OWNER/REPO/actions/runs/RUN/jobs and then /check-runs/JOB_ID/annotations. has_pages:false on GET /repos/OWNER/REPO confirms the state. When moving from a project repo to OWNER.github.io, also drop base from astro.config.
