Title: [Plugin: WordPress HTTPS (SSL)] Shared SSL & non-default Permalinks: Let's solve this! Last modified: August 20, 2016 --- # [Plugin: WordPress HTTPS (SSL)] Shared SSL & non-default Permalinks: Let's solve this! * Resolved [Marty](https://wordpress.org/support/users/bozzmedia/) * (@bozzmedia) * [14 years ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/) * Hi everyone– * This plugin is awesome, and one issue holding us back from using it more is that at least with shared SSL situations (ex: bluehost, hostgator), one has to turn off pretty permalinks and instead use the default (ex: yoursite.com/?p=224). * So far the only hunch is to add to your .htaccess: `ErrorDocument 404 /index. php` * But this doesn’t seem to work for me, at least not with a blog installed into a subdirectory. As I understand it, WP isn’t processing the permalink structure because it’s not the default installation URL. The ? modifier seems to get around this. * Interestingly, if I use my shared ssl URL structure and only keep it the root directory of the blog, (ex: [https://secure.bluehost.com/~username/dev/cms/](https://secure.bluehost.com/~username/dev/cms/)) the page template loads but with a wordpress-processed 404 error message. * If I try to go one level further ([https://secure.bluehost.com/~username/dev/cms/apage](https://secure.bluehost.com/~username/dev/cms/apage)) then I get a real server 404 * Anyway, I figure there are hundreds of us who are effected by this and it would be great for us to solve this problem collectively so we can all benefit from not having to turn on global default permalinks to get it to work with shared SSL. * Would really appreciate hearing from others who are trying to work around this. Thanks! * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/) Viewing 15 replies - 1 through 15 (of 15 total) * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [14 years ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2769906) * To my knowledge, there is no way around this. The proxy sitting in front of the server hosting WordPress is not properly passing the Request URI so WordPress doesn’t know where to send the user (it can’t even pull up the front page). Unfortunately, this is caused by a proxy not being configured correctly, but sometimes it is intentional by the hosting company because they do not want you using the Shared SSL certificate with WordPress or anything like that. * That’s what I’ve learned from talking to users of my plugin that have run into this issue. * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [14 years ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2769907) * I do have a theory that if I can somehow get WordPress to strip off the extra Shared SSL path information (`/~username`) before it tries to query the current page, that it would cause the URL’s to be looked up by their correct path, and it would work. Just a theory. * Thread Starter [Marty](https://wordpress.org/support/users/bozzmedia/) * (@bozzmedia) * [14 years ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770006) * Thanks for the insight! * Is there any specific behavior or events you are picking up that indicates an improper proxy setting? * If we can’t get the proxy to play nice, can we help WordPress anticipate these requests and serve up the proper information, perhaps through .htaccess ? * Thread Starter [Marty](https://wordpress.org/support/users/bozzmedia/) * (@bozzmedia) * [14 years ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770007) * Is it possible to make these configuration options conditional on https? Maybe a conditional wp-config.php? * ``` define('WP_SITEURL', 'https://secure.bluehost.com/~USERNANAME/BLOG_DIRECTORY'); define('WP_CONTENT_URL', 'http://www.site.com/BLOG_DIRECTORY/wp-content'); ``` * Thanks! * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770039) * This should be fixed in the latest release. I found the filter for WordPress’ rewrite rules and that allowed me to add a filter including the extra path information, causing the pages to now be found. * Thread Starter [Marty](https://wordpress.org/support/users/bozzmedia/) * (@bozzmedia) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770040) * Great news! I’ll try it out, thank you!! * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770041) * Try the [development version](http://downloads.wordpress.org/plugin/wordpress-https.zip) if you’re going to be trying soon. * [hurucheng1212](https://wordpress.org/support/users/hurucheng1212/) * (@hurucheng1212) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770044) * Bozz Member Posted [4 days ago #](http://wordpress.org) * Great news! I’ll try it out, thank you!! * Mvied Member Posted 4 days ago # * Try the development version if you’re going to be trying soon. * R * [phetefirst](https://wordpress.org/support/users/phetefirst/) * (@phetefirst) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770045) * Thanks for the great plugin, though I am having the same issues (bluehost shared ssl, 404s on any pages with forced ssl). I tried the development version you recently posted, this did not solve the issue. What am I doing wrong? 😉 * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770046) * I’m not sure if the plugin has been tested with Bluehost’s Shared SSL yet. * If you could give me admin access and FTP access to a WordPress install on your server and the Shared SSL URL, I may be able to get the plugin to work on Bluehost. Some Shared SSL’s will never work. * [phetefirst](https://wordpress.org/support/users/phetefirst/) * (@phetefirst) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770047) * Thank you, I just sent you an email. * [Josiah](https://wordpress.org/support/users/colewebdev/) * (@colewebdev) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770049) * I just tried again with the development version and am still getting a 404 on HostGator. * I’m assuming the “domain mapping” feature is where we configure this, although I didn’t see any documentation so I may have the values wrong. * Can you explain this new feature so we can test? * My secure URL format is the following: * [https://secure000.websitewelcome.com/~username/](https://secure000.websitewelcome.com/~username/) * [sanjayidhatiya](https://wordpress.org/support/users/sanjayidhatiya/) * (@sanjayidhatiya) * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770061) * i had Same issue. * Some Pages Of wordpress does not work with ssl with permalinks on. * but after reading many posts and trying to be solved i found the solution. * just add your page name means permalinks url to “URL Filter”. * And it’s Work For me * thanks for such a great Plugin. * [Chad Warner](https://wordpress.org/support/users/chad-warner/) * (@chad-warner) * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770063) * I just tested the dev version with Hostmonster (owned by Bluehost, with the same shared SSL configuration) and still get redirect errors and 404 pages when trying to secure my login. All I want to do is use my shared SSL to secure my login form. * I’d be happy to help troubleshoot. Just let me know what details you need. * [Chad Warner](https://wordpress.org/support/users/chad-warner/) * (@chad-warner) * [13 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770084) * Has there been any progress on this (specifically, using shared SSL from Bluehost or Hostmonster)? Viewing 15 replies - 1 through 15 (of 15 total) The topic ‘[Plugin: WordPress HTTPS (SSL)] Shared SSL & non-default Permalinks: Let's solve this!’ 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/) ## Tags * [HTTPS](https://wordpress.org/support/topic-tag/https/) * [SSL](https://wordpress.org/support/topic-tag/ssl/) * 15 replies * 7 participants * Last reply from: [Chad Warner](https://wordpress.org/support/users/chad-warner/) * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-shared-ssl-non-default-permalinks-lets-solve-this/#post-2770084) * Status: resolved