Title: [Plugin: WordPress HTTPS] strange redirection
Last modified: August 19, 2016

---

# [Plugin: WordPress HTTPS] strange redirection

 *  [UMdB](https://wordpress.org/support/users/umdb/)
 * (@umdb)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/)
 * Hi,
    I’m trying to implement a way to have all the admin part with ssl. I’ve 
   installed the plugin. My ssl connection is on a hostgator server with a ssl shared
   certificate. I’ve added the following string to the **wp-config** file
 * _define(‘FORCE\_SSL\_ADMIN’, true);_
 * in the configuration part of the plugin I flagged the “Shared SSL”
    and added
   the encripted url [https://nameserve.hostgator.com/](https://nameserve.hostgator.com/)**
   ~userid**
 * the problem is that when I try to connect I’m redirected to the site
    [https://nameserve.hostgator.com/](https://nameserve.hostgator.com/)**
   ~userid**/**~userid**
 * I’ve tryed to remove the **~userid** part, but it does not work 🙁
 * any idea?

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

 *  [kitchin](https://wordpress.org/support/users/kitchin/)
 * (@kitchin)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/#post-2028651)
 * Doing the same thing here. The plugin is buggy when using if for shared hosting
   and FORCE_SSL_ADMIN.
 * I have a bunch of code fixes I am testing out, but then maintaining the changes
   becomes a chore. If anybody wants to test the new code, I can post it somewhere.
 * The main changes:
 * 1. Override the pluggable function **wp_redirect()**.
 * 2. WP will aggressively change
    **a. [http://example.com/dir](http://example.com/dir)**
   to **b. [https://example.com/dir](https://example.com/dir)** when what we want
   is **c. [https://shared.example2.com/dir2](https://shared.example2.com/dir2).**
   So str_replace(b,c) in a few obvious & obscure places. The b should never appear
   anywhere, so that makes it easier.
 * 3. The part of **process()** at line 221, starting with:
    “$url_path = parse_url(
   $url, PHP_URL_PATH)” is completely borked. Replaced all that code.
 * 4. When editing a page, make the **“View page”** and **“Preview”** links stay
   on HTTPS for all pages. Easier to use it that way.
 * 5. Clean up a few warnings when in WP debug mode, and remove some empty iterations
   due to off-by-one.
 * I have some good debug functions now.
 *  [dyrk](https://wordpress.org/support/users/dyrk/)
 * (@dyrk)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/#post-2028656)
 * Thanks for the help Kitchin.
 * My problem is similar, though I’m only trying to force a single frontend page
   to SSL – with shared SSL certificate.
 * I end up with an apache 404 with a message:
 * ‘index.php was not found on this server.’
 * I am using %category%/%postname% permalinks.
 * Any ideas how I can fix this? Or is this still the same problem as above even
   though it’s not admin?
 *  [kitchin](https://wordpress.org/support/users/kitchin/)
 * (@kitchin)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/#post-2028663)
 * I posted part of my fix here: [http://wordpress.org/support/topic/plugin-wordpress-https-trying-to-get-property-of-non-object](http://wordpress.org/support/topic/plugin-wordpress-https-trying-to-get-property-of-non-object)
   
   but I’m not sure if that’s enough to get it working for you.
 *  Thread Starter [UMdB](https://wordpress.org/support/users/umdb/)
 * (@umdb)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/#post-2028847)
 * Is there any news about the fix of the problem from the developer of this plugin?
   Mvied, have you tryed kitchin fix?
 *  [matthewjamesshaw](https://wordpress.org/support/users/matthewjamesshaw/)
 * (@matthewjamesshaw)
 * [15 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/#post-2028855)
 * [@dyrk](https://wordpress.org/support/users/dyrk/), I’m trying to do the same
   thing — force a couple pages to SSL.
 * From what I understand, this isn’t supposed to be hard to implement… But the 
   shared base URL from my host (bluehost) doesn’t seem to be working

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

The topic ‘[Plugin: WordPress HTTPS] strange redirection’ 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/)

 * 5 replies
 * 4 participants
 * Last reply from: [matthewjamesshaw](https://wordpress.org/support/users/matthewjamesshaw/)
 * Last activity: [15 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-strange-redirection/#post-2028855)
 * Status: not resolved