Let's Encrypt SSL Certificates

  1. Home
  2. Docs
  3. Let’s Encrypt SSL Certificates
  4. Setup
  5. Downloads

Downloads

Download the GetSSL.ps1 PowerShell script

First, you’ll need a copy of the GetSSL PowerShell script. Download the file using the link below and save it on your server where you’ll want to install the SSL certificate. We recommend making a new folder for the SSL renewal files at C:\Program Files\FileMaker\SSL Renewal\ and saving this script in there. This folder will also hold logs and other renewal-related files once the script is run.

Download 

Download Crypt-LE (le64.exe)

This script uses the Crypt-LE program from https://github.com/do-know/Crypt-LE/releases. Download the le64.exe executable and store it in a permanent, accessible location on your server. Preferably this would the same SSL Renewal folder used in the last step.

This application is a recommended ACME implementation for Windows from Let’s Encrypt. The source code is available for you to download and build it yourself. There is also a Perl version if you’d like to run that instead of a pre-compiled executable.

Change Windows security to allow PowerShell Scripts to run

Windows Server will not allow you to run PowerShell scripts by default, so you’ll need to modify your security settings to allow this. Open PowerShell or PowerShell ISE as Administrator using the “Run as Administrator” option and enter the command:

Set-ExecutionPolicy -Scope LocalMachine Unrestricted

Enter “y” and press enter to accept the security warnings that appear.

If you’ve copied this file to your server though RDP or over a network you should be fine here, but if the file was downloaded directly to the server from this site there may be another “downloaded from the internet” warning that you’ll have to clear. Place the file in a semi-final location and unblock it using the Unblock-File command, passing in the path to the file as a parameter.

Unblock-File -Path "C:\Program Files\FileMaker\SSL Renewal\GetSSL.ps1"

Note: PowerShell must be Run as Administrator for this step and all subsequent steps, or you will receive errors. Be sure you are running PowerShell or the PowerShell ISE as Administrator using the “Run as Administrator” option, not just a user named Administrator.

Was this article helpful to you? Yes No 1

How can we help?