You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ed has reported on our forums that on our GitLab appliance the Confconsole Let's Encrypt module mangles the domain when triggering GitLab to get a Let's Encrypt certificate. It adds an https:// prefix to the existing value of "external_url" in /etc/gitlab/gitlab.rb.
Whilst it may be irrelevant to this issue specifically, it's worth noting that GitLab does not use the "normal" TurnKey Confconsole Let's Encrypt process. It includes it's own mechanism to get a LE cert, so this issue should be unique to GitLab.
[update] After having a quick look, it seems that the issue is likely in this line.
The text was updated successfully, but these errors were encountered:
Ed has reported on our forums that on our GitLab appliance the Confconsole Let's Encrypt module mangles the domain when triggering GitLab to get a Let's Encrypt certificate. It adds an
https://
prefix to the existing value of "external_url" in /etc/gitlab/gitlab.rb.Whilst it may be irrelevant to this issue specifically, it's worth noting that GitLab does not use the "normal" TurnKey Confconsole Let's Encrypt process. It includes it's own mechanism to get a LE cert, so this issue should be unique to GitLab.
[update] After having a quick look, it seems that the issue is likely in this line.
The text was updated successfully, but these errors were encountered: