My domain is: diliver.all.net
I ran this command:
PER the manual:
If you’d like to obtain a certificate running certbot
on a machine other than your target webserver or perform the steps for domain validation yourself, you can use the manual plugin. While hidden from the UI, you can use the plugin to obtain a certificate by specifying certonly
and --manual
on the command line. This requires you to copy and paste commands into another terminal session, which may be on a different computer.
The manual plugin can use either the http
or the dns
challenge. You can use the --preferred-challenges
option to choose the challenge of your preference.
The http
challenge will ask you to place a file with a specific name and specific content in the /.well-known/acme-challenge/
directory directly in the top-level directory (“web root”) containing the files served by your webserver. In essence it’s the same as the webroot plugin, but not automated.
======================= ACTUAL TRANSCRIPT:
It produced this output:
=======================
certbot certonly --manual
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Please enter in your domain name(s) (comma and/or space separated) (Enter 'c'
to cancel): diliver.all.net
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for diliver.all.net
NOTE: The IP of this machine will be publicly logged as having requested this
certificate. If you're running certbot in manual mode on a machine that is not
your server, please ensure you're okay with that.
Are you OK with your IP being logged?
(Y)es/(N)o: Y
Create a file containing just this data:
hpeEqjxEwt0Sz0ytcGb7326oJEKwZ1szbC09bJLBzaE.KISF3d6LBdw-L_Z8ejIPrIWHfFjEUwI5AkzyAXgtrz4
And make it available on your web server at this URL:
http://diliver.all.net/.well-known/acme-challenge/hpeEqjxEwt0Sz0ytcGb7326oJEKwZ1szbC09bJLBzaE
Press Enter to Continue
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. diliver.all.net (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://diliver.all.net/.well-known/acme-challenge/hpeEqjxEwt0Sz0ytcGb7326oJEKwZ1szbC09bJLBzaE: Error getting validation data
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: diliver.all.net
Type: connection
Detail: Fetching
http://diliver.all.net/.well-known/acme-challenge/hpeEqjxEwt0Sz0ytcGb7326oJEKwZ1szbC09bJLBzaE:
Error getting validation dataTo fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
======================= WHEN I PULL FROM THE WEB SERVER USING A BROWSER USING THE URL IDENTIFIED:
hpeEqjxEwt0Sz0ytcGb7326oJEKwZ1szbC09bJLBzaE.KISF3d6LBdw-L_Z8ejIPrIWHfFjEUwI5AkzyAXgtrz4
======================= WHEN I LOOK AT THE SOURCE IT IS IDENTICAL
Note there is no newline after the hypnhen - it's just an appearance from the form
Looks exactly right to me
My web server is (include version): A custom Web server - no name
The operating system my web server runs on is (include version): Linux - many variants
My hosting provider, if applicable, is: AWS - it's a normal server instance
I can login to a root shell on my machine (yes or no, or I don't know): Indeed. And if I stop my server, run the certbot where it provides the server, it works - then I restart my server and the SSL certificate works.
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 --version
certbot 0.31.0