No such authorization

[computerscot]

Command entered:

sudo certbot certonly

Expected result:

Spin up a temporary webserver (standalone)

Actual result:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Runs an HTTP server locally which serves the necessary validation files under
the /.well-known/acme-challenge/ request path. Suitable if there is no HTTP
server already running. HTTP challenge only (wildcards not supported).
(standalone)
2: Saves the necessary validation files to a .well-known/acme-challenge/
directory within the nominated webroot path. A seperate HTTP server must be
running and serving files from the webroot path. HTTP challenge only (wildcards
not supported). (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Enter email address (used for urgent renewal and security notices)
 (Enter 'c' to cancel): xxxxxxxxxxxx@xxxxx.com

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf. You must
agree in order to register with the ACME server. Do you agree?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: y

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing, once your first certificate is successfully issued, to
share your email address with the Electronic Frontier Foundation, a founding
partner of the Let's Encrypt project and the non-profit organization that
develops Certbot? We'd like to send you email about our work encrypting the web,
EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: n
Account registered.
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): xxxxx.xxxxx.xxx
Requesting a certificate for xxxxx.xxxxx.xxx
An unexpected error occurred:
No such authorization
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.

[SasukeFreestyle]

You're right.

Certbot has probably updated something my output did not look like this when i wrote this guide. But I'm getting the same expected results that you are getting.

Will edit the guide to reflect this. Thank you.

You did everything correctly, 1 is the correct option.

Your error

An unexpected error occurred:
No such authorization

Is probably because something is blocking port 80 in your system/firewall for authorization.

[SasukeFreestyle]

I just performed a new certificate just to test.

Make sure port 80 is not in use in your system and is open to the Internet.

xxxx@ubuntu-server:~$ sudo certbot certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Nginx Web Server plugin (nginx)
2: Runs an HTTP server locally which serves the necessary validation files under
the /.well-known/acme-challenge/ request path. Suitable if there is no HTTP
server already running. HTTP challenge only (wildcards not supported).
(standalone)
3: Saves the necessary validation files to a .well-known/acme-challenge/
directory within the nominated webroot path. A seperate HTTP server must be
running and serving files from the webroot path. HTTP challenge only (wildcards
not supported). (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-3] then [enter] (press 'c' to cancel): 2
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): XXXXXXX.net
Requesting a certificate for XXXXXXX.net

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/XXXXXXX.net/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/XXXXXXX.net/privkey.pem
This certificate expires on 2023-05-18.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
 * Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
 * Donating to EFF:                    https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[computerscot]

You can make certbot behave more consistently by explicitly specifying the options you want, e.g.:

sudo certbot certonly --standalone --preferred-challenge http --agree-tos --register-unsafely-without-email

[SasukeFreestyle]

You can make certbot behave more consistently by explicitly specifying the options you want, e.g.:

sudo certbot certonly --standalone --preferred-challenge http --agree-tos --register-unsafely-without-email

Since this guide was designed for newbies on Linux, and they usually copy-paste the commands. Your solution is much easier. Thanks!

Fixed in e4b659f