Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install trouble with autogenerated third level domains #22

Open
sevaa opened this issue Nov 19, 2024 · 0 comments
Open

Install trouble with autogenerated third level domains #22

sevaa opened this issue Nov 19, 2024 · 0 comments

Comments

@sevaa
Copy link

sevaa commented Nov 19, 2024

My Cpanel based hosting setup has a feature that for every second level domain there is a set of autogenerated third level domains. E. g. if my domain is example.com, the same site also serves up autodiscover.example.com, cpanel.example.com and several others. If I want TLS on those, they need to be listed in the certificate under the SAN extension. Let's Encrypt supports that, and so does Certbot. If you specify all those domains in the run command under the -d option, comma separated but no space, the certificate is generated correctly.

As far as Cpanel is concerned, all those domains are being served up from a single site and share a certificate.

Now here is the issue. When it comes to installing the cert on Cpanel, the plugin treats all those domains as if they were separate zones and separate sites. So it tries to install the cert into example.com, then into autodiscover.example.com - and that fails, since that's not a zone from the Cpanel standpoint.

My setup also has legitimate third level domains under example.com - ones that do have a zone of their own.

Can this kind of setup can be deduced from the Cpanel API and handled accordingly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant