Gitlab Pages: 404 for even the simplest setup

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?

1 Like

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!”?

1 Like

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.