Deployed to Gitlab Pages, still unavailable after more than 12 hours

aknudsen · July 10, 2019, 7:31am

I successfully deployed a Hugo blog project to GitLab Pages yesterday, but even after 12+ hours it isn’t available, i.e. its designated URL 404s.

Could anyone help me troubleshoot why it won’t come up? AFAICT, I’ve done everything correctly.

aknudsen · July 11, 2019, 9:29am

I was able to get it published now - I can’t tell for sure, but I’m pretty certain it’s because I changed the project’s visibility to public instead of private. I also had to make another deploy after making it public, before it came up. I noticed the same behaviour with another project, so I guess this more or less confirms that there’s a bug with GitHub Pages and private projects?

tjwilliams · July 11, 2019, 10:33pm

@aknudsen Welcome to the forum!

The visibility level of the project shouldn’t matter as the deployment will be public regardless. On your first deployment there is usually a delay of ~30 minutes or so that we’re working on reducing, but I’ve never personally seen it take longer than that.

aknudsen · July 12, 2019, 6:42am

But I saw that it took more than a day, and it only got published after I changed visibility to public and redeployed. I also experienced a previous project to only get published after I changed its visibility to public. Is this purely coincidence?

Have you tested publishing a private project to verify that it works?

gitlab-greg · July 15, 2019, 5:08pm

Hi @aknudsen,

A deploy time more than 30-60 minutes is abnormal. I’ve never seen it take longer than a couple hours. Has this happened before?
I’m not sure why it would take this long, but I can confirm that Private projects are visible in Pages form.

This Private Jekyll project was forked and deployed to pages in ~5 minutes: https://greg.gitlab.io/jekyll/

A fork of your personal-blog project, also set to private was built and deployed on GitLab Pages in ~20 minutes:

I deleted this fork after testing, but here’s a screenshot:

I can confirm that setting a project to “Private” will not limit the accessibility of the GitLab Pages deployment.

aknudsen · July 15, 2019, 6:19pm

hi @gitlab-greg, it has happened to me once before, and then I experienced the same thing, i.e. that I had to make the project public and re-deploy it before it was published. Is there any way to see why GitLab hasn’t published a project yet?