The external web server has to be configured to respond to GET requests rooted at /.well-known/acme-challenge/ using the aforementioned path. In order for FileZilla Server to be able to respond to the Let’s Encrypt® challenges via an external web server, you have to specify the file system path to a folder on the external web server machine, such that FileZilla Server has the rights to write files into it. Selecting the custom entry you will be allowed to enter the URL to any other ACME protocol directory of your choice (useful in case you want to make use of other providers compatibleīack to Top Perform challenges via an external web server Note: You need to approve Let’s Encrypt Terms of Service by clicking on the Yes button. Check out Let’s Encrypt® Staging documentation to learn more.
Let’s Encrypt® recommends testing against their staging environment before using their production environment, so that you can get things right before issuing trusted certificates and reduce the chance of you hitting Let’s Encrypt® rate limits. For instance, if your email is the contact will have to be provided in the following form: The ACME directory chosen can be one among Let’s Encrypt® production, Let’s Encrypt® staging (for testing only) and custom. Let’s Encrypt® accepts only email addresses as contact, other providers supporting the same protocol might accept other types of contacts, though (like phone numbers, for instance).Įmail contacts must be provided using the appropriate URI, which always begins with mailto. To create a new account, click on the Create new account button.Ī new dialog will ask you to input one or more contact URI and which ACME protocol directory to use. You might need to create a new account if the one you have is already in use.
If you don’t have a Let’s Encrypt® account you must create one. In order to proceed, select the Enable Let’s Encrypt® certificate generation checkbox. To generate a TLS certificate via Let’s Encrypt® you have to create a Let’s Encrypt® account and to select how to execute the Let’s Encrypt® challenge.
0 kommentar(er)
