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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.
1: vhaan.me.tld
2: mail.vhaan.me.tld
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Requesting a certificate for vhaan.me.tld and mail.vhaan.me.tld
An unexpected error occurred:
Invalid identifiers requested :: Cannot issue for "mail.vhaan.me.tld": Domain name does not end with a valid public suffix (TLD) (and 1 more problems. Refer to sub-problems for more information.)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
My web server is (include version): - Server version: Apache/2.4.61
The operating system my web server runs on is (include version): - Name: Debian GNU/Linux
Pretty Name: Debian GNU/Linux 12 (bookworm)
Version: 12 (bookworm)
Version ID: 12
Codename: bookworm
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know): i dont know
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): certbot 2.11.0
Domain names for issued certificates are all made public in Certificate Transparency logs(e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Thus you need to own and have control over the Domain Name (or have a subdomain under an existing domain name, for example pointed to your server by your employer or school) you wish to obtain a certificate for, from an ICANN Accredited Registrar.
But you will need a domain name that does end with a public suffix (TLD) to obtain a certificate issued by Let’s Encrypt. Presently Let’s Encrypt does not issue certificates for IP Addresses.
MultipleIPAddressDiscrepancy
WARNING
vhaan.me has multiple IP addresses in its DNS records. While they appear to be accessible on the network, we have detected that they produce differing results when sent an ACME HTTP validation request. This may indicate that some of the IP addresses may unintentionally point to different servers, which would cause validation to fail.
[Address=70.50.92.209,Address Type=IPv4,Server=Apache/2.4.61 (Debian),HTTP Status=404] vs [Address=76.76.21.21,Address Type=IPv4,Server=Vercel,HTTP Status=404]
Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
