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

---

# [Plugin: WordPress HTTPS (SSL)] Slash Truncated

 *  [wpcdn](https://wordpress.org/support/users/wpcdn/)
 * (@wpcdn)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/)
 * Hi,
 * With the new version of the plugin, I can’t get it to work with a shared SSL.
 * When I enter the hostname in the plugin, e.g.:
 * hostname.domain.com/~accountname
 * …and I save the settings in the plugin, everything looks good. However, SSL logins
   do not work, and the URL looks mangled, with the ~accountname in the URL twice.
 * When I check the settings again, I see the apparent reason: The slash has been
   truncated, and the hostname appears as:
 * hostname.domain.com~accountname
 * Any ideas?
 * Thanks,
 * Mark
 * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/)

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

 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/#post-2689582)
 * Hey Mark,
 * Is this only happening on the login form and nowhere else? Do pages appear to
   be working correctly otherwise?
 * Thanks,
    Mike
 *  Thread Starter [wpcdn](https://wordpress.org/support/users/wpcdn/)
 * (@wpcdn)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/#post-2689586)
 * Hi,
 * The problem is that I can’t get logged in via SSL. For example, I go to:
 * [https://hostname.domain.com/~accountname](https://hostname.domain.com/~accountname)
 * …and hit the login button, there is then a 404 because the browser is trying 
   to go to this URL:
 * [https://hostname.domain.com/~accountname/~accountname](https://hostname.domain.com/~accountname/~accountname)
 * Also, when I go to the login form as mentioned above, there is no CSS (Just the
   ugly unformatted form)…in case that’s relevant.
 * Thanks,
 * Mark
 *  Thread Starter [wpcdn](https://wordpress.org/support/users/wpcdn/)
 * (@wpcdn)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/#post-2689587)
 * Oh, if you were asking if the front-side pages of the blog work via SSL and that
   address, they do but the CSS is missing too (as expected).
 * Mark
 *  Plugin Author [mvied](https://wordpress.org/support/users/mvied/)
 * (@mvied)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/#post-2689592)
 * Hey Mark,
 * Thanks, that helped me track down the bug. I’ll be working on a fix.
 * Thanks,
    Mike
 *  Thread Starter [wpcdn](https://wordpress.org/support/users/wpcdn/)
 * (@wpcdn)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/#post-2689595)
 * Cool, thanks!
 * I’ll test promptly when the fix is available.
 * Mark

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

The topic ‘[Plugin: WordPress HTTPS (SSL)] Slash Truncated’ 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
 * 2 participants
 * Last reply from: [wpcdn](https://wordpress.org/support/users/wpcdn/)
 * Last activity: [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-slash-truncated/#post-2689595)
 * Status: not resolved