This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

LetsEncrypt plugin#

This plugin is possible starting with CrushFTP v9. You need to download this plugin and place it in your CrushFTP ▸ Plugins folder. LetsEncrypt.jar
On OSX machines you need to copy the file into:
⁨Applications⁩ ▸ ⁨CrushFTP9_OSX⁩ ▸ ⁨CrushFTP9.app⁩ ▸ ⁨Contents⁩ ▸ ⁨Resources⁩ ▸ ⁨Java⁩ ▸ ⁨plugins⁩

About Let's Encrypt: It is a certificate authority that provides certificates (only domain-validated certificates) for free. (for more info : https://letsencrypt.org/how-it-works/)


LetsEncrypt plugin allows you to create a java key store file (the .JKS file) authorized by the Let's Encrypt certificate authority. You do not need to install, configure, or do anything with certbot if using this plugin.



Domains : Multiple domains should be separated with a comma.

Keystore: Set the location of the jks file, and the name.

Staging flag: It is for test mode. If the is true it will only generate a dummy jks, not a valid one.

If the all fields are ready hit the submit, and the jks will be created in the specified keystore location.

Once done, and full success, there is another step. On Preferences_>Encryption_>SSL page, will need to supply the same full path to the keystore (.jks) file and the passwords you entered on the Letsencrypt plugin. The plugin only generates the key store, but doesn't apply it. Once done, test, if successful, save, then restart the HTTPS port or the CrushFTP service, to actually load the cert. Then can test with a browser.

Will need to click Submit and restart every 60-90 days , bacuse the Letsencrypt cert is valid only for this long.

Troubleshooting
#

1. Check that your server is reachable through the given domain with http protocol on the default port (80).
2. Check the Delete account key pair and Delete domain key pair flags and test again.
3. Rewrite the Keystore Password and Key Password, test it again.