<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Https on Alemasone</title><link>https://www.alemasone.com/en/tags/https/</link><description>Recent content in Https on Alemasone</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 19 Sep 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://www.alemasone.com/en/tags/https/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Install Let's Encrypt SSL on Windows IIS</title><link>https://www.alemasone.com/en/install-lets-encrypt-ssl-windows-iis/</link><pubDate>Sun, 28 Jul 2024 16:05:49 +0000</pubDate><guid>https://www.alemasone.com/en/install-lets-encrypt-ssl-windows-iis/</guid><description>&lt;div class="lead !mb-9 text-xl"&gt;&#10; On a Windows server running IIS, the easiest way to get free HTTPS is with &lt;strong&gt;win-acme&lt;/strong&gt;: it fetches the certificate from Let’s Encrypt, installs it on your site, configures the binding on port 443, and automatically creates the scheduled task for renewal. If instead you already have a certificate file (&lt;code&gt;.pfx&lt;/code&gt; or &lt;code&gt;.cer&lt;/code&gt;) to import, you can find the procedure using the Certificate Manager console further down.&#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;A certificate does two things: it encrypts the traffic between the visitor and the server, and it proves that the site is indeed what it claims to be. Without it, browsers will display a warning that scares everyone away.&lt;/p&gt;</description></item></channel></rss>