WordPress.org

1. newelley
   Member
   Posted 6 months ago #

   Hi,
   This has been driving me crazy! I have purchased a SSL certificate with 123reg (who my hosting and domain is with) and i can see that my site is now protected with AlphaSSL. However when i activate your plugin and click to checkout, i just gets stuck on a redirect loop. AHHHHHH!!

   Website is http://www.grandmasquerade.co.uk

   Can't work this one out, please help!!!

   Thanks :)

   http://wordpress.org/extend/plugins/wordpress-https/

2. newelley
   Member
   Posted 6 months ago #

   Anyone?

3. Mvied
   Member
   Posted 6 months ago #

   I just pushed out version 2.0.1. Let me know if it fixes your issue.

   Thanks,
   Mike

4. newelley
   Member
   Posted 6 months ago #

   Hi,

   No this didn't work, it's really annoying as if you switch the plugin off, go to the checkout and manually add the s to https it works fine but forcing SSL on that page causes it to go mad. Really can't work this one out. I've searched google and cant find a resolve that works for me.

   Any other ideas?
   Thanks again :)

5. Mvied
   Member
   Posted 6 months ago #

   Hey newelley,

   The redirect loop is a bug in the plugin. I wouldn't expect you to find a fix on Google, haha.

   The quickest way I could fix it is if you created an admin account for me on the site where I could alter my plugin to come up with a fix. The redirect loop issue can be caused by a number of things, and it's never really easy to pinpoint what's causing it.

   If you'd like, you can create an account for mike[at]mvied[dot]com.

   Thanks,
   Mike

6. newelley
   Member
   Posted 6 months ago #

   Hi Mike,

   Thanks a lot, i have emailed you the details.

   Cheers :)

7. Mvied
   Member
   Posted 6 months ago #

   Hey newelley,

   It looks like your hosting provider is using a proxy that is not configured correctly. WordPress (and WordPress HTTPS) has no way of telling if the current page is HTTPS. This causes the plugin to not fix elements on HTTPS pages and when a page is forced to HTTPS, the plugin always thinks the page is HTTP, so it continuously tries to redirect to HTTPS.

   There's not really anything I can do about that. Talk to your hosting provider about it and see if they can help. If they can't, I would recommend a new hosting provider.

   Thanks,
   Mike

8. newelley
   Member
   Posted 6 months ago #

   Thanks a lot for trying Mike. I'll get onto 123reg. I've read so many bad reviews about them, seriously regretting going for the cheap option!

   Thanks again

9. mistaecko
   Member
   Posted 6 months ago #

   > WordPress (and WordPress HTTPS) has no way of telling if the current page is HTTPS.
   Can you elaborate on this a bit?

   I installed the 'Force SSL on admin' on a development server of mine (Apache2 on Ubuntu) and it got stock in the redirect loop on the login page.

   If I run a simple test file like this:

   <?php
   if($_SERVER['HTTPS']){
   echo 'you are secured';
   }else{
   echo 'you are not secured';
   }
   ?>

   it detects the HTTPS connection correctly.

   I guess that above file should fail on @newelley's shared host, and my problem is a different one. Correct?

10. Mvied
    Member
    Posted 6 months ago #

    Hey mistaecko,

    Yes, that's right. There is a bug in 2.0.1. I just pushed up version 2.0.2. After updating, save your WordPress HTTPS settings and it should be fixed. Let me know.

    Thanks,
    Mike

11. mistaecko
    Member
    Posted 6 months ago #

    Thanks for your quick reply!

    No sorry. Still not working. As soon as I activate the plugin I am kicked out, even when I am logged in via https at that time.

    http://twitpic.com/7k0w1n

    (All blurred out parts mention the same host)

    This is not a clean/fresh install, so there might be interactions with an older config or another plugin. The .htaccess file is clean though and only contains the standard wordpress index.php rewrite.

    I came up with my own handwritten .htaccess based solution so not sure how much time I will invest in troubleshooting this, sorry.

12. Mvied
    Member
    Posted 6 months ago #

    Hey mistaecko,

    Yeah, the bug that the previous version caused is probably the issue. If you're comfortable with editing your database, you can go in and delete the entries in wp_options that start with 'wordpress-https' and that should clear it up.

    If you're not comfortable playing around in the database, you can delete WordPress HTTPS, install 1.9.2, update your SSL Host, and then upgrade back to 2.0.2. That should clear it up.

    Thanks,
    Mike

13. mistaecko
    Member
    Posted 6 months ago #

    Thanks, deleting the wp_options entries did the trick!

    The 'Force SSL Administration' option works solid now.

    mistaecko

Reply

You must log in to post.