[Help] [Question] Pihole ssl comodo

[vebat84995]

I went to sectigo.com and I saw this:

SSL Certificates | Web Site Security

-----BEGIN RSA PRIVATE KEY-----
(Your Private Key: your_domain_name.key)
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
(Your Primary SSL certificate: your_domain_name.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Your Intermediate certificate: SectigoRSA.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Your Root certificate: USERTrustRSACertificationAuthorityCARoot.crt)
-----END CERTIFICATE-----

Then it would be like this:

HSSL.key
-----BEGIN RSA PRIVATE KEY-----
(Your Private Key: your_domain_name.key)
-----END RSA PRIVATE KEY-----

domain.com.crt

-----BEGIN CERTIFICATE-----
(Your Primary SSL certificate: your_domain_name.crt)
-----END CERTIFICATE-----

SectigoRSADomainValidationSecureServerCA.crt

-----BEGIN CERTIFICATE-----
(Your Intermediate certificate: SectigoRSA.crt)
-----END CERTIFICATE-----

USERTrustRSAAAACA.crt

-----BEGIN CERTIFICATE-----
(Your Root certificate: USERTrustRSACertificationAuthorityCARoot.crt)
-----END CERTIFICATE-----

I am right?
This would be the combined.pem file that I see in this tutorial:

Enabling HTTPS for your Pi-hole Web Interface

How can I enable HTTPS (SSL/TLS) for my Pi-hole Web Interface? Many users run their Pi-hole on Virtual Private Servers and such, meaning that they would need to access the Web Interface via insecure HTTP. Now, you are able to configure Pi-hole so you can securely access your Web Interface, and not cause issues with blocked HTTPS content. What has changed to allow this? With the release of v3.2, we have made changes to our default lighttpd config to not automatically enable the SSL engine if /…

If I'm wrong, correct me.
Thanks, I think I'm making progress.