Title: [Plugin: WordPress HTTPS (SSL)] Not working for Shared SSL on Bluehost
Last modified: August 20, 2016

---

# [Plugin: WordPress HTTPS (SSL)] Not working for Shared SSL on Bluehost

 *  Resolved [dgebel](https://wordpress.org/support/users/dgebel/)
 * (@dgebel)
 * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/)
 * I’m having a lot of trouble getting this to work. I have installed and removed
   it a couple times, including going into the database and cleaning out the entries,
   creating new sites, etc.
 * – I set up a clean site with SimpleScripts
    – My WP testing site is: [http://example.com/testsite](http://example.com/testsite)–
   I deactivated and deleted all other plugins, then installed WordPress-https –
   I set the secure host as per BH documentation to: secure.bluehost.com/~example
   <— actually it’s ~username – left the port field blank – that uses the default
   443 right? – saved (the first time I installed it, the page never finished saving,
   but it has done so ever since.)
 * – logged out
    – went to secure.bluehost.com/~example/testsite/wp-admin –> it 
   went to [http://example.com/testsite/wp-login.php?redirect_to=http%3A%2F%2Fexample.com%2Ftestsite%2Fwp-admin%2F&reauth=1](http://example.com/testsite/wp-login.php?redirect_to=http%3A%2F%2Fexample.com%2Ftestsite%2Fwp-admin%2F&reauth=1)—
   I logged back in fine.
 * – when I check the Force SSL Administration page and save, I get sent to:
    `http://
   example.com/testsite/wp-admin/options-general.php?page=wordpress-https` and am
   told “Internet Explorer cannot display the webpage”
 * – I get the same message when I go to [http://example.com/testsite/wp-admin](http://example.com/testsite/wp-admin)
 * – when I go to [https://example.com/testsite/wp-admin](https://example.com/testsite/wp-admin)
   or [https://secure.bluehost.com/~examples/testsite/wp-admin](https://secure.bluehost.com/~examples/testsite/wp-admin)
   I just get 404s.
 * – the weirdest thing is, I think I was getting that redirect loop people have
   mentioned instead of being able to log in initially. When I first installed it,
   I was getting the SSL site with a lovely bright red address bar in IE due to 
   the shared address (which is fine for my use) and it just redisplayed the login
   screen.
 * I deleted the plugin & database contents and tried again, and got the above results.
   Then I completely deleted the site and all folders and database, and reinstalled
   WP from scratch and still got the above results. I suspected something is still
   being retained by bluehost, somewhere, but I created another new site in a different
   folder and still get the same results. I’m baffled now.
 * Help???
 * ** The plugin REALLY should clean out the database entries when deleting itself!
   Reinstalling, it grabbed all the entries from the first time and locked me out
   again. Blech.
 * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/)

Viewing 15 replies - 16 through 30 (of 31 total)

[←](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/?output_format=md)
[1](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/?output_format=md)
2 [3](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/3/?output_format=md)
[→](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/3/?output_format=md)

 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400918)
 * Hey Bozz,
 * I just pushed out 2.0.3. Update and see if it works. I believe I found where 
   the bug was.
 * Thanks,
    Mike
 *  [Marty](https://wordpress.org/support/users/bozzmedia/)
 * (@bozzmedia)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400919)
 * Great news! I will check it out and report back, thank you
 *  [Marty](https://wordpress.org/support/users/bozzmedia/)
 * (@bozzmedia)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400920)
 * Here’s what I’m getting with 2.0.3:
 * 1. Permalinks on Edit Page are looking good now, sweet!
 * 2. It doesn’t like me using a subdirectory in the settings (which is necessary
   if your wordpress blog is not hosted in the main public html directory of your
   account), when I do that it goes into some sort of loop.
 * I can get the plugin to give me this:
 * [https://secure.bluehost.com/~example/?page_id=35](https://secure.bluehost.com/~example/?page_id=35)
 * But, I need a URL that looks like this, which if I put it into my browser works
   well:
 * [https://secure.bluehost.com/~example/instrument/?page_id=35](https://secure.bluehost.com/~example/instrument/?page_id=35)
 * Is there a way to accommodate such a need without producing a double down of 
   the directories? This is the URL I’m getting with the subdirectory in the settings(
   secure.bluehost.com/~example/instrument/)
 * [https://secure.bluehost.com/~example/instrument/~example/instrument/?page_id=35](https://secure.bluehost.com/~example/instrument/~example/instrument/?page_id=35)
 * It’s sticking an extra “~example/instrument/” in there. Hopefully it’s a quick
   fix.. what do you think Mike? Thanks!
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400921)
 * Hey Bozz,
 * If your WordPress installation is located in a subfolder, you don’t need to add
   it to your SSL Host. The plugin takes care of that automatically. I’m not sure
   if that will fix anything, but give it a shot and let me know.
 * Thanks,
    Mike
 *  [Marty](https://wordpress.org/support/users/bozzmedia/)
 * (@bozzmedia)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400922)
 * if I set it to just secure.bluehost.com/~example then it is directed to a different
   site completely.
 * How is the plugin passing on the subdirectory info? My site is using its own 
   domain and my General settings are:
 * WordPress address (URL) [http://www.mydomainname.com](http://www.mydomainname.com)
   
   Site address (URL) [http://www.mydomainname.com](http://www.mydomainname.com)
 * This is an addon domain which then points to a subdirectory on another domain.
   I don’t think WordPress knows that, it just knows to go to the domain name.
 *  Thread Starter [dgebel](https://wordpress.org/support/users/dgebel/)
 * (@dgebel)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400923)
 * I haven’t had time to test the 3.3 version yet but…
 * Ya, I would need to specify the individual subdirectory too, because I have multiple
   add-on domains pointing to the subdirectory sites. And possibly another in my
   userid root directory.
 * Sounds like this indicates the source of the problem, that the plugin is assuming
   a root directory.
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400924)
 * Hey Bozz,
 * Well, in a normal setup, it takes the path info off the Home URL and appends 
   it to the SSL Host. It doesn’t assume the public directory, there’s just an issue
   when it’s building the secure URL.
 * This just a guess since I can’t easily test this scenario, but, replace this 
   block at line 504:
 *     ```
       if ( strpos($url_parts['path'], $https_url_path) === false ) {
       	if ( $url_parts['path'] == '/' ) {
       		$url = rtrim('/', $url) . $https_url_path;
       	} else {
       		$url = str_replace($url_parts['path'], $https_url_path . $url_parts['path'], $url);
       	}
       }
       ```
   
 * With this:
 *     ```
       if ( $url_parts['path'] == '/' ) {
       	$url = rtrim('/', $url) . $https_url_path;
       } else if ( strpos($url_parts['path'], $https_url_path) === false ) {
       	$url = str_replace($url_parts['path'], $https_url_path . $url_parts['path'], $url);
       }
       ```
   
 * Let me know.
 * Thanks,
    Mike
 *  [Marty](https://wordpress.org/support/users/bozzmedia/)
 * (@bozzmedia)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400925)
 * I tried the replacement but unfortunately got the same results with the double
   directories ([https://secure.bluehost.com/~example/instrument/~example/instrument/?page_id=35](https://secure.bluehost.com/~example/instrument/~example/instrument/?page_id=35)).
   Let me know if I can test anything else, thanks for being so responsive.
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400926)
 * Hey Bozz,
 * It would be easier if I could just log in and fix it. It’s hard to guess what
   code isn’t working right, lol. If you can, set me up a user that can edit plugins.
   My email is mike[at]mvied[dot]com.
 * Thanks,
    Mike
 *  Thread Starter [dgebel](https://wordpress.org/support/users/dgebel/)
 * (@dgebel)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400927)
 * Mike, did you get the “join” email I sent you as administrator?
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400928)
 * Hey dgebel,
 * I remember seeing it, but I can’t find it. Not sure what to search for in my 
   email. If you can send it again or tell me the email it came from, I’ll take 
   a look at your site. Sorry. 😛
 * Thanks,
    Mike
 *  [Marty](https://wordpress.org/support/users/bozzmedia/)
 * (@bozzmedia)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400929)
 * For those coming to this thread later, Mike fixed a couple bugs in 2.0.4 and 
   it’s working great with default permalinks! Thanks Mike!
 * I’m curious if anyone has managed to make their HTTPS configuration work with
   pretty permalinks using Shared SSL?
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400930)
 * Hey Bozz,
 * I’ve seen this issue many times and as far as I know you can’t use anything but
   the default permalinks.
 * The only thing I seem to remember someone mentioning was adding this to the .
   htaccess: `ErrorDocument 404 /index.php` But I have no idea if that works.
 * Thanks,
    Mike
 *  Thread Starter [dgebel](https://wordpress.org/support/users/dgebel/)
 * (@dgebel)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400932)
 * Mike,
    I’m still not working with 2.04 I’ve sent you the details with the subject“
   login credentials”.
 * I thought is was working with 2.02 as long as I didn’t force admin. I managed
   to get in at once point, but then the admin gave me only a 404 error.
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/2/#post-2400933)
 * Hey dgebel,
 * For some reason the cookie isn’t being set correctly. The login screen allows
   to you to log in, but when you get to the admin panel, the admin panel redirects
   you back to the login page. Give me some time to look it over and I’ll see if
   I can figure out what’s going on.
 * Thanks,
    Mike

Viewing 15 replies - 16 through 30 (of 31 total)

[←](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/?output_format=md)
[1](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/?output_format=md)
2 [3](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/3/?output_format=md)
[→](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/3/?output_format=md)

The topic ‘[Plugin: WordPress HTTPS (SSL)] Not working for Shared SSL on Bluehost’
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/)

 * 31 replies
 * 4 participants
 * Last reply from: [mvied](https://wordpress.org/support/users/mvied/)
 * Last activity: [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost/page/3/#post-2401013)
 * Status: resolved