<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=616259) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary I am attempting to utilise what [`work_items/28996`](https://gitlab.com/gitlab-org/gitlab-foss/-/work_items/28996) describes: automatic Let's Encrypt renewal. Due to [`work_items/3342`](https://gitlab.com/gitlab-org/omnibus-gitlab/-/work_items/3342), I have utilised my root domain, of `norfolkNeighbourhoodWatch.co.UK`. However, although domain validation has succeeded, I observe: > Something went wrong while obtaining the Let's Encrypt certificate. I have attempted to adhere to what [`lets_encrypt_integration.md`](https://gitlab.com/gitlab-org/gitlab/-/blob/ee9f4777d12b4e2f3da95593cc0e526cb353a4b1/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md#L1-130:~:text=Show%20all-,lets_encrypt_integration%2Emd,-6%2E03%20KiB) describes. However, its troubleshooting amounts to selecting the "Retry" button, when it fails. Due to what [`work_items/332214#note_2436872216`](https://gitlab.com/gitlab-org/gitlab/-/work_items/332214#note_2436872216:~:text=As%20you%20have%20closed%20the%20MR%2C%20can%20we%20close%20this%20issue%3F%20Thank%20you%2E) describes, I know that this is not because my project has somehow failed to be public; it is public. I had considered two alternatives: - [~] What concerns me is that [`work_items/525311`](https://gitlab.com/gitlab-org/gitlab/-/work_items/525311#note_3201011207:~:text=Based%20on%20the%20policy%20for%20inactive%20bugs%2C%20this%20issue%20is%20now%20being%20closed%2E) may apply here, although I have no idea how to check. - [~] I've no reason to believe that [`work_items/354722#note_873712018`](https://gitlab.com/gitlab-org/gitlab/-/work_items/354722#note_873712018) applies, but I am unable to confirm. However, in retrospect, it was because the domain included capital letters. Removing them resolved it. ### Steps to reproduce 1. I created [`gitlab.com/neighbourhood-watch-network/association-nfk/gitlab-profile`](https://gitlab.com/neighbourhood-watch-network/association-nfk/gitlab-profile). 1. I added a GitLab Pages configuration. 1. I deployed it. 1. I added a custom domain: `norfolkNeighbourhoodWatch.co.UK`. 1. I added its values to Hostinger: {width=900 height=221} 1. I waited for it to verify. 1. After it verified, when it failed to add an LE certificate, I selected “Retry”. 1. After it failed again, I removed the domain. 1. I added `norfolkneighbourhoodwatch.co.uk`, in its stead. ### Example Project [`gitlab.com/neighbourhood-watch-network/association-nfk/gitlab-profile/-/tree/4b58d46c8de1e8f860912f32ff7e2547d793cf8a`](https://gitlab.com/neighbourhood-watch-network/association-nfk/gitlab-profile/-/tree/4b58d46c8de1e8f860912f32ff7e2547d793cf8a/) ### What is the current *bug* behavior? When `norfolkNeighbourhoodWatch.co.UK` was added: - > Something went wrong while obtaining the Let's Encrypt certificate. - ~~~log 13:26:09.213 GET https://www.norfolkneighbourhoodwatch.co.uk/ NS_ERROR_UNKNOWN_HOST GET scheme https host www.norfolkneighbourhoodwatch.co.uk filename / Transferred0 B (0 B size) Request PriorityHighest DNS ResolutionSystem Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Encoding gzip, deflate, br, zstd Accept-Language en-GB Cache-Control no-cache Connection keep-alive Cookie SITES_NON_ESSENTIAL_COOKIES_CONSENT=1 Host www.norfolkneighbourhoodwatch.co.uk Pragma no-cache Priority u=0, i Sec-Fetch-Dest document Sec-Fetch-Mode navigate Sec-Fetch-Site none Sec-Fetch-User ?1 Upgrade-Insecure-Requests 1 User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:156.0) Gecko/20100101 Firefox/156.0 ~~~ ### What is the expected *correct* behavior? LE should apply a certificate, irrespective of capitalisation, because DNS is case-insensitive. ### Relevant logs and/or screenshots {width=735 height=600} ### Output of checks > This bug happens on GitLab.com > > @gitlab-bot label ~"reproduced on GitLab.com" > > @gitlab-bot label ~"type::bug" #### Results of GitLab environment info > GitLab Enterprise Edition `19.3.0-pre` 342d582a650 ### Possible fixes I have asked [`community.letsencrypt.org/t/250404`](https://community.letsencrypt.org/t/i-am-unable-to-acquire-a-le-certificate-via-gitlab-pages-for-my-norfolkneighbourhoodwatch-co-uk/250404?u=beedell.roke).