*
* procedura per certificare i siti sotto Xampp 
*

programma in C:\lews




 A simple Windows ACMEv2 client (WACS)
 Software version 2.1.20.1185 (release, trimmed, standalone, 64-bit)
 Connecting to https://acme-v02.api.letsencrypt.org/...
 Scheduled task looks healthy
 Please report issues at https://github.com/win-acme/win-acme

 N: Create certificate (default settings)
 M: Create certificate (full options)
 R: Run renewals (0 currently due)
 A: Manage renewals (5 total)
 O: More options...
 Q: Quit

 Please choose from the menu: m

 Running in mode: Interactive, Advanced
 Source plugin IIS not available: No supported version of IIS detected.

 Please specify how the list of domain names that will be included in the
 certificate should be determined. If you choose for one of the "all bindings"
 options, the list will automatically be updated for future renewals to
 reflect the bindings at that time.

 1: Read bindings from IIS
 2: Manual input
 3: CSR created by another program
 C: Abort

 How shall we determine the domain(s) to include in the certificate?: 2

 Description:        A host name to get a certificate for. This may be a
                     comma-separated list.

 Host: www.fun4events.it

 Source generated using plugin Manual: www.fun4events.it

 Friendly name '[Manual] www.fun4events.it'. <Enter> to accept or type desired name: <Enter>

 The ACME server will need to verify that you are the owner of the domain
 names that you are requesting the certificate for. This happens both during
 initial setup *and* for every future renewal. There are two main methods of
 doing so: answering specific http requests (http-01) or create specific dns
 records (dns-01). For wildcard domains the latter is the only option. Various
 additional plugins are available from https://github.com/win-acme/win-acme/.

 1: [http-01] Save verification files on (network) path
 2: [http-01] Serve verification files from memory
 3: [http-01] Upload verification files via FTP(S)
 4: [http-01] Upload verification files via SSH-FTP
 5: [http-01] Upload verification files via WebDav
 6: [dns-01] Create verification records manually (auto-renew not possible)
 7: [dns-01] Create verification records with acme-dns (https://github.com/joohoi/acme-dns)
 8: [dns-01] Create verification records with your own script
 9: [tls-alpn-01] Answer TLS verification request from win-acme
 C: Abort

 How would you like prove ownership for the domain(s)?: 1

 Description:        Root path of the site that will serve the HTTP validation
                     requests.

 Path: D:\xampp\htdocs

 Description:        Copy default web.config to the .well-known directory.
 Default:            False
 Argument:           False (press <Enter> to use this)

 Copy default web.config before validation? (y/n*) - yes

 After ownership of the domain(s) has been proven, we will create a
 Certificate Signing Request (CSR) to obtain the actual certificate. The CSR
 determines properties of the certificate like which (type of) key to use. If
 you are not sure what to pick here, RSA is the safe default.

 1: Elliptic Curve key
 2: RSA key
 C: Abort

 What kind of private key should be used for the certificate?: 2

 When we have the certificate, you can store in one or more ways to make it
 accessible to your applications. The Windows Certificate Store is the default
 location for IIS (unless you are managing a cluster of them).

 1: IIS Central Certificate Store (.pfx per host)
 2: PEM encoded files (Apache, nginx, etc.)
 3: PFX archive
 4: Windows Certificate Store
 5: No (additional) store steps

 How would you like to store the certificate?: 2

 Description:        .pem files are exported to this folder.

 File path: D:\xampp\htdocs\.well-known\acme-challenge

 Description:        Password to set for the private key .pem file.

 1: None
 2: Type/paste in console
 3: Search in vault

 Choose from the menu: 1

 1: IIS Central Certificate Store (.pfx per host)
 2: PEM encoded files (Apache, nginx, etc.)
 3: PFX archive
 4: Windows Certificate Store
 5: No (additional) store steps

 Would you like to store it in another way too?: 5

 Installation plugin IIS not available: No supported version of IIS detected.

 With the certificate saved to the store(s) of your choice, you may choose one
 or more steps to update your applications, e.g. to configure the new
 thumbprint, or to update bindings.

 1: Create or update bindings in IIS
 2: Start external script or program
 3: No (additional) installation steps

 Which installation step should run first?: 3

 Existing renewal:   [Manual] www.fun4events.it - renewed 1 time, due after
                     2022/5/1 17:06:10

 Overwrite settings? (y*/n) - yes

 Overwriting previously created renewal

 Using cache for [Manual] www.fun4events.it. To get a new certificate within 1 days, run with --force.
 Store with PemFiles...
 Exporting .pem files to D:\xampp\htdocs\.well-known\acme-challenge
 Installing with None...
 Scheduled task looks healthy
 Next renewal scheduled at 2022/5/1 17:06:10
 Certificate [Manual] www.fun4events.it created

 N: Create certificate (default settings)
 M: Create certificate (full options)
 R: Run renewals (0 currently due)
 A: Manage renewals (5 total)
 O: More options...
 Q: Quit

 Please choose from the menu: