Skip to content

Update getting_started_part_three.md section for the GitLab Page alias / domain…

What does this MR do?

Submitting this Merge Request after discussing with Mark Fletcher to provide additional explicit clarification about GitLab Page Alias / Domain settings and corresponding TXT type DNS entries required to ensure that both URLs http://domain.com and www.domain.com reach the same website. If only one set of entries made per the previous instructions then the other URL displays a GitLab 404 Page Not Found error.

Are there points in the code the reviewer needs to double check?

In the alias / domain entries section, I have added this additional instructions: If you are expecting that both URLs www.domain.com and http://domain.com reach your website then kindly note that they require two "New Domain" entries in your GitLab project Pages settings (you'll need navigate to your project's Setting > Pages and click + New domain to add your custom domain to add domain.com and then repeat the steps to add www.domain.com to your GitLab Pages). Correspondingly, two TXT type DNS entries will be required with the two verification codes on your Domain Management Control Panel. For example: (1) Type: TXT, Name: T_gitlab-pages-verification-code.domain.com, Value: corresponding code taken from your GitLab page domain settings page. (2) Type: TXT, Name: T_gitlab-pages-verification-code.mydomain.com, Value: corresponding code taken from your GitLab page domain settings page. If only one set of entry is made for let's say domain.com then the other URL www.domain.com displays a GitLab 404 page not found error. But after the above two entries in GitLab and Domain Control Panel you can now access your website with both URLs viz. http://domain.com and www.domain.com.

Why was this MR needed?

I followed the instructions to create a new site but my domain could be accessed only with one URL http://domain.com while the other URL www.domain.com displayed a GitLab 404 page not found error message. It required a lot of research on past issues reported on GitLab forum and various trial and error iterations before I figured out the above solution. The above explicit instructions will help everyone going forward as all of us would normally expect our domain to be reachable with both the above URLs.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

I reported this issue no. 3151 and discussed with Mark Fletcher - https://gitlab.com/gitlab-com/support-forum/issues/3151

Also, issue no. 569 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.

Closes https://gitlab.com/gitlab-com/support-forum/issues/3151

Edited by Mark Fletcher

Merge request reports