6
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Sep 2024
6 points (100.0% liked)
WebDev
1154 readers
1 users here now
Community for all things Web Development related.
founded 1 year ago
MODERATORS
Do you have:
www.domain.com
domain as well?www.domain.com
For your error, it's probably the first one. When the traffic comes in under
www.domain.com
, there's no virtual server configured to listen on that hostname and it's likely falling back to a default response.Not sure how that works with Github pages, but in general, that's usually what it is.
It wouldn't be the first time that Gitlab documentation[1] contradicted reality, but I don't see an option in Gitlab Pages to achieve what you describe.
1: https://docs.gitlab.com/ee/user/project/pages/custom_domains_ssl_tls_certification/#redirect-wwwdomaincom-to-domaincom-with-cloudflare
Ah. Looks like Gitlab just does a redirect versus serving the same content under both domains.
Assuming you followed all the steps, then I'm not sure what the problem could be.
Thanks. I followed them as closely as possible. Their instructions are for Cloudflare whereas I'm using Letshost. But Letshost haven't figured it out either since I notified them.