Windows server infinite redirect after upgrading to 3.1

I’m getting same error on my site (windows 2003 server) – but I’m not using any extra modules for permalinks – it seems to be something 3.1 is doing under windows, even with ‘standard’ links.

Me too. I won’t post my ordeal (I have access to my server so I’ve tried a lot) but you can look up my posts.

While I can get to the back end of my site, I can’t get to the front end (IE just hangs, but FF and Chrome were nice enough to give me a redirect / loop error message).

Same here. I have a test server running on Windows Server and IIS 6 with standar permalinks, and I can’t access the admin dashboard.
I can see the frontend, though

LOL – well I think I’d rather the front end show and seem ok. ?? At least clients wouldn’t be calling asking “Where is my website!”

Seems like there are enough of us having an issue – wonder why someone from WordPress isn’t saying something, or at least acknowledging?

I’m having a similar problem. Tried a manual upgrade on an iis7 server and now I can login. The front end works fine but I have no access to admin.

I can see there has been no consensus as to how to rectify this, has there?

I’ve been posting since this morning. :-\

I agree AardvarkGirl – the front end would at least mean my visitors were seeing something while i wait for someone from the dev team to post

Same here, but it concerns only the homepage. WP-Admin Backend is accessible.

I’m having the same issue. I can access all pages except the homepage.

Have you tried:
– deactivating all plugins to see if this resolves the problem? If this works, re-activate the plugins one by one until you find the problematic plugin(s).
– switching to the default theme to rule out any theme-specific problems?
– re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress?
– Try re-saving your permalink structure or using the default structure at Settings/Permalinks in your admin panel. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.
-renaming your .htaccess to test.htaccess

For those who cannot log in:
– resetting the plugins folder by using FTP or whatever file management application your host provides. Sometimes, an apparently inactive plugin can still cause problems.
– switching to the default theme by renaming your current theme’s folder in wp-content/themes using FTP or whatever file management application your host provides.
-renaming your .htaccess to test.htaccess

pretty much done all of that..

did the reset plugins, set to default theme. went into the permalinks page and hit save (i’m using default structure anyway)

remember we’re saying it’s on windows – so no .htaccess files to play with as they are unix/linux only.

I’ve gone through all those steps and it’s still going into the infinite loop on permalinks that do not include /index.php/ at the beginning or are just using the /?p= format.

I just installed this plugin:
https://www.ads-software.com/extend/plugins/permalink-fix-disable-canonical-redirects-pack/

And it seems to have fixed my issue. I can bring up all the site pages now.

keesiemeijer

Have you tried:
– deactivating all plugins to see if this resolves the problem? If this works, re-activate the plugins one by one until you find the problematic plugin(s).

Yup. Was able to deactivate them all in the admin. Someone suggested go change the plug in folder name – I not only tried it on FTP but actually remoted onto the server and it would not grant me access to change the plug in name (access denise, in use…).

– switching to the default theme to rule out any theme-specific problems?

That was the first thing I did. And to rule that out I ran the install on another wordpress site I have (a test that is a stock install – only a child theme and no plug ins) and it bombed as well.

– re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress?

I did one better – I killed EVERYTHING and downloaded and unzipped a fresh 3.1 to my server and put the files on the directory by hand.

Then on our WP test site we killed EVERYTHING including the database and did a ‘from scratch’ brand new install of 3.1 and had the same exact issues we had with the auto-updated site.

– Try re-saving your permalink structure or using the default structure at Settings/Permalinks in your admin panel. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.
-renaming your .htaccess to test.htaccess

I’m on a windows machine.

I’ve tried to change the perm links structure through the admin page to see if that gives it a kick – no change.. so changed it back to standard
/?p= format

I can’t believe this isn’t a fundamental bug/flaw in the base code – maybe not been tested on windows servers enough?

i hope someone in the dev team is taking note – every second that ticks by is lost visitors to my site.

I guess I need to read up on going back a version.. I guess I can’t get away with copying files in from 3.0.5 but leaving the db as is? (any db changes for 3.1?)