Hmmm... I'm not seeing any glaring issues in the log file. Is the browser console throwing any JS errors of any sort? You may also want to try deleting your Umbraco cache (~/App_Data/Temp), republishing & then try upgrading again.
How are you upgrading? a nuget update-package UmbracoCms or downloading the files & installing the old fashioned way? Be sure to make a backup of your working 8.0.1. I've had things explode countless times & ended up having to redo stuff when I don't do this.
I found the cause of the problem. Because of SEO reasons we have a rewrite rule in the Web.config file, which converts all URLs to lower case. Since Umbraco calls a lot of APIs with mixed case, we added a condition to the rule:
It turned out, that the update process uses an URL like /install/PostUpgradeOrSomethingLikeThis. I don't remember the exact name, but the POST uses a mixed case name and the path doesn't start with "umbraco", but with "install". So the rule converts the URL into /install/postupgradeorsomethinglikethis and returns a 301 redirect. The browser responds with a GET instead of a POST which ends in an error, since POST is the only allowed verb for the given route.
Upgrade to 8.0.2 fails
I try to upgrade an Umbraco 8.0.1 Site to 8.0.2. Umbraco recognizes the correct version:
If I press Continue the following error message appears:
Nothing appears in the log.
Does your Windows event viewer shed any light on the potential issue?
@Brandon: Nope. No entry from w3wp.
More log information: I posted an issue here and it contains a log file made in debug mode.
Hmmm... I'm not seeing any glaring issues in the log file. Is the browser console throwing any JS errors of any sort? You may also want to try deleting your Umbraco cache (~/App_Data/Temp), republishing & then try upgrading again.
How are you upgrading? a nuget update-package UmbracoCms or downloading the files & installing the old fashioned way? Be sure to make a backup of your working 8.0.1. I've had things explode countless times & ended up having to redo stuff when I don't do this.
I found the cause of the problem. Because of SEO reasons we have a rewrite rule in the Web.config file, which converts all URLs to lower case. Since Umbraco calls a lot of APIs with mixed case, we added a condition to the rule:
It turned out, that the update process uses an URL like /install/PostUpgradeOrSomethingLikeThis. I don't remember the exact name, but the POST uses a mixed case name and the path doesn't start with "umbraco", but with "install". So the rule converts the URL into /install/postupgradeorsomethinglikethis and returns a 301 redirect. The browser responds with a GET instead of a POST which ends in an error, since POST is the only allowed verb for the given route.
Adding a second condition solves the problem.
is working on a reply...