I am assuming that your domain is a public domain and not localhost. If you search OpenSSL on this forum you will see some example scripts. If you get as far as generating a certificate pfx file then your next step is to script the conversion of that file to the files you need for apache/tomcat SSL configuration. This has the advantage of also not needing to run on the same machine your website is on. The other possibility is that your Apache is not using port 80 at all and the 404 error you got was from Certify’s own http challenge server (which only runs temporarily) you can check that by browsing to and if you get ‘OK’ then it was the built in server that responded.Īnother alternative is to use DNS validation (where you use an automated DNS provider or temporarily use a manual DNS update to set a TXT record to a given value). ![]() So if you solve that configuration problem then http validation will continue as normal. txt extension) in your website root folder (htdocs?) and see if you can open that file in a browser, if not then Let’s Encrypt won’t be able to check it either. When the app asks Let’s Encrypt to provide a certificate for your domain(s) using http validation it will tell the app that each domain must server a challenge response text file at the path the app will then attempt to work out how to arrange for that file to be served up depending on your configuration.īy default Certify The Web runs it’s own http challenge server on port 80 using http.sys, so you don’t need to have IIS installed, but if you have apache installed and using port 80 then this http challenge listener won’t be able to start and your website on port 80 (presumably handled by apache) will have to handle the challenge response itself, that’s where your website root directory comes in. Serving a challenge response file to Let’s Encrypt You can redirect to other ports but port 80 must be open and accepting requests. I assume this is whats failing for you (you can provide the log file which would say more). If the built-in validation tests are preventing you progressing (including checking your website is accessible on port 80 - if it’s not then Let’s Encrypt will not validate the domain) you can disable the apps own tests under Authorization, un-checking Perform challenge response config checks. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |