Replies: 8 comments 8 replies
-
|
GitHub Pages can’t read your deployment data correctly — likely a small config or build issue. Double-check your output folder, workflow config, and branch. update your workflow to use: - uses: actions/deploy-pages@v4Quick fix steps: Re-run your workflow with “Rebuild and redeploy”. |
Beta Was this translation helpful? Give feedback.
-
|
Additional checks:
So it looks to me more a permission problem, but I have not clue... For the record, my yaml file is pretty standard, used to work just out of the box! : |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi @queenofcorgis , I read your page about 404 errors on GH pages |
Beta Was this translation helpful? Give feedback.
-
|
The Root CauseThe error occurs because GitHub Pages recently made changes to how deployment artifacts are validated. The error "Failed to create deployment (status: 422)" specifically indicates that the deployment API is rejecting the artifact payload. Common Causes:1. Pages Deployment API ChangesGitHub Pages changed some internal validation rules. The 2. Pages Not Enabled CorrectlyGo to your repository Settings → Pages and verify:
3. Artifact Size or Structure IssuesThe artifact might exceed size limits or have an unexpected structure. Solutions to Try:Solution 1: Update Your Workflow to Use Latest Stable VersionsInstead of relying on Pelican's workflow, try creating your own workflow with explicit versions: name: Deploy Pelican to GitHub Pages
on:
push:
branches: ["main"]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Install Pelican
run: pip install 'pelican[markdown]'
- name: Build site
run: pelican content -s publishconf.py
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: 'output/'
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4Solution 2: Verify Pages Settings
Solution 3: Check Repository Environment SettingsThe deployment might be failing due to environment protection rules:
Solution 4: Re-enable PagesSometimes the Pages service gets into a weird state:
Solution 5: Use
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @justinmayer, I notice you made a commit two weeks ago on the Pelican" Deploying to GH pages" yaml file: |
Beta Was this translation helpful? Give feedback.
-
|
It seems that recent changes in the That said, I don’t use GitHub Pages myself, I am not the best person to ask about this. What do you think, @seanh? |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thanks to all that have answered, I think I found the problem:
So I tried making it public and re-run the jobs, and everything was fine, pages back online. The things is: that seems to be a recent change (or is it, @queenofcorgis ?), because my website has been build from a private repo since the beginning, and I don't think I had any notice from GH that they changed their policy on that topic! To be clear: I perfectly understand the fact that GH can change their policy anytime and decide to charge user for a given service. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi,
I have some static pages, built with Pelican, but I notice that there is a deployment failure on Github pages.
The "build" step runs fine.
It used to work perfectly before (a couple of years), I don't think I've done anything significant in between.
After rerun the failed deployment with debug options, I have a
HttpError: Validation Failederror:line 60:
And the URL on github.io returns a 404?
The status pages (https://www.githubstatus.com/) says there are no problems with Pages.
I don't understand what the problem is.
Anybody has an idea of further steps I can try?
Beta Was this translation helpful? Give feedback.
All reactions