# Let's Encrypt with Windows **URL:** \ **Category:** Ignition\ **Created:** [October 7, 2020, 5:05pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467 "2020-10-07T17:05:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mjeppsen](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@mjeppsen](https://forum.inductiveautomation.com/u/mjeppsen)\ **Post date:** [October 7, 2020, 5:05pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/1 "2020-10-07T17:05:29Z")
It is possible to setup an SSL in a Windows version of an Ignition server? Everything that I can see in the documentation and other forums is for Linux only. ---
**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\ **Post date:** [October 7, 2020, 5:49pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/2 "2020-10-07T17:49:06Z")
I’m not really following what you’re saying but hopefully starting here helps you out: [https://docs.inductiveautomation.com/display/DOC80/Using+SSL#UsingSSL-EnablingSSL](https://docs.inductiveautomation.com/display/DOC80/Using+SSL#UsingSSL-EnablingSSL) ---
**Author:** ![mjeppsen](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@mjeppsen](https://forum.inductiveautomation.com/u/mjeppsen)\ **Post date:** [October 8, 2020, 1:36pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/3 "2020-10-08T13:36:49Z")
Sorry should have been more clear in the description. I’m wondering if anyone has successfully setup an SSL certificate with Let’s Encrypt on a Windows Ignition Server. All of the literature/examples that I can find are only for Linux. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 8, 2020, 4:35pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/4 "2020-10-08T16:35:16Z")
You absolutely can set up Let’s Encrypt on a Windows host - you’ll find that most guides follow Linux because it’s _somewhat_ simpler to set up, but there’s absolutely nothing stopping you. It’s important to separate a few things: Let’s Encrypt is a new CA (Certificate Authority) and one of/the first CAs to support the [ACME](https://en.wikipedia.org/wiki/Automated_Certificate_Management_Environment) protocol - as the acronym implies, it’s all about automated certificate management. ACME/LE push towards a new style of short-lived, automatically renewed certs; ‘legacy’ SSL certs generally last so long (2, 3, 5 years) that it’s not worth the effort to automate. By only issuing short lived certs, LE incentivizes automation. In _addition_ to Let’s Encrypt, you’ll often see something called `certbot` - though it’s usually not called out as a separate “thing”. `certbot` is an ACME ‘client’, and it absolutely has support for Windows: [https://certbot.eff.org/lets-encrypt/windows-other.html](https://certbot.eff.org/lets-encrypt/windows-other.html) - but, you really just need _any_ ACME client to use Let’s Encrypt - `certbot` is just the “reference” implementation. For instance, there’s a variety of IIS implementations: [https://letsencrypt.org/docs/client-options/#clients-windows-/-iis](https://letsencrypt.org/docs/client-options/#clients-windows-/-iis) Once you have an ACME client, a lot of the rest of the SSL guide [here](https://www.inductiveautomation.com/resources/article/lets-encrypt-guide-for-ignition#acme-client) should still apply - you’ll have to change the command line arguments a bit, but the basic process is still the same. ---
**Author:** ![mjeppsen](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@mjeppsen](https://forum.inductiveautomation.com/u/mjeppsen)\ **Post date:** [October 8, 2020, 4:55pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/5 "2020-10-08T16:55:20Z")
@paul-griffith we’ll give it a try as you describe. Many thanks! ---
**Author:** ![lane.duncan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lane.duncan/32/83700_2.png) [@lane.duncan](https://forum.inductiveautomation.com/u/lane.duncan)\ **Post date:** [October 13, 2020, 1:58pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/6 "2020-10-13T13:58:46Z")
I have used Certify the Web successfully on a Win2016 server: > **[Getting Started | Certify The Web Docs](https://docs.certifytheweb.com/docs/intro/)** > > Certify The Web (a.k.a Certify) is the most popular GUI for professional ACME certificate management on Windows, allowing you to easily request, deploy, auto-renew and manage free SSL/TLS certificates from Certificate Authorities such as Let's... ---
**Author:** ![mudbay](https://avatars.discourse-cdn.com/v4/letter/m/a4c791/32.png) [@mudbay](https://forum.inductiveautomation.com/u/mudbay)\ **Post date:** [January 26, 2022, 6:32pm UTC](https://forum.inductiveautomation.com/t/lets-encrypt-with-windows/39467/7 "2022-01-26T18:32:41Z")
@lane.duncan **Certify The Web** requires Port 80 to be open to validate you domains. I am currently already using a Cert and have HTTPS enabled on the Gateway (have not implemented ACME). How did you configure things to both use Port 80 for Certify domain validation, but keep the Gateway access only using HTTPS? My concern comes from having to expose Port 80 and how to do this securely.