lets-encrypt

I know how to configure let's encrypt for nginx . I'm having hard time configuring let's encrypt with nginx inside a docker image. Let's encrypt certificates are symlinked in etc/letsencrypt/live folder and I don't have permission to view the real certificate files inside /etc/letsencrypt/archive Can someone suggest a way out ? If anyone having this problem, I've solved it by mounting the folders into docker container. I've mounted both etc/letsencrypt and etc/ssl folders into docker Docker has -v flag to mount volumes. Don't forget to open port 443 for the container. Based on how you mount it

This is my current htaccess configuration of /frontend/web RewriteEngine on RewriteCond %{HTTPS} !=on RewriteRule ^.*$ https://%{SERVER_NAME} [R,L] # if a directory or a file exists, use it directly RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d # otherwise forward it to index.php RewriteRule . index.php I am trying to insert this: RewriteCond %{REQUEST_URI} !^.well-known/acme-challenge/$ or RewriteCond %{REQUEST_URI} ! /\.well-known|^\.well-known above RewriteRule ^.*$ https://%{SERVER_NAME} [R,L] to create letsecnrypt certificate, but none of this is working.

I'm trying to set up let's encrypt on a load balancer written in Go, I tried both the automatic and manual setup but I always get errors. The domain is pointing correctly to our server (Digital Ocean) and I can even open the site from a browser without errors, also an ssl check report no errors on this domain. The fact is that when I run the Go executable on server from CLI I get errors repeatedly. Automatic (acme/autocert) setup: The server code is that, the certificate and the key are created when I look at the domain from a browser for the first time after the server start: go func() { log

I've followed Heroku's Automated Certificate Management instructions for generating an SSL certificate via LetsEncrypt (kudos to LetsEncrypt and heroku!!) for my Ruby Sinatra app but generation of the SSL certificate for my custom domain is failing. After activating automated certificate management, the heroku domain name for my app changes from *.herokuapp.com to *.herokudns.com, as expected. I've updated my Google Domain records accordingly, however Google Domain doesn't allow the domain root to be specified as a CNAME record. Instead the root needs to be pointed at http(s)://www

I recently added LetsEncrypt certificates to my server and my java applet is having problems connecting using TLS. My applet uses Apache HttpClient. My web server is Apache 2,4, and I have a few virtual hosts set up as subdomains of my main domain (foo.com - not my real domain name). When I run my applet on the staging subdomain (e.g. it runs off https://staging.foo.com ), I get the following error: javax.net.ssl.SSLException: Certificate for <staging.foo.com> doesn't match any of the subject alternative names: [developer.foo.com] at org.apache.http.conn.ssl.AbstractVerifier.verify