Gitlab Pages: 404 for even the simplest setup

@aggieben is your project’s name also benjamincollins.com? This is what you should use as a Pages URL. You can also find the URL by going to the Pages page.

Problem: I created a new GitLab project site as per instructions on https://docs.gitlab.com/ee/user/project/pages/#getting-started and mapped a custom domain as per instructions on https://docs.gitlab.com/ee/user/project/pages/getting_started_part_three.html#adding-your-custom-domain-to-gitlab-pages and still faced a similar issue as listed on this thread. I could access my website as http://mydomain.com but got a GitLab 404 error page when I tried to access my website as www.mydomain.com (my site does not have SSL).

Solution: Under my GitLab project site left navigation bar, I went to “Settings” -->? “Pages” and followed the instructions on https://docs.gitlab.com/ee/user/project/pages/getting_started_part_three.html#adding-your-custom-domain-to-gitlab-pages to add TWO domains viz. mydomain.com and www.mydomain.com. Both these domain names created on GitLab had DIFFERENT verification codes. On my Domain Management Control Panel, I added TWO entries of type TXT:
(1) Type: TXT, Name: T_gitlab-pages-verification-code.mydomain.com, Value: corresponding code taken from my GitLab page domain settings page.
(2) Type: TXT, Name: T_gitlab-pages-verification-code.www.mydomain.com, Value: corresponding code taken from my GitLab page domain settings page.
After the above two entries in GitLab and Domain Control Panel I could now access my website with both URLs viz. http://mydomain.com and www.mydomain.com.

Hope this helps others facing the same problem.

ResumeFodder problem: As per the original problem listed on this issue (https://gitlab.com/gitlab-com/support-forum/issues/569) I tried in my browser and see that the website is reachable as https://resumefodder.com but not as https://www.resumefodder.com. Looks like that problem is not solved for ResumeFodder till date after couple of years since this issue was originally posted. My site did not have httpS compared to ResumeFodder. However, ResumeFodder owner may want to try if my above solution works and www.resumefodder.com also starts working.

Thanks!

This is absolutely pathetic. People waiting several days for a website to how up, yet no help from actual admins from gitlab. I’m also in the same boat, forked a hugo project and under “pages” there is no page. Going to myusername.gitlab.io just gives me 404.

I just wasted hours, checking several guides and everything and I just need to “wait”? There is no information on the official pages regarding the “wait” part. Pathetic.

1 Like

@acc Ehi man, don’t be so stressed out. In a way or another they’re gonna figure that out. If you’re in a hurry you can set up an automatic deploy to a another hosting (e.g. shared hosting via ftp, Google App engine, ecc…).

It’s disappointing that sometimes it works sometimes it’s not. Initially, I observed that it takes a while before my site loads but its been taking hours now. The CI/CD went succesffuly, including deploying pages. A link is available in Settings/Pages but i always received 404. I must admit it’s kinda annoying.

Thinking of moving to S3, GH or Azure Storage.

I hope GL team can figure this out soon. Thanks still, it’s cool platform just little brittle.

Solution:

gitlab pages are slow to appear/update. How “slow” is slow depends on the current state of the infrastructure. It’s about 15 minutes to half an hour at the moment of writing.

I don’t have enough privileges to mark another comment as a solution, but I wanted to make it clear since this is the first thing that comes up googling “gitlab pages 404”

6 Likes

I’m experiencing this issue at the moment with, www.absolutejam.co.uk and absolutejam.co.uk, but blog.absolutejam.co.uk loads fine. Obviously this is still an issue because my URLs all point to absolutejam.co.uk, but the strange part is that all of the CSS etc. is loading using absolutejam.co.uk (eg. http://absolutejam.co.uk/css/main.css), but pages do not.

The first 2 domains had been associated with another repo previously, but not for a little while.

All domains are verified and have the same DNS configuration.

Yeah, that’s an issue with large Pages setups, so if you use .gitlab.io, new Pages take 10-15 minutes to show up. Subsequent changes are almost instant though.

I’ve just encountered this again and like you said, googled “gitlab pages 404”. Then I saw that it was me that wrote the initial post. :joy:

I swear that your own thoughts have a half-life of about one month.

Thanks for reiterating that initial gitlab pages are slow to propagate. :slight_smile:

1 Like

so, now do you have a good ideas for how to fix this 404 about gitlab, my email is elasticsearch@163.com, if you had solved it , please gave me a email ? thank you very much!!!

I am suprised that it takes really a veyr long time. Anwya, thanks for clearifying the issue.

I hit this 404 issue twice yesterday.
I noticed once I download the artifacts from the pages job, then the page begin to show!
It seems like the download triggered something?
Can anyone else confirm this?

2 Likes

exactly the same issue at this moment

1 Like

That worked for me too. Could be a coincidence, but weird.

If this is a known issue then could a note about it be added to the Pages Settings where it says “Congratulations!”?

2 Likes

404 error: “It takes couple of minute to start!
why?
Because behind the scenes, gitlab is running instructions mentioned in .gitlab.ci.yaml in their server… now, since you’re not the only one doing this and there could be several people trying more or less same, you’ll be queued… when the server is available, it’ll pick up your task and execute

1 Like

404 error: “** It takes couple of minutes to start! **”
why ?
Because behind the scenes, gitlab is running instructions mentioned in .gitlab.ci.yaml in their server… now, since you’re not the only one doing this and there could be several people trying more or less same, you’ll be queued… when the server is available, it’ll pick up your task and execute

There are many which get the same problem just to mention they have this problem.
As mentioned by others before in this discussion.
Be patient and the site will come up after about 15 to 30 minutes.

same +1 :pensive:

+1 Same here. I have waited more than an hour.