Github pages doesn't update & 404 errors for some posts

[nohchunsam]

Hello, I'm using github page for my blog.
I'm using Chirpy(Jekyll) theme.
I noticed the github deployment didn't work yesterday, but as I saw it is resolved, I tried to deploy it...
However, it didn't updated new posts. Moreover, if I click old posts it goes to 404 error. It didn't show up yesterday.
I'm trying to find out how to solve this... or is this just github bug? The blog works well in local.

What I did

• my blog repository is public
• make empty commit and push
• clear cache of my browser
• check setting for my branch is correct
• searched similar discussion but it didn't worked (I'm not using custom host link)

[yaswanthteja]

Chirpy (Jekyll) blog works locally but fails to update on GitHub Pages, and old posts now lead to 404, it's likely related to GitHub Pages or Jekyll build problems, not a Chirpy or browser issue.

Things You've Already Done (Good!)
Repo is public

Pushed changes (with empty commit)

Cleared browser cache

Branch setting is correct

Not using a custom domain

Check GitHub Pages Build Logs
Go to: Repo → Actions → Pages build and deployment

See if there is any ❌ build failure or jekyll error.

⚠️ If you see something like Theme could not be found or 404 for _site, it means the GitHub build is broken.

2. Force Regenerate _site/ with GitHub Pages
   If you're using GitHub Pages (and not building it locally), ensure this is in your root repo:

✅ You have a _config.yml file

✅ You have no _site/ directory checked into your repo (GitHub builds it)

Make a dummy change and commit:

git commit --allow-empty -m "Trigger rebuild"
git push origin main

3. Ensure Correct Branch & Directory in Settings
   Go to: Settings → Pages

Ensure:

Source is set to GitHub Actions (or main / (root) if not using Actions)

No wrong folder like /docs selected

4. Check File Paths and Permalinks
   If old posts return 404:

Check _posts filenames are correct: YYYY-MM-DD-title.md

Check if permalinks or front matter changed recently in _config.yml

Confirm no .html extension is wrongly removed

5. Local Build Matches Remote Build
   Run this to simulate GitHub's environment:

JEKYLL_ENV=production bundle exec jekyll build

Make sure it doesn't break locally in production mode.

6. Switch to Build with GitHub Actions (Optional but Recommended)
   If GitHub Pages builds are flaky:

Use Chirpy Starter Template which builds using GitHub Actions.

Set Pages → Source to GitHub Actions.

[nohchunsam]

1. Check GitHub Pages Build Logs: Checked and no errors
2. Force Regenerate _site/ with GitHub Pages: checked config.yml file and no _site directory. Did empty commit, but no changes
3. Setting > Build and Deployment: Deploy from a branch - main - /(root)
4. one of my post file name is 2025-07-11-rive-ch2.md / I didn't change anything excepts adding goatcounter
5. Did local build and checked posts folder... and it worked in local. But not for github pages
6. Changed to github action (builds with jekyll) but it doesn't even build.

Thanks for help, but i'm still handling problems.... would it be problem of chirpy?

[soufyen004]

✅ 1. Verify Deployment Status on GitHub
Go to your repository → Actions tab.

Check the most recent GitHub Pages deployment.

Look for red ❌ or yellow ⚠️ in the build log. Even if the deploy step shows success, errors in the Jekyll build might prevent it from creating the correct files.

✅ 2. Force Rebuild
Sometimes GitHub Pages gets stuck. Try this:

bash
Copy
Edit
git commit --allow-empty -m "Trigger rebuild"
git push
You've done this already — but do it once again just to be sure after fixing _config.yml and any files you edit.

✅ 3. Check _config.yml Settings
Make sure these settings are correct in your _config.yml:

yaml
Copy
Edit
baseurl: "" # if your blog is at https://username.github.io
url: "https://username.github.io"
🔁 If your blog is in a subfolder, like https://username.github.io/blog, then baseurl should be /blog.

✅ 4. Make Sure _posts/ Folder Exists and Has Valid Posts
Posts should be named like YYYY-MM-DD-title.md

Each post must have a correct front matter, like:

yaml
Copy
Edit

title: My Post
date: 2025-07-18
categories: [Blog]

If the front matter is broken or missing title/date, Jekyll may skip it.

✅ 5. Check _site/ Is NOT Committed
If you ever manually committed the _site/ folder (used in local builds), it might conflict with GitHub Pages.

Make sure it’s in .gitignore

Delete _site/ and recommit.

✅ 6. Check GitHub Pages Branch and Folder Setting
Go to:
Repository → Settings → Pages
✅ Make sure it says:

Source: GitHub Actions (or main / master branch and / (root) or /docs folder if not using Actions)

✅ 7. Clear GitHub Pages Cache (Indirectly)
Unfortunately, there’s no official GitHub cache clear — but doing the following can force an update:

Change something in _config.yml (like add a comment)

Commit and push again

✅ 8. Check for Theme Update Issues
Sometimes Chirpy themes have breaking changes. If you updated the theme recently:

Compare _config.yml with the default from Chirpy’s latest version

Run bundle exec jekyll build locally and check for warnings/errors

✅ 9. Check Link Format (Old Posts 404)
If old posts give 404:

Check the permalink structure in _config.yml:

yaml
Copy
Edit
permalink: /posts/:title/
Make sure _posts filenames match the title.

Example:
_posts/2025-07-18-my-post.md → should be accessible at /posts/my-post/

✅ 10. Turn on GitHub Pages Build Logs (Optional)
Add .github/workflows/pages.yml to control builds (if not using it yet). Chirpy recommends GitHub Actions for deployment now.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬