SSL_ERROR_BAD_CERT_DOMAIN in Gitlab Pages when username contains a .

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

When setting up a website through Gitlab Pages, The SSL certificate is only valid for gitlab.io and *.gitlab.io.

Because of this, usernames containing a . (in my case firstname.lastname) are not considered valid, resulting in a warning screen with the header "Warning: Potential Security Risk Ahead" (on Firefox) and the error code SSL_ERROR_BAD_CERT_DOMAIN.

Note that I'm not able to change my username as I already have other projects setup.

Steps to reproduce

  1. Setup an account with a username containing a . (ex firstname.lastname).
  2. Create a new project using the Pages/Plain HTML template.
  3. Run the CI/CD Pipeline for the newly created project.
  4. Once the website is up, access it through Settings/Pages.
  5. A warning screen with the error SSL_ERROR_BAD_CERT_DOMAIN appears.

Example Project

project: https://gitlab.com/august.almgren/pages-ssl-bug

website: https://august.almgren.gitlab.io/pages-ssl-bug

What is the current bug behavior?

The SSL_ERROR_BAD_CERT_DOMAIN error screen appears.

What is the expected correct behavior?

The website should load without errors or warnings.

Relevant logs and/or screenshots

gitlab-ssl-error-screenshot

Output of checks

This bug happens on GitLab.com

Possible fixes

Making the SSL certificate valid for *.*.gitlab.io should resolve the issue.

Edited by 🤖 GitLab Bot 🤖