Get HTTPS for free

This is my project, happy to answer questions or receive feedback. The goal was to let people experiment with getting a Let's Encrypt cert before the had to install anything on their server. The static/unhosted property is to strengthen trust that nothing shady is going on here.

<i>Slightly off topic</i>:<p>I know everyone here is all about naked websites but I couldn&#x27;t help but add these three lines of CSS to the body:<p><pre><code> max-width: 630px; margin: 0 auto; padding: 0 15px; </code></pre> Makes the whole thing much more pleasant to read! (And even looks good on mobile)<p>Here&#x27;s a screenshot: <a href="http:&#x2F;&#x2F;imgur.com&#x2F;UFHJp8a" rel="nofollow">http:&#x2F;&#x2F;imgur.com&#x2F;UFHJp8a</a>

&gt; This website is static, so it can be saved and loaded locally. Just right-click and &quot;Save Page As..&quot;!<p>This strikes me as particularly neat. I wish more SPA&#x27;s were able to work like this.

For those that are interested, I posted an article[1] a little while ago on how to automate the renewal process for Letsencrypt using Daniel&#x27;s acme-tiny[2] script. It&#x27;s a lot nicer to let cron handle it than doing it manually ;)<p>[1] <a href="http:&#x2F;&#x2F;robmclarty.com&#x2F;blog&#x2F;how-to-secure-your-web-app-using-https-with-letsencrypt" rel="nofollow">http:&#x2F;&#x2F;robmclarty.com&#x2F;blog&#x2F;how-to-secure-your-web-app-using-...</a><p>[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;diafygi&#x2F;acme-tiny" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;diafygi&#x2F;acme-tiny</a>

This is definitely a step in the right direction. It&#x27;s bugged me that vendors are leveraging a commercial and proprietary system to secure sites. If we are going to move forward with this as the baseline of security for public facing sites then it&#x27;s good to see a free and transparent solution pop up to help lower costs for students and the developing world.

Very nice, I quite like it!<p>I recently hacked together a completely web-based, client-side CSR generator for PKCS#10; you can take a look at it at <a href="https:&#x2F;&#x2F;johannes.truschnigg.info&#x2F;csr&#x2F;" rel="nofollow">https:&#x2F;&#x2F;johannes.truschnigg.info&#x2F;csr&#x2F;</a> With something like that fused into your project, users wouldn&#x27;t even have to execute `openssl` to generate their key material and CSR, they&#x27;d just need a modern browser with support for the W3 Web Cryptography API.

What is the HTTPS&#x2F;security solution for devices on a home&#x2F;office LAN? They aren&#x27;t externally accessible, don&#x27;t have a globally unique name, but do have access to valuable content (think your router, baby camera, lighting controller, NAS, media device).<p>Having to teach users that you always see the padlock when accessing your valuable information over the Internet, but do not see it when accessing your even more valuable information on the LAN doesn&#x27;t seem good.

The Let&#x27;s Encrypt certificates seem to expire after 90 days. I wrote up some example code in Go so you can automate the process of issuing these certs here: <a href="http:&#x2F;&#x2F;goroutines.com&#x2F;ssl" rel="nofollow">http:&#x2F;&#x2F;goroutines.com&#x2F;ssl</a><p>It does not require CSRs, but uses your DNS provider to complete the challenge. You do not need to run anything on your production servers.

I had been using free Startcom SSL certs, but their UI and overall experience was not as great as this simple website. I just generated mine in about 10 minutes. The last I remember was that StartSSL required something to be stored on my local browser, but I reinstalled my browser, so lost some certificate, etc. If was free, but painful. I know I should automate every 3 months, but even when I miss it, I know I can use this website and manually generate a cert in 10 min.<p>Thanks to OP, diafygi and Lets Encrypt !

Thanks for making such a great little tool.<p>Are you still intending to add a renew page at some point?

This is awesome, just replaced my self-signed ssl with it. Great Thanks!!<p>so the cert will expire in 90 days, how to deal with that? come to the same site every 3 months and regenerate a new SSL cert? Why not at least valid for a year?

What is the intermediate certificate hardcoded in the source?

I plead ignorance here. I&#x27;m sort of out of touch with recent developments, with typically just buying a cert when I need it. So I have a question -- where will Let&#x27;s Encrypt certificates not work? I see Mozilla and Chrome as sponsors, so I&#x27;m guessing it&#x27;s added as authority in at least those browsers?<p>This would be great, apart from apparent insurance regular certificates bring, which I still don&#x27;t know how to claim.

Since it&#x27;s free, could this be included into the installation or configuration scripts of major packages that provide web services ? As long as I have the DNS set up, it would be great if I can run &quot;dpkg-reconfigure exim4-config&quot; and have working STARTTLS with real certificates.

Free is great. My only issue with LetsEncrypt is that the certificates are only valid for 3 months. It&#x27;s a hassle to keep updating the certs...<p>I just switched to AWS Cert Manager last month from StartSSL, which is free if you&#x27;re an AWS customer.

Let&#x27;s encrypt looks so cool with its very few steps. But then you install and you get all sorts of errors not me toned on the page. I spent a good 5 hours debugging yesterday.<p>When it finally works I see that the certificate expires in 2 months.

Or you could use Amazon Web Services for their certificate manager? They offer wild card certificates for free?

Or we could Amazon Web Services for their wildcard certificates?

This is fantastic! Thank you very much for creating this!

These are the things we need for the web.

Sadly Let&#x27;s Encrypt still doesn&#x27;t work if your ISP blocks port 80 and 443.