Title: HTTP not working (only HTTPS)
Last modified: August 21, 2016

---

# HTTP not working (only HTTPS)

 *  [bilica](https://wordpress.org/support/users/bilica/)
 * (@bilica)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/)
 * Hi,
 * After installation, website returns “Internal Server Error” for all pages on 
   the website.
 * However, pages are accessible using HTTPS.
 * Is this the expected behaviour ?
 * How do I create a rule to redirect HTTP pages to HTTPS using iThemes Security?
 * Thanks!
 * [https://wordpress.org/plugins/better-wp-security/](https://wordpress.org/plugins/better-wp-security/)

Viewing 15 replies - 1 through 15 (of 17 total)

1 [2](https://wordpress.org/support/topic/http-not-working-only-https/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/http-not-working-only-https/page/2/?output_format=md)

 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859177)
 * If your goal is to use https primarily, you can update your WP site URLs in Settings
   to include https.
 * Depending on your hosting, you might need a redirect rule for http to https to
   ensure http redirects. If it’s shared hosting, most likely that will be htaccess
   rewrite.
 * Note, make sure you actually do have SSL certificate installed on your hosting/
   server.
 * I would also highly recommend to use [WordPress HTTPS](https://wordpress.org/plugins/wordpress-https/)
   plugin instead to get better set of tools to manage https on your WP.
 *  [pratik9722](https://wordpress.org/support/users/pratik9722/)
 * (@pratik9722)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859215)
 * I have WordPress site that has SSL(not all page but only some pages are https
   because I don’t want to add https on all pages to avoid load on server and those
   https page are done by iThemes Security plugin) and now I want to redirect non-
   www. to www. site to avoid duplicate content issue(I hear that now Google don’t
   create any issue related to this but I also want to submit my site to other search
   engines) & I will going to past below code on 1st line of .htacces file to make
   redirect now-www to www site but I’m not sure that my code is right! or is it
   affect on other https pages?(in SSL page;all page are successfully redirecting
   to www [https://www.mywebsite.com](https://www.mywebsite.com))
 * I like to also mansion wordpress general setting
    WordPress Address (URL):[https://www.mywebsite.com](https://www.mywebsite.com)
   Site Address (URL):[https://www.mywebsite.com](https://www.mywebsite.com)
 * RewriteEngine on
    RewriteCond %{HTTP_HOST} ^([a-z.]+)?mywebsite\.com$ [NC] RewriteCond%{
   HTTP_HOST} !^www\. [NC] RewriteRule .? [http://www.%1mywebsite.com%](http://www.%1mywebsite.com%){
   REQUEST_URI} [R=301,L]
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859227)
 * If I understood correctly, you don’t want https on all pages. In this case, you
   probably should change WP address and Site address URLs to http:// version, and
   keep using page/post specific https feature that comes with ithemes security 
   plugin.
 * For non-www to www redirect, you need to edit default WP redirect code. Here’s
   what it should look like:
 *     ```
       # BEGIN WordPress
       RewriteEngine On
       RewriteCond %{HTTP_HOST} !^www\.
       RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
       RewriteBase /
       RewriteRule ^index\.php$ - [L]
       RewriteCond %{REQUEST_FILENAME} !-f
       RewriteCond %{REQUEST_FILENAME} !-d
       RewriteRule . /index.php [L]
       # END WordPress
       ```
   
 * **Note:** There is no need to add your domain here, it automatically detects 
   and redirects non-www to www domain.
 *  [pratik9722](https://wordpress.org/support/users/pratik9722/)
 * (@pratik9722)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859230)
 * wow man..your support is so fast like a pro & it’s work well,no error nothing.
   thanks.
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859240)
 * Glad I could help 🙂 We provide WP support to dozens of websites, so many issues
   I’ve seen over and over again. I actually had this issue saved in our database
   for quick reference.
 *  Thread Starter [bilica](https://wordpress.org/support/users/bilica/)
 * (@bilica)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859243)
 * Hi,
 * Thanks Viktor, but the original thread issue (my original post) has not been 
   addressed yet.
 * I have SSL certificate installed and working correctly for some pages (login 
   and admin dashboard). Other pages are non-SSL.
 * The problem is that, after the installation of the iThemes Security Plugin, all
   pages that are non-SSL (HTTP only) do not work unless I manually access them 
   by changing the address in the home bar of my browser to include HTTPS.
 * Thanks again,
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859262)
 * bilica, whats this set to? [http://i.imgur.com/h6GPbth.png](http://i.imgur.com/h6GPbth.png)
 *  Thread Starter [bilica](https://wordpress.org/support/users/bilica/)
 * (@bilica)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859265)
 * I tried all 3 options and the result is the same.
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859266)
 * When you turn SSL options off completely, does HTTP work then?
 *  Thread Starter [bilica](https://wordpress.org/support/users/bilica/)
 * (@bilica)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859267)
 * No, it does not… it only works when I access pages using HTTPS.
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859277)
 * Ok, what’s your WP and Site URLs are set to under Settings > General?
    – http
   or https?
 * Few things to try:
 * 1. Disable SSL options for this plugin.
    2. Reset your htaccess to default WP
   htaccess rewrites. (check, does it work?) 3. If not, check wp-config for 2 SSL
   lines that plugin adds. Remove them. Then check again. Does it work?
 * If it still does not work. Follow these instructions to completely remove plugin,
   so we can see if its really causing the issue:
    [http://wordpress.org/support/topic/how-to-reset-ithemes-security-plugin-to-fix-issues?replies=92](http://wordpress.org/support/topic/how-to-reset-ithemes-security-plugin-to-fix-issues?replies=92)
 * I’m assuming WP was working fine with https before you installed the plugin. 
   Just to confirm.
 *  Thread Starter [bilica](https://wordpress.org/support/users/bilica/)
 * (@bilica)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859278)
 * I am sorry but I should have mentioned before that I am using a multisite installation–
   hence I cannot find the Settings – General you just mentioned.
 * Thanks again for the help,
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859294)
 * That’s totally different beast, don’t have a lot of experience with Multisite.
 * As Codex says about site and WP urls:
    `These directions are for single installs
   of WordPress only. If you are using WordPress MultiSite, you will need to manually
   edit your database.`
 * It should be easy. You can check under wp_options table and look for site url
   and home url options to update them if necessary, or at least see what they are.
 * Others are having https issue too, so possible its plugin issue.
 *  Thread Starter [bilica](https://wordpress.org/support/users/bilica/)
 * (@bilica)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859297)
 * Thanks but I thought iThemes Security supported Multi-site installations.
 * So it is not supported ?
 *  [Viktor Nagornyy](https://wordpress.org/support/users/viktorix/)
 * (@viktorix)
 * [12 years ago](https://wordpress.org/support/topic/http-not-working-only-https/#post-4859302)
 * The plugin does support MS version, but either your MS has something thats conflicting
   with the plugin or its a bug in the plugin.
 * There are a lot of additional variables that can cause issues with MS.

Viewing 15 replies - 1 through 15 (of 17 total)

1 [2](https://wordpress.org/support/topic/http-not-working-only-https/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/http-not-working-only-https/page/2/?output_format=md)

The topic ‘HTTP not working (only HTTPS)’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 17 replies
 * 3 participants
 * Last reply from: [pratik9722](https://wordpress.org/support/users/pratik9722/)
 * Last activity: [11 years, 7 months ago](https://wordpress.org/support/topic/http-not-working-only-https/page/2/#post-4859520)
 * Status: not resolved