lets-encrypt

问题 I have a Node Express app running on Heroku that I want to encrypt with a free-of-charge SSL cert from LetsEncrypt. However, the methods I've seen require opening up ports 443 and 80 to allow the ACME process to work. Heroku only gives you one port, and doesn't let you choose which port. So how can I use LetsEncrypt? I spent a bunch of time figuring this out yesterday. First time in a long time there were no answers on StackOverflow for something I was trying to do! 回答1: Update: Heroku now

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 years ago . I am just simply trying to add the domain test.example.com to the certificate that already exists for example.com . How do I add a domain to my existing certificate and replace the old certificate? I have tried these few commands ./letsencrypt-auto certonly --cert-path /etc/letsencrypt/archive/example.com -

问题 I am developing a Java application that queries a REST API on a remote server over HTTP. For security reasons this communication should be switched to HTTPS. Now that Let's Encrypt started their public beta, I'd like to know if Java currently works (or is confirmed to be working in the future) with their certificates by default. Let's Encrypt got their intermediate cross-signed by IdenTrust, which should be good news. However, I cannot find any of these two in the output of this command:

问题 I am working with cert-manager in my kubernetes cluster, in order to get certificates signed by let'sencrypt CA to my service application inside my cluster. I am performing the following steps in the order presented. I've wanted provide the most details as a possible of my process in order to understand the behavior presented. Install the CustomResourceDefinition resources separately ⟩ kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.7/deploy/manifests/00

问题 To renew a LetsEncrypt certificate I was following this Bitnami doc and: sudo /opt/bitnami/letsencrypt/lego --tls --email="somebody@example.com" --domains="example.com" --domains="www.example.com" --path="/opt/bitnami/letsencrypt" renew --days 90 kept returning the error: You have to pass an account (email address) to the program using --email or -m I tried retyping the hyphens and quotations in case they were being changed to en dashes and inverted commas in copy/paste, but no luck.

问题 I am running into an issue with executing 'letsencrypt-auto' on the GCE Bitnami Ghost image. The issue can be reproduced using the base installer below: https://cloud.google.com/launcher/solution/bitnami-launchpad/ghost Here is the command I use, and it's output: sudo wget https://github.com/letsencrypt/letsencrypt/archive/master.zip sudo unzip master.zip cd letsencrypt sudo /opt/bitnami/ctlscript.sh stop sudo ./letsencrypt-auto --debug ..install dependencies... **Reading package lists...

问题 Hi have setup a small serve, generated a free certificate from Let's encrypt and configured Nginx to use that certificate (fullchain.pem and privkey.pem) However, when I attempt to make a call from my Android app (with OkHttp3) I get this error java.security.cert.CertPathValidatorException: Trust anchor for certification path not found Is Let's encrypt root certificate not trusted by the Android cert trust store? Or did I miss something when setting up nginx? What is a work around for this If

问题 I am trying to install letsencrypt on ubuntu 14 on DigitalOcean Server but getting this issue. I tried sudo to install but same error, also try to install libs but nothing happen. apt-key update result : gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>" not changed gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>" not changed gpg: key

问题 I am using Let's Encrypt to install a free TLS/SSL certificate in my server. I followed the suggestion of Mozilla SSL Configuration Generator and configured nginx like this: ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH"; The problem is that I need Java 7 to communicate with the server and it doesn't work with the configuration above. When I submit my site to ssllabs I get the following message: Java 7u25 Server sent fatal alert: handshake_failure If I just comment the ssl

问题 I have installed SSL successfully for my main domain eg. domain.net and www.domain.net I am now trying to enable SSL into the blog on the website eg. blog.domain.net and www.blog.domain.net I have gone through the installation and everything has been a success, however after restarting nginx when I visit 'blog.domain.net.conf' it is returning a '403 Forbidden' error now. I have tried doing: sudo chown -R root:root /usr/share/nginx/html/* sudo chown -R dev:dev /usr/share/nginx/html/* sudo