Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 31 of 40

Re: pages user site not published

I have the same problem that a lot of people are having, but don't see how it is getting fixed.

I was hoping to use the address <username>.github,io,

I first tried creating the pages in a repository called /docs, but under settings -> GitHub pages -> Source,

the option to use docs as the source was greyed out.  Then I tried creating a repository

<username>.github.io, and when I do that, under settings -> GitHub pages -> Source, rather than

giving me a menu, it says that "Your GitHub Pages site is currently being built from the master branch"

and above that it says "Your site is ready to be published at http://<username>.github.io/"

Sounds good, but when I click that link I get a 404 page.  I'm sure I'm missing something

(maybe "ready to be published" is different that "published" and I need to do something else),

but I don't know what.

Any ideas?

 

Highlighted
Copilot Lvl 2
Message 32 of 40

Re: pages user site not published

Well, never mind.

After I changed the name to my repository, I had to make a commit before it would get published.  But not it's up.

Highlighted
Copilot Lvl 2
Message 33 of 40

Re: pages user site not published

Did you figure out the issue? I'm having the same one :O

Highlighted
Copilot Lvl 2
Message 34 of 40

Re: pages user site not published

I assume you were able to push the code successfully to the repo.

Make sure the following things are in place:
1. Angular Cli Version should be 8+.
2. Repo should be public and not private - navigate to settings and change the repo to public.
3. Try the following command: ng deploy --repo=https://github.com/<userID>/<repoName> --base-href=https://<userID>.github.io/<repoName>/

In the settings page, you'll get the generated link.
Check the network tab to see if the bundles are being loaded successfully, else clear the cache once and try : ctrl + shift + R.

Highlighted
Ground Controller Lvl 1
Message 35 of 40

Re: pages user site not published

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.

Highlighted
Ground Controller Lvl 2
Message 36 of 40

Re: pages user site not published

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

..
Highlighted
Ground Controller Lvl 2
Message 37 of 40

Re: pages user site not published

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?

Highlighted
Ground Controller Lvl 1
Message 38 of 40

Re: pages user site not published

For those who still are having problems,

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

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

 

Hope it helps.

Highlighted
Ground Controller Lvl 1
Message 39 of 40

Re: pages user site not published

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.

Highlighted
Ground Controller Lvl 1
Message 40 of 40

Re: pages user site not published

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.