The following is outdated! See the comment below for notes updated on 2nd December 2015 . Some notes on using the webroot domain verification process with the test ACME server (don’t do this on a live server yet!) in case anyone else wants to have a play with this — this method will be best suited f…

yeah bit spread out :slight_smile: also webroot authentication useful for non-standard nginx/apache or other web server setups where paths to web server config files and structure are unknown to letsencrypt

how does webroot require SSH I read that manual mode + webroot is the perfect way to get a cert from your home PC and push the challenge and later the cert to the server.

[image] My1: how does webroot require SSH I read that manual mode + webroot is the perfect way to get a cert from your home PC and push the challenge and later the cert to the server. webroot still runs letsencrypt client which is run in ssh. see my example at https://community.centminmod.com…

well the client itself doesnt need SSH but rather terminal access at any server (at least that’s what I read) so you can us4e a VM, raspi or anything that runs linux let it run the auth in manual mode you get the challenge, upload it to your server and get your cert.

well SSH = terminal as you’d still need to point domain dns to ip of the terminal accessed server for webroot

[image] LE client needs to bind to port 80, which I'm already using webroot: (--webroot-path should be pointed to your public_html) you specify a directory where the files for verification are added by the client without starting a webserver at all manual: (-a manual) Requires to copy and paste …

As far as I understood it you can use the LE on your desktop computer e.g., but you (temporarily) have to change the ip associated with the domain you want to generate a cert for, so that it points to your desktop computer. If it is like this this is not really different than just using any other n…

but I dont see any need to change the DNS it just checks whether the challenge lies on the domain so if the user puts the challenge from the LE client (which doesnt have any DNS entries) to the Webserver (obviously in the domain DNS) then LE just checks “here’s the challenge, so I am happy” doesnt i…

You don’t have to change anything in your DNS configuration for manual mode. Just your webserver config.

[image] My1: if the user puts the challenge from the LE client (which doesnt have any DNS entries) to the Webserver (obviously in the domain DNS) then LE just checks "here's the challenge, so I am happy" doesnt it? yes if user manually setups up the .well-known uri and proper content-type res…

Using the webroot domain verification method

Server

My1 November 3, 2015, 10:40am 19

as seen in the quote,manual mode does not need SSH on the target server, just a way to get files (for webroot) and the cert (obviously) on it. so you can use any computer that is compatible with LE to get your cert.

Topic		Replies	Views
Letsencrypt Webroot Authentication Tested on Beta invited/whitelisted domain Issuance Tech	6	16349	December 2, 2015
[Webroot] Error: The client lacks sufficient authorization Help	11	5557	January 6, 2016
New to LetsEncrypt Help	33	3187	September 29, 2021
Webroot plugin : The client lacks sufficient authorization Uncategorized	37	37370	April 25, 2017
I just want a certificate Uncategorized	26	11366	December 11, 2015

Using the webroot domain verification method

Related topics