We are getting an odd error in the logs with regards to scheduled publishing.
2016-03-07 16:17:39,536 [44] ERROR [http://www.*****.com.au/umbraco/RestServices/ScheduledPublish/Index] Umbraco.Web.Mvc.AdminTokenAuthorizeAttribute – [P4776/T66/D6] Failed to format passed in token value
System.Security.Cryptography.CryptographicException: Error occurred during a cryptographic operation.
at System.Web.Security.Cryptography.HomogenizingCryptoServiceWrapper.HomogenizeErrors(Func`2 func, Byte[] input)
at System.Web.Security.FormsAuthentication.Decrypt(String encryptedTicket)
at Umbraco.Core.StringExtensions.DecryptWithMachineKey(String value)
at Umbraco.Web.Mvc.AdminTokenAuthorizeAttribute.AuthorizeCore(HttpContextBase httpContext)
This error pops up every minute.
Our site is on Umbraco 7.2.8 running on Azure, and has 2 domain names attached for different parts of the site. We have only just moved it to Azure, and never had this issue when it was running on a dedicated server.
It seems to fail during the decryption of the token?
We have added a machine key to the web.config just in case but this has no effect.
I should point out another issue with this that might be causing the problem but we are not sure how to solve.
Our tree is a little different. It looks like this domains have been swapped out for alternatives. Lets call them domain A and Domain B
Home <--- Domain A assigned here
|- page
|- page
|- Blog <--- Domain B assigned here
I know this looks a little odd but originally the blog was just a page on the site but they registered a separate domain for it.
Now this setup worked fine on the old production site. And it works on Azure except for the error mentioned above.
But what we are noticing is that all the scheduled publishing calls are registered against domain B instead of domain A? In azure the primary domain assigned to the Web App for some reason has ended up being domain B? Could this cause the cryptography error because the token is for domain A when its expecting domain B?
Umbraco 7.2.8 Umbraco Scheduled publishing error on Auzre
We are getting an odd error in the logs with regards to scheduled publishing.
This error pops up every minute.
Our site is on Umbraco 7.2.8 running on Azure, and has 2 domain names attached for different parts of the site. We have only just moved it to Azure, and never had this issue when it was running on a dedicated server.
It seems to fail during the decryption of the token?
We have added a machine key to the web.config just in case but this has no effect.
Anyone else seen anything like this?
I should point out another issue with this that might be causing the problem but we are not sure how to solve.
Our tree is a little different. It looks like this domains have been swapped out for alternatives. Lets call them domain A and Domain B
I know this looks a little odd but originally the blog was just a page on the site but they registered a separate domain for it.
Now this setup worked fine on the old production site. And it works on Azure except for the error mentioned above.
But what we are noticing is that all the scheduled publishing calls are registered against domain B instead of domain A? In azure the primary domain assigned to the Web App for some reason has ended up being domain B? Could this cause the cryptography error because the token is for domain A when its expecting domain B?
Update. We were missing a setting in the umbracosettings.config for the baseUrl of the scheduled publishing. Adding in the attribute had no effect :(
will try an upgrade to a latter version to see if this resolves it.
And now for no reason we can see the errors have stopped. ??
Will keep this thread open as we are trying to figure it out still.
Hi Peter - did you ever get to the bottom of this? I am also seeing this issue on 7.2.8 (not on Azure).
I have seen it in the past and as you describe it suddenly just stopped, but now it has started again and been going for a few hours.
is working on a reply...