Error when trying to register a certificate

[joost1]

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.

My domain is: joost.zip

I ran this command: certbot certonly -d joost.zip --server "https://dv.acme-v02.api.pki.goog/directory" --standalone

It produced this output: Saving debug log to C:\Certbot\log\letsencrypt.log
Requesting a certificate for joost.zip

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:

• Domain: joost.zip*
• Type: incorrectResponse*
• Detail: DNS look-up of joost.zip returned no results.*

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): -

The operating system my web server runs on is (include version): windows

My hosting provider, if applicable, is: -

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): 2.6.0

[rg305]

Hi @joost1, and welcome to the LE community forum

In order to use this command:

@joost1

I ran this command: certbot certonly -d joost.zip --server "https://dv.acme-v02.api.pki.goog/directory" --standalone

You will need to update the DNS zone so that name returns the Internet IP where the site will be hosted.

Right now, it returns nothing/empty string:

nslookup joost.zip 8.8.8.8
Server:  dns.google
Address:  8.8.8.8
Name:    joost.zip
[EMPTY reply]

Then you will need to ensure the Internet can reach that IP via HTTP.

[Osiris]

Or, use the dns-01 challenge. The certbot-dns-multi plugin for Certbot supports Google Domains since version 4.11.0.

[danb35]

@joost1

I ran this command: certbot certonly -d joost.zip --server "https://dv.acme-v02.api.pki.goog/directory" --standalone

If you're trying to use Google's Certificate Authority, why are you asking for help here?

[petercooperjr]

@danb35

why are you asking for help here

Because Certbot's error message always directs users here, for any problem, regardless of which CA is being used.

(Which may even be correct, if this is the "certbot support forum" and not just the "Let's Encrypt support forum"? I don't think it's clear whether certbot should change or our community should expect to support other CAs through certbot, which is probably why the messaging is still there in the meantime.)

[danb35]

@petercooperjr

if this is the "certbot support forum"

Don't see why it should be, any more than it should be the support forum for acme.sh or winacme. ISRG has been quite explicit for a number of years that certbot is a separate project from a separate organization. But that's probably a discussion that belongs in another topic.

[MikeMcQ]

I asked about this a few months back and the Certbot team said they discussed this and do not plan changing the referal. I'm not sure if "they" meant just EFF or also ISRG.

[Osiris]

While offtopic, my 2 cents:

The Let's Encrypt team has said previously that this Community should not be seen as Let's Encrypt-only nor Certbot-only. This Community (the site) should be there to help to achieve the goals of Let's Encrypt, which is to create a more secure and privacy-respecting web. Regardless of the CA or ACME client used.

Every member of this Community can choose for themselves if they want to help anyone using something else than Certbot or LE. That's their prerogative. But specifically telling people they should not ask for help here due to the fact they're not using LE and/or Certbot is not the way to go.

[Bruce5051]

True; but there is this also https://community.letsencrypt.org/t/provide-support-for-commercial-acme-clients-such-as-acme-sh/156764/27?u=bruce5051

[Osiris]

True.