Title: Mixed Content error when forcing https
Last modified: November 1, 2020

---

# Mixed Content error when forcing https

 *  [gr33ngrl](https://wordpress.org/support/users/gr33ngrl/)
 * (@gr33ngrl)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/mixed-content-error-when-forcing-https/)
 * Receiving the error Mixed Content: The page at ‘[https://spiritvoyage.com/&#8217](https://spiritvoyage.com/&#8217);
   was loaded over HTTPS, but requested an insecure script ‘[http://spiritvoyage.com/wp-content/plugins/dynamicconditions/public/js/dynamic-conditions-public.js?ver=1.4.6&#8217](http://spiritvoyage.com/wp-content/plugins/dynamicconditions/public/js/dynamic-conditions-public.js?ver=1.4.6&#8217);.
   This request has been blocked; the content must be served over HTTPS.

Viewing 1 replies (of 1 total)

 *  Plugin Author [crazypsycho](https://wordpress.org/support/users/crazypsycho/)
 * (@crazypsycho)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/mixed-content-error-when-forcing-https/#post-14266842)
 * Hello [@gr33ngrl](https://wordpress.org/support/users/gr33ngrl/)
 * you should look in your wordpress settings if your site-url is entered with https.

Viewing 1 replies (of 1 total)

The topic ‘Mixed Content error when forcing https’ is closed to new replies.

 * ![](https://ps.w.org/dynamicconditions/assets/icon-256x256.jpg?rev=1969812)
 * [Dynamic Conditions](https://wordpress.org/plugins/dynamicconditions/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/dynamicconditions/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/dynamicconditions/)
 * [Active Topics](https://wordpress.org/support/plugin/dynamicconditions/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/dynamicconditions/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/dynamicconditions/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [crazypsycho](https://wordpress.org/support/users/crazypsycho/)
 * Last activity: [5 years, 1 month ago](https://wordpress.org/support/topic/mixed-content-error-when-forcing-https/#post-14266842)
 * Status: not resolved