Struggling to get SSL for subdomains with CertSage (Domainfactory, cPanel)

Help
1

i managed to get SSL via CertSage for spule.at, thanks to Struggling to set up a SSL certificate in the cPanel of DomainFactory

but for any subdomain of spule.at CertSage responses with a »Trouble... urn:ietf:params:acme:error:unauthorized [IP redacted] Invalid response from http:// subdomain.spule.at/.well-known/acme-challenge/ [challenge redacted]: 404«

any help highly appreciated

merci + a bienTom

— — — 8< — — — — — —
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: spule.at (SSL working), test.spule.at (SSL not working)

I ran this command: via CertSage

It produced this output: Trouble... urn:ietf:params:acme:error:unauthorized [IP redacted] Invalid response from http:// test.spule.at/.well-known/acme-challenge/[challenge redacted]: 404

My web server is (include version): Apache Version 2.4.66

The operating system my web server runs on is (include version): linux, Kernel Version 4.18.0-553.54.1.lve.el8.x86_64

My hosting provider, if applicable, is: DomainFactory, df.eu

I can login to a root shell on my machine (yes or no, or I don't know): I don't know yet

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes, cPanel Version 126.0 (build 47)

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): CertSage version 3.2.1, Perl Version 5.26.3
— — — >8 — — — — — —

2

Welcome to the Let's Encrypt Community! :slightly_smiling_face:

I'm the author of CertSage. Please follow the guide below and if you still have questions I'll be happy to answer them.

3

For subdomain names that don't point to the same content as the apex (non-subdomain) name, you need to visit certsage.php from that subdomain name like sub.domain.com/certsage.php so that the certsage.php file for sub exists in the webroot content directory for sub. You can't visit domain.com/certsage.php to acquire a certificate for sub.domain.com unless domain.com and sub.domain.com serve from the same webroot content directory, which, aside from the www subdomain, they usually don't.

4

thanks a lot @griffin — copying certsage.php to every subdomain-path was the solution
i misinterpretated »Domain and Subdomain Names« as being able to manage SSL for the domain as well as any of its subdomains from the domains certsage.php

merci + a bienTom