pages user site not published

Posting this reply because I ran into the same problem and using the response marked as a solution did not work for me.

To publish my page, I followed the steps in here:

I got a 404 error when I navigated to <username><repo-name>

What worked for me was
-ensuring my repo was public
-changing the name of my repo to a new name (to repo-name2 for example) and then
-updating the package.json file with “homepage”: “http://<username><repo-name2>”
-then running npm run deploy command again

this fixed the problem for me.


You need to chooose a theme in settings.  Click ‘Change theme’ and choose one.



Thank you! Worked for me.

I also had the same problem like this last week and when using an incognito mode, everything was fine.

My 404 problem was fixed when I called my repository the same as my username.


1 Like

Thank you SOOOOOOOOO much! This is the piece of info that totally helped me! 

I tryed both of solution but it still not working. It shows following.

thanks so much

this is the real solution. Thanks it worked for me

I’m still having problems.

I’ve had my site for years. I just upgraded my Pelican.

In settings, I’m serving from gh-pages. My generated code is in gh-pages.

I’ve selected a Jekyll theme (why do I need to select a Jekyll theme for a Pelican blog? I’ve never had to do this before.)

My site is still serving the content from before I updated and pushed the new, generated code.

What do I do?

Thanks it worked.

For those who still are having problems,

I faced the same issue. I published my github pages site and then visited as advised in the docs but got 404 not found error as everyone.

But, the actual working link is:
i.e. https://<username><reponame>/ 
wherereponame is same as <username>

Hope it helps.

1 Like

This solved the problem, thank you so much!

@osaimola Thanks bud, well done :slight_smile:

When you upload your files to GitHub, make sure you upload them individually, do not upload the whole folder; I discovered that was the reason behind my page not loading initially. It’s worth giving that a try.

This is real …It worked !!! Thank You

But I have another issue …the main file i.e., index.html worked but as I click in my login and Signup button only the html files open not the css.

Another thing-- I believe if you add collaborators on your hosting repo, the site will be hidden to the public. Revoke your collaborators’ permissions under Settings -> Manage Access.

my issue solved by switching from master to working branch, issue was generating while running command npm run deploy.

I had the same issue. This is happening because there is only one commit, i.e the initial commit in the repository. You can get gh-pages to redploy by having a minor change in your index.html file,addition of  a blank space will do.

After that commit ,

git commit --allow-empty -m "Trigger rebuild"

And push.

Wait for gh-pages to redploy.

I don’t have package.json file in my repo