Viewing 9 replies - 1 through 9 (of 9 total)
  • Same here, 302 loop when trying to enter the admin area. Frontend pages are still working. (edit: maybe they were working because they are cached to static files via .htaccess)

    Remote Address:104.18.41.191:443
    Request URL:https://www.***.com/wp-admin/
    Request Method:GET
    Status Code:302 Moved Temporarily
    Response Headers
    cache-control:no-cache, must-revalidate, max-age=0
    cf-ray:212a20f695240e36-MXP
    content-type:text/html; charset=UTF-8
    date:Sat, 08 Aug 2015 09:17:33 GMT
    expires:Wed, 11 Jan 1984 05:00:00 GMT
    location:https://www.***.com/wp-admin/
    pragma:no-cache
    server:cloudflare-nginx
    status:302 Moved Temporarily
    version:HTTP/1.1
    x-cf-powered-by:WP 1.3.18
    x-powered-by:PHP/5.5.24
    Request Headers
    :host:www.***.com
    :method:GET
    :path:/wp-admin/
    :scheme:https
    :version:HTTP/1.1
    accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
    accept-encoding:gzip, deflate, sdch
    accept-language:en-US,en;q=0.8,it;q=0.6
    cache-control:max-age=0
    cookie: [***]
    upgrade-insecure-requests:1
    user-agent:Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36

    Plugin Author Paul

    (@paultgoodchild)

    I just can’t replicate this. The logic is exactly the same as before except we’ve added the option to also look for “HTTP_X_FORWARDED_PROTO” which is a more generally used header (which CloudFlare also use)

    I have the same problem (after upgrading) with the redirect loop too. Where can I download plugin V 1.0.0?

    Plugin Author Paul

    (@paultgoodchild)

    I reverted back to V 1.0.0 and still had the redirect loop so I added the following lines to wpconfig…

    define(‘WP_HOME’,’https://www.yourdomain.com’);
    define(‘WP_SITEURL’,’https://www.yourdomain.com’);

    Voila! I gained access to wp-admin. I updated the plugin to V 1.1.0 and there was no problem after that.

    How strange!

    Plugin Author Paul

    (@paultgoodchild)

    Hey guys,

    I’ve released v1.2 just there – it’ll try to ensure that the plugin is the first plugin of the site to be loaded. My concern is that with the upgrade of the plugin, it moved its load position on your sites and it’s loading too late for some of you.

    Can I ask you to try out v1.2 ?

    Hi, I updated it to 1.2 but I had the same problem. Anyway I solved it by uninstalling and reinstalling the plugin. (to uninstall it I had to switch the site back to http, disable the CF “force https” rules, etc.)

    Thank you

    Thread Starter BatchHeader

    (@batchheader)

    @paul G. I have updated quite a few sites to v1.2.1 and have come across no errors.

    Thanks for all the updates and a great plugin.

    Plugin Author Paul

    (@paultgoodchild)

    Great! Glad it worked in the end and thanks for reporting back! Sorry for any trouble caused with the updates.

    May I ask, could you guys leave a nice review if you’re happy with the plugin, please? It’d really help!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Update to v1.1.0 created redirect loop’ is closed to new replies.