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: comic.collar6.wiki
I ran this command: sudo certbot (then instructed it to make cert for only comic.collar6.wiki)
It produced this output: output as expected
My web server is (include version): Apache 2.4.41
The operating system my web server runs on is (include version): Ubuntu Server 18.04
My hosting provider, if applicable, is: selfhost
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): 0.31.0 (via Canonical)
I don’t -think- I’ve hit rate limits for the week, but I have done some revoking and new domains on my server/account in the last week.
Other active certs I have include: raindrop.works, nextcloud.raindrop.works and collar6.wiki. I’ve revoked certs for backup.collar6.wiki and collabora.raindrop.works, but if I understand the rate limits policy, I shouldn’t be at that limit, and even if I was, the cert should fail, not give me a cert for the domain when I’m requesting the subdomain