Thank you

When you encounter a 404 error on your GitHub Pages site, it usually means that the server couldn't find the requested page. This can happen for a few reasons, but don't worry, we'll work through them step by step.

Here's a guide to help you troubleshoot those pesky 404 errors:

Check Your File Paths: The first thing to do is make sure your file paths are correct. Double-check that you've specified the right file names and folder locations in your URLs and links. Remember, GitHub Pages is case-sensitive, so "Page.html" and "page.html" are considered different files.

Branch and Directory Settings: If your site isn't showing up, make sure that the branch you're using for GitHub Pages is correct. Also, confirm that your site's main HTML file (like "index.html") is in the root directory of your repository.

Wait for Changes to Reflect: If you've recently made changes to your site, remember that it might take a little time for those changes to be visible due to caching. Give it a bit of time, or try clearing your browser cache.

GitHub Pages Build: Sometimes, a 404 error might be caused by a problem during the GitHub Pages build process. Make sure your repository has been successfully built. You can check the "Settings" tab in your repository for GitHub Pages build logs.

Link Errors: If you're linking to external resources like CSS, JavaScript, or images, ensure that the URLs are correct. An incorrect link could lead to a 404 error.

File Extensions: GitHub Pages often assumes that files like "Page.html" should be accessed as "page.html". Check if your file extensions and URLs are consistent.

Repository Permissions: Ensure that your repository is public if you intend for your GitHub Pages site to be accessible to everyone. Private repositories won't be visible to the public.

Custom Domain: If you're using a custom domain, make sure your DNS settings are properly configured. Incorrect settings could lead to 404 errors.

Typos in URLs: It's easy to overlook typos in URLs. Make sure there are no typos in your links and URLs that could be causing the issue.

GitHub Status: Occasionally, GitHub itself might experience issues that can result in temporary disruptions. You can check the GitHub Status page to see if there are any ongoing problems.

By following these steps, you should be able to narrow down the cause of the 404 error on your GitHub Pages site and get it back up and running smoothly.

Please add another reason is that your folders may start with _ (underscore), for example Blazor's _framework and _content. You have to add a .nojekyll file into your root directory.

Credit to mpetrovich/stylemark#65.

I'm trying to deploy a web page with react and vite, I've followed all the steps you mentioned before but I still have a 404 response :/

Hello everyone
I hope my messge finds you well.
I am new in github. I have been trying to publish my assignment for a few hours now. The adress I want to visualise should be this one:
https://anoma3.github.io/module5-solution/index.html
It worked for my previous assignments, but this time I get a 404 error and I do not understand why.

My repository is there:
https://github.com/anoma3/module5-solution

Could you help me please?

It's not working! It's driving me crazy!
Ur static page stuff is broken.
static.yml

*Simple workflow for deploying static content to GitHub Pages
name: Deploy static content to Pages

on:

• Runs on pushes targeting the default branch
  push:
  branches: ["main"]

• Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

• Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
  permissions:
  contents: read
  pages: write
  id-token: write

• Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.

• However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
  concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:

• Single deploy job since we're just deploying
  deploy:
  environment:
  name: github-pages
  url: ${{ steps.deployment.outputs.page_url }}
  runs-on: ubuntu-latest
  steps:
  • name: Checkout
    uses: actions/checkout@v4
  • name: Setup Pages
    uses: actions/configure-pages@v4
  • name: Upload artifact
    uses: actions/upload-pages-artifact@v3
    with:
    • Upload entire repository
      path: '.'
  • name: Deploy to GitHub Pages
    id: deployment
    uses: actions/deploy-pages@v4

I don't know, but it says I don't have the rights to change some things...

Error: .github#L1
actions/checkout@v4, actions/configure-pages@v4, actions/upload-pages-artifact@v3, and actions/deploy-pages@v4 are not allowed to be used in gitmonkey/gitmoneky.github.io. Actions in this workflow must be: within a repository owned by gitmonkey.

IM THE ... OWNER!!! What's happen?
I've configured all the rights and options, it's on the main branch, and I've checked everything, but none of it seems to be working. It's really frustrating.

Now, I'm utilizing the old version I had stored. However, when attempting to operate with version v4, it feels like colliding my head against the hard wall of reality, as it simply doesn't function.

use this!
deploy.yml

name: Deploy to GitHub Pages

on:
push:
branches:
- master

jobs:
build:
runs-on: ubuntu-latest

steps:
  - uses: actions/checkout@v2
  - name: Install dependencies
    run: |
      npm install
  - name: Build and deploy
    run: |
      npm run build
      npx gh-pages -d build

Please fix this fast! it's the worst for newbies :(

I am getting a 404 error about my page not being found. It has been working for quite a while and I haven't made any updates to my page since 5 months ago and it all of a sudden stopped working. Has something change in the last few months with the structure?

Hi, can you add a guide about .nojekyll to the 404 docs and add it with the first post of this discussion? I was trying to deploy my Avalonia WASM project and was held up for a long time until I saw the reply from @datvm which solved the issue. I had also gone through the docs before, but there were no relevant instructions in there :(
This entry would help people like me who are looking to deploy Avalonia/Blazor.

I am getting 404 error still everything is made correct, i have index.html and main branch as default still i am getting this error it is worked before. but it is not working now?

Thanks for putting together this awesome guide on tackling those pesky 404 errors. Mind if I chip in with a few more ideas? I've banged my head against this wall a few times, so here are some extra things to check that might save someone else a headache:

Jekyll being Jekyll: If you're using Jekyll (which a lot of us do), sometimes it throws a fit. Check your build logs for any drama, and make sure your Gemfile and _config.yml are playing nice.
File permission shenanigans: This one's a bit techy, but sometimes file permissions get wonky. Make sure your files are set to 644 and folders to 755. It's like making sure everyone has the right backstage pass to your site.
The sneaky .gitignore: Ever added something to your .gitignore and then wondered why it's not showing up? Yeah, been there. Maybe take a peek and make sure you haven't accidentally told Git to ignore something important.
Size matters: Did you know GitHub Pages has a size limit? 1GB for the whole repo and 100MB per file. If you're going big, you might need to trim things down a bit.
Case sensitivity chaos: This one's bitten me before. GitHub Pages is super picky about uppercase and lowercase. So index.html and Index.html are totally different things to it. Double-check all your file names and links!
The cache strikes back: Sometimes your browser is just showing you old stuff. Try hard refreshing (Ctrl+F5 usually does the trick) or open an incognito window to see if that fixes things.
Path problems: If you're working on a project page (like username.github.io/coolproject), make sure all your links include the project name. It's easy to forget and end up with broken links all over the place.

Hope these extra tips help someone out there avoid pulling their hair out over a 404! If anyone's still stuck after all this, don't be shy