How to fix HTTP 404 on Github Pages

Question

Here is my GitHub repository on the gh-pages branch  Everything looks good  I have my index html  my CSS  JS and pictures folders   But when I access http   roine github com p1 I get HTTP 404 not found   Any explanation and solution

User · Answer

Add the following in the beginning of the index html file   lt  DOCTYPE html gt

User · Answer

Another variant of this error    I set up my first Github page after a tutorial but gave the file readme md a - from my perspective - more meaningful name  welcome md    That was a fatal mistake       We   ll use your README file as the site   s index if you don   t have an   index md  or index html   not dissimilar from when you browse to a   repository on GitHub    from Publishing with GitHub Pages  now as easy as 1  2  3  I was then able to access my website page using the published at link specified under Repository   Settings   GitHub Pages followed by welcome html or shorter welcome

User · Answer

I had just one commit with all my files  I pushed an empty commit  refreshed the page and it worked   git commit --allow-empty -m  Trigger rebuild  git push   If this doesn t work  as  Hendrikto pointed out in the comments  check out the Github status page and make sure GitHub Pages are operational

User · Answer

In my case my repository was private  Make repository public and go through all steps again

User · Answer

In my case  I had folders whose names started with    like  css and  js   which GH Pages ignores as per Jekyll processing rules  If you don t use Jekyll  the workaround is to place a file named  nojekyll in the root directory  Otherwise  you can remove the underscores from these folders

User · Answer

I faced the same issue 404 on a newly set up GitHub pages website  yesterday  I tried many methods such as switching a new theme etc  But it seems that it still did not work on my case  I finally figured it out by switching the branch of GitHub pages website to another branch  click save  Wait for a while and switch it back again  Then the problem was suddenly solved

User · Answer

I faced this problem  404  too and the root cause was my file was named INDEX md  I was developing on Windows and my local Jekyll site worked  since Windows treats file names case insensitive by default   When pushed to Github  it didn t work  Once I renamed the INDEX md to index md  things worked well

User · Answer

Also  GitHub pages doesn t currently support Git LFS  As such  if you have images  or other binary assets  in GitHub pages committed with Git LFS  you ll get 404 not found for those files   This will be quite common for documentation generated with Doxygen or similar tool   The solution in this case is to simply not commit those files with Git LFS

User · Answer

For some reason  the deployment of the GitHub pages stopped working today  2020-may-05   Previously I did not have any html  only md files  I tried to create an index html and it published the page immediately  After removal of index html  the publication keeps working

User · Answer

The solution for me was to set right the homepage in package json  My project name is monsters-rolodex and I am publishing from console gh-pages -d build   quot homepage quot    quot https   github com monsters-rolodex quot    The project was built assuming it is hosted at  monsters-rolodex    Before it didn t work because in the homepage url I included my github username

User · Answer

I bound my domain before this problem appeared  I committed and pushed the branch gh-pages and it solved my problem  New commits force jekyll to rebuild your pages

User · Answer

If you haven t already  choose a Jekyll theme in your GitHub Pages settings tab  Apparently this is required even if you re not using Jekyll for your Pages site

User · Answer

On a private repo  when I first added and pushed my gh-pages branch to github  the settings for github pages automatically changed to indicate that the gh-pages branch would be published  but there no green or blue bar with the github io url and no custom domain options    It wasn t until I switched the source to master and quickly switched the source back to gh-pages that it actually updated with the green bar that contains the published url

User · Answer

Four months ago I have contacted  the support and they told me it was a problem on their side  they have temporarily fix it  for the current commit    Today I tried again    I deleted the gh-pages branch on github  git push origin --delete gh-pages I deleted the gh-pages branch on local  git branch -D gh-pages I reinitialized git  git init I recreated the branch on local  git branch gh-pages I pushed the gh-pages branch to github  git push origin gh-pages   Works fine  I can finally update my files on the page

User · Answer

Just wait about ten minutes to one hour  If it still doesn t work  contact github  Usually it s the problem at their end  But  if you re in a hurry  you can try to open by adding     question mark at the end of URL  It force query to search for the resource  Like this   http   roine github com p1

User · Answer

In my case  all the suggestions above were correct  I had most pages working except few that were returning 404 even though the markdown files are there and they seemed correct  Here is what fixed it for me on these pages     On one page  there were a few special characters that are not part of UTF-8 and I think that s why GitHub pages was not able to render them  Updating removing these char and pushing a new commit fixed it   On another page  I found that there were apostrophes   surrounding the title  I removed them and the page content started showing fine

User · Answer

In my case  the URL was quite long  So  I guess there is a limit  I put it to my custom subdomain and it worked

User · Answer

I did all the tricks here on My Fork to fix page 404 on Github Page but it kept 404 ing     Finaly found that my browser hardly keep the 10 minutes cache before it up on the web   Just add  index html into the end of URL then it showed up and solved the case      https   username github io index html

User · Answer

I was following this YT video  So  when I ran the command in my terminal  it pushed the code to gh-pages branch already  Then I pushed to the master branch  It was giving me 404 error  Then I swapped the branch to master and then again reverted to gh-pages and now the error is gone  It s pointing to the index html even if it s not in the URL

User · Answer

I got the site to work by deleting the  username github io  folder on my computer going through the steps again  including changing the index html file   My mistake  I think  is that i initially cloned  https   github com username username github io git  instead of https   github com username username github io  no   git

User · Answer

If you saw 404 even everything looks right  try switching https http   The original question has the url wrong  usually you can check repo settings and found the correct url for generated site   However I have everything set up correctly  and the setting page said it s published  then I still saw 404   Thanks for the comment of  Rohit Suthar  though that comment was to use https   I changed the url to http and it worked  then https worked too

User · Answer

In my case in react was necessary to select the gh-pages branch

User · Answer

in my case i had to go to project settings and enable the github pages  The default is off

User · Answer

I had same issue   Very strange issue   My HTML was with space after title   gt   lt title gt   gt    gt   lt script gt    Fixed  after removing space   gt   lt title gt   gt   lt script gt

User · Answer

I also faced this issue  my pages getting 404  And then I added README md on my repository  and the 404 was gone

User · Answer

If you are sure that your structure is correct  just push an empty commit or update the index html file with some space  it works

User · Answer

I was facing the same issue  after trying most of the methods mentioned above I couldn t get the solution  In my case the issue of because of Github changing the name of master to main branch  Go to Setting - gt  go to GitHub Pages section and change the branch to main   to  Save it and select a theme  and the website is live

User · Answer

In my case the browser had a previous cached version of my app  To avoid getting the cached version  access you url using a random query string  https     your-username   github io   your-repository   randomquery

User · Answer

I had to rename my repo to a random name then rename it back to it s original name for it to work  Seems like it might be a GH Pages bug

User · Answer

Yet another scenario    using an Organization Page  not a Project page  that has a repository named  lt orgname gt  github io source documents as markup in master branch  asciidoc  Travis CI pulling source doc files from master and pushing generated html files to gh-pages branch   The gh-pages branch is updated with the generated html pages  The GitHub Environment tab provides the link to the organization page  Clicking it results in a 404   According to https   help github com articles configuring-a-publishing-source-for-github-pages      User and Organization Pages that have this type of repository name are   only published from the master branch   If I understand this correctly  GitHub Pages will not be published from the gh-pages branch if you are creating a User or Organization site rather than a Project site   I renamed my repo to make it a Project site rather than Organization site and then the gh-pages branch was published as expected

User · Answer

In my case on 8 Aug 2017   if your user page is https   github com mgravell  you repo name must be mgravell github io under root  create a file index html under root  create a folder docs  create a file CNAME under docs  note  NO extension like  txt  make sure your file system shows extension  gh-pages branch is optional  master branch is sufficient   more  check official docs here  https   help github com articles configuring-a-publishing-source-for-github-pages

User · Answer

My pages also kept 404 ing  Contacted support  and they pointed out that the url is case sensitive  solved my issue

User · Answer

I had the same issue after forking a repo with a gh-pages branch  I was able to fix by simply pushing a new commit  just whitespace in index html  to my fork s gh-pages branch

User · Answer

Go to settings section of your repository and choose master branch at the Source section and click save button after that refresh the page and you will be able to see the link of your page

User · Answer

I had this exact problem with typedocs  The README md worked but none of the actual docs generated by my doc strings displayed  I just got a 404 Github Pages screen   To fix this  just place a empty file in your  docs directory  or wherever you generate your docs   amp  call it  nojekyll  To confirm  your file structure should now look like     docs  nojekyll    plus all your generated docs   Push this up to your remote Github repo and your links etc should work now   Also make sure you have selected in your Github settings   Settings - gt  Github Pages - gt  Source - gt  master brach  docs folder   Depending on your doc framework  you probably have to recreate this file each time you update your docs  this is an example of using typedocs  amp  creating the  nojekyll file each time in a package json file     package json         scripts              typedoc    typedoc --out docs src  amp  amp  touch docs  nojekyll

[github] How to fix HTTP 404 on Github Pages?

Examples related to github

Examples related to github-pages