Title: [Plugin: WordPress HTTPS (SSL)] force SSL
Last modified: August 20, 2016

---

# [Plugin: WordPress HTTPS (SSL)] force SSL

 *  Resolved [gcall166](https://wordpress.org/support/users/gcall166/)
 * (@gcall166)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/)
 * If ‘Force SSL’ check box is checked in post, post does not load:
    Secure Connection
   Failed An error occurred during a connection to srtonlinemedia.com.
 * SSL received a record that exceeded the maximum permissible length.
 * (Error code: ssl_error_rx_record_too_long)
 * the page I am trying to load is [https://srtonlinemedia.com/test-https/](https://srtonlinemedia.com/test-https/)
   and it loads OK as http (SSL box unchecked)
 *  The page you are trying to view can not be shown because the authenticity of
   the received data could not be verified.
    Please contact the web site owners 
   to inform them of this problem. Alternatively, use the command found in the help
   menu to report this broken site.
 * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/)

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

 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320329)
 * Hey gcall166,
 * It seems like there’s an error with your SSL Certificate. Try getting in touch
   with your hosting provider to see if they can fix it for you.
 * Thanks,
    Mike
 *  Thread Starter [gcall166](https://wordpress.org/support/users/gcall166/)
 * (@gcall166)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320353)
 * Hi,
    Many thanks, and I had not set up the shared server settings correctly. 
   I have now set up the shared secure server info that Hostgator supplied, and 
   can access the front end of srtonlinemedia.com via the SSL HOST they gave. BUT
   when I try it with my post; [https://secure647.hostgator.com/~gcall166/SRTONLINEMEDIA.COM/test-https/](https://secure647.hostgator.com/~gcall166/SRTONLINEMEDIA.COM/test-https/)
   I now get Error 404. Any ideas? thanks Simon
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320368)
 * Hey Simon,
 * Some Shared SSL’s won’t work with custom permalinks. Set your permalink structure
   to the default and it should work.
 * Thanks,
    Mike
 *  Thread Starter [gcall166](https://wordpress.org/support/users/gcall166/)
 * (@gcall166)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320370)
 * Wow. That did it. thanks Mike!!
 *  [dankru](https://wordpress.org/support/users/dankru/)
 * (@dankru)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320393)
 * Hi folks,
 * it took me 2 and a half days to find this enlightening explanation:
    “Some Shared
   SSL’s won’t work with custom permalinks.” **Bluehost certainly does not work!**
   The permalink trap should be mentioned somewhere on the settings page …
 * Thanks anyway, Mike!
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320398)
 * Hey dankru,
 * In the next version, when the user updates their SSL Host, the plugin is going
   to try to hit a random post on the site and see if it produces a 404. If so, 
   it will throw a warning to the user that custom permalinks need to be disabled.
 * Also, I’m adding this to the FAQ since it comes up so often.
 * Thanks,
    Mike
 *  [olametro](https://wordpress.org/support/users/olametro/)
 * (@olametro)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320484)
 * Admin page access is no more possible now with the above error after I tried 
   to change the HTTP to HTTPS in the general settings. When I try to login back,
   it says:”SSL received a record that exceeded the maximum permissible length.
 * (Error code: ssl_error_rx_record_too_long)” Please HELP, HELP, and HELP!
    My 
   url is cccusahq.org.
 *  [olametro](https://wordpress.org/support/users/olametro/)
 * (@olametro)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320485)
 * Hello Mvied, or any other helper,
    Please can you explain how to log in into 
   amy admin when you’re logged out. My url is: [http://cccusahq.org](http://cccusahq.org).
   I tried to changed HTTP to HTTPS in the general settings in the dashboard, and
   hit save button. That’s it, it quickly displaced an error that: “Secure Connection
   Failed An error occurred during a connection to cccusahq.org. SSL received a 
   record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)”
 *  Pleas help as i can not get to my admin again. Nothing can be accessed at all
   please.
 * Thanks, Ola

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

The topic ‘[Plugin: WordPress HTTPS (SSL)] force SSL’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-https_bec2c9.svg)
 * [WordPress HTTPS (SSL)](https://wordpress.org/plugins/wordpress-https/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-https/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-https/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-https/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-https/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-https/reviews/)

 * 8 replies
 * 4 participants
 * Last reply from: [olametro](https://wordpress.org/support/users/olametro/)
 * Last activity: [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-force-ssl/#post-2320485)
 * Status: resolved