Title: Lets encrypt not supported
Last modified: September 1, 2016

---

# Lets encrypt not supported

 *  Resolved [mruepp](https://wordpress.org/support/users/mruepp/)
 * (@mruepp)
 * [9 years, 12 months ago](https://wordpress.org/support/topic/lets-encrypt-not-supported/)
 * For Lets Encrypt to issue and autoupdate certificates, the public_html/.well-
   known/acme-challenge/ directory MUST be accessible.
 * The Plugin does not support this. Most of the Panels does support Lets Encrypt
   nowadays.
 * [https://www.virtualmin.com/node/41543#comment-760360](https://www.virtualmin.com/node/41543#comment-760360)
 * Please consider implementing the functionality.
 * [https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Contributor [wpsolutions](https://wordpress.org/support/users/wpsolutions/)
 * (@wpsolutions)
 * [9 years, 12 months ago](https://wordpress.org/support/topic/lets-encrypt-not-supported/#post-7620321)
 * If one of the AIOWPS firewall rules is causing this then I recommend that you
   do some tests by disabling/enabling the firewall rules until you find the particular
   rule.
    When you find the rule which is doing the blocking just leave it disabled.
 *  Thread Starter [mruepp](https://wordpress.org/support/users/mruepp/)
 * (@mruepp)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/lets-encrypt-not-supported/#post-7620351)
 * Firewall disabling does not work. The aiowps plugin has to be disabled completely
   while updating lets encrypt certificates.
 * This is bad because most hosting panels allow autoupdating of letsencrypt and
   the intervals are very short, like 1-2months.
 * So if using AIOWPS, you for sure run into a update mess every 1-2 months if hosting
   large amounts of customers.
 * I would reccomend implementing a checkbox “If you use Lets encrypt, check this
   box” like you did with the Jetpack situation where the xml-rpc rule blocked the
   functionality.
 * I do not know the exact api but a file in public_html/.well-known/acme-challenge/
   must be accessible (readable) with curl from inside the server out and from outside
   as well.
 *  Plugin Contributor [wpsolutions](https://wordpress.org/support/users/wpsolutions/)
 * (@wpsolutions)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/lets-encrypt-not-supported/#post-7620365)
 * I’m not familiar with that other plugin you are referring to and hence I have
   no idea what is causing the issue you are seeing.
 * If it’s not the firewall rules it could be some other feature in the AIOWPS plugin
   doing the blocking.
 * Since you’re already familiar with that encrypt plugin I recommend that you you
   go through the AIOWPS features and perform some tests to find which feature is
   doing the blocking.
    When you find it let us know. When we know what the cause
   is, we may be able to offer a workaround or solution.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Lets encrypt not supported’ is closed to new replies.

 * ![](https://ps.w.org/all-in-one-wp-security-and-firewall/assets/icon-256x256.
   png?rev=2798307)
 * [All-In-One Security (AIOS) – Security and Firewall](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [wpsolutions](https://wordpress.org/support/users/wpsolutions/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/lets-encrypt-not-supported/#post-7620365)
 * Status: resolved