Title: Two SSL Errors
Last modified: March 28, 2023

---

# Two SSL Errors

 *  Resolved [darrenasmithmtm](https://wordpress.org/support/users/darrenasmithmtm/)
 * (@darrenasmithmtm)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/two-ssl-errors/)
 * [https://d.pr/i/2iATd0](https://d.pr/i/2iATd0)
 * The above screenshot shows the errors with SSL that we cannot resolve.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ftwo-ssl-errors%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Support [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * (@jarnovos)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/two-ssl-errors/#post-16601965)
 * Hi [@darrenasmithmtm](https://wordpress.org/support/users/darrenasmithmtm/),
 * **#1: Code execution allowed in the public “uploads” folder**
 * This message appears if you have not enabled the option _“Prevent code execution
   in the public ‘Uploads’ folder”_ under _Settings > Hardening_.
 * It is generally recommended to disable PHP code execution in any public-facing
   directory where user uploads are stored, as an added security measure.
 * You can either enable the option and click _“Save”_, or if you do not wish to
   use this feature, dismiss the Dashboard notice about it by clicking the “X” behind
   the notice.
 * **#2: Frame Ancestors header not set**
 * This message appears if you haven’t configured [the Frame Ancestors security header (details here)](https://really-simple-ssl.com/definition/what-are-frame-ancestors/)
   found under _Settings > Content Security Policy_.
 * As the latter concerns a Premium feature, please reach us via **support(at)really-
   simple-ssl.com **if you have any further questions about this.
 * Kind regards, Janro
    -  This reply was modified 3 years, 2 months ago by [Jarno Vos](https://wordpress.org/support/users/jarnovos/).
 *  Thread Starter [darrenasmithmtm](https://wordpress.org/support/users/darrenasmithmtm/)
 * (@darrenasmithmtm)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/two-ssl-errors/#post-16601995)
 * Thank you.
 * **#1: Code execution allowed in the public “uploads” folder**
 * The setting is on: [https://d.pr/i/5V0tv7](https://d.pr/i/5V0tv7)
 * **#2: Frame Ancestors header not set**
 * I have premium. [https://d.pr/i/GTsuhs](https://d.pr/i/GTsuhs)
 *  Plugin Support [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * (@jarnovos)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/two-ssl-errors/#post-16604763)
 * Hi [@darrenasmithmtm](https://wordpress.org/support/users/darrenasmithmtm/),
 * If you’ve enabled the setting, the notice in the Dashboard about this feature
   might still be cached. You can dismiss the notice by clicking the **“X” **behind
   it.
 * The latter concerns Premium feature(s) and as we’re solely allowed to discuss
   the Free plugin on these forums, please reach us via **support(at)really-simple-
   ssl.com **if you require any further assistance with this.
 * Kind regards, Jarno

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

The topic ‘Two SSL Errors’ is closed to new replies.

 * ![](https://ps.w.org/really-simple-ssl/assets/icon-256x256.png?rev=2839720)
 * [Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)](https://wordpress.org/plugins/really-simple-ssl/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/really-simple-ssl/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/really-simple-ssl/)
 * [Active Topics](https://wordpress.org/support/plugin/really-simple-ssl/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/really-simple-ssl/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/really-simple-ssl/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * Last activity: [3 years, 2 months ago](https://wordpress.org/support/topic/two-ssl-errors/#post-16604763)
 * Status: resolved