BitsNStuff

I just performed the 4.0 upgrade on my web-facing server, and afterward the schemes had not been changed to https, so I have to apologize at the false alarm. On my staging server I either did not set those schemes like I thought I did, or some other plugin or theme had set them to https.

Anyway, this is all great information for me to have. Thanks again for the help.

I just tested out this theory, and I am confirming that the https redirects were all caused by those two urls on the General->Settings page being set to https. However I think part of the 3.9.2 to 4.0 upgrade is to change them (in the database) to https if they’re not that way already.

I did the upgrade to 4.0 , and then changed them back to http on the General->Settings page. After logging out of wordpress I navigated to a generic http root page and the redirect problem had disappeared.

Thanks for your help Samuel!

I just looked at the Settings->General page, and yes the urls there are set to https. In my notes I show that I had originally changed them to http so that creating new posts, pages, and multimedia would all be addressed in the database using http (which is what I wanted). It appears then that doing the 3.9.2 to 4.0 upgrade changed these to https.

I’ll do a bit more experimenting to see if I can perform the upgrade, then change those urls back to http and hopefully make this redirect problem go away.

Hi Samuel. No nothing I could find that would be causing this behavior. After numerous hours and several days I thought I’d try just copying the version 3.9.2 files manually back over to my wordpress staging directories, and after doing that the problem disappeared. I honestly don’t have the time or knowledge to start going through those php files trying to figure out which specific lines of code were the cause.

I could reproduce this quite easily. First do the 4.0 upgrade, and then within nginx use only a single server that responds on port 80. The result should be website not responding.

I don’t have a vital need to solve this, because on my web-facing server I just left it at version 3.9.2 .. I just thought I’d see if anyone else had experienced the same problem, and to bring this to peoples’ attention.

I just ran into this problem and spent many hours (over several days) trying to find out what had caused it. It started after I had done several updates at once, a bunch of themes, plugins, and wordpress update from version 3.9.2 to 4.0 .. I was doing this on my staging environment (Virtualbox) .. I run nginx, MySQL, wordpress, etc.

Suddenly I couldn’t load the root page, and I went into a redirect loop, going back and forth between my port 443 server and port 80 server. Going from port 443 to 80 was my own design, but going from port 80 back to 443 was a mystery. None of my settings explained why this was happening. I was being forced to use https.

I tried several things, removing plugins, themes, and wordpress itself. I finally narrowed it down to wordpress being the culprit. I downloaded version 3.9.2 and copied files manually back into the staging environment, and sure enough that fixed the problem. Something about the update from 3.9.2 to 4.0 was causing forced https. There are too many files for me to look through, so I just wanted to leave this here in the hopes it will get to concerned parties.