417 Missing Token in Back Office not resolved by F5
We started getting this error on an SSL site running Umbraco 7.7.7 and the issue continues after an upgrade to 7.7.13. The site is hosted on a Windows Server 2012 R2 VM.
Hi @Kevin, do you know which version after 7.10.1 has the solution for 417 missing token problem please? The problem occurs with the latest 7.13.0 but I didn't have this problem with 7.5.7.
Thanks in advance.
We resolved the issue and you were on the right track - we resolved by doing a complete site delete and rebuild from scratch. We're reviewing our automated deployment process now to make sure this doesn't happen again. Thanks again for your suggestions!
417 Missing Token in Back Office not resolved by F5
We started getting this error on an SSL site running Umbraco 7.7.7 and the issue continues after an upgrade to 7.7.13. The site is hosted on a Windows Server 2012 R2 VM.
This is a similar issue to U4-9873 and 417 Missing token suddenly occurring on all our sites except an F5, or more thorough "Empty Cache and Hard Reload", fails to resolve the 417 errors.
When first login to backoffice, none of the Umbraco cookies load (UMB-XSRF-TOKEN, UMB-XSRF-V, UMB_UCONTEXT). An F5 causes the cookies to load.
Failed calls are to GetCheck, GetDashboard?section=content, and GetSections. Fiddler reveals the X-UMB-XSRF-TOKEN header is missing from these calls.
I have attempted a number of fixes from the Forum without success:
I have not yet attempted these Forum suggestions:
Wondering if anyone else has encountered or resolved my particular flavour of these 417 backoffice problems?
Upgrade to Umbraco 7.10.1 did not resolve the issue.
Hi @Kevin, do you know which version after 7.10.1 has the solution for 417 missing token problem please? The problem occurs with the latest 7.13.0 but I didn't have this problem with 7.5.7. Thanks in advance.
A long shot, but have you tried something as simple as using an incognito window?
Thanks for the suggestion - issue not resolved with an Incognito window, and occurs in multiple browsers.
It was a long shot, but I had a similar problem and removing cookies resolved it for me 😔
I'm afraid I'm out of ideas! Other than a classic delete the bin folder (backing up in case) and running a rebuild!
We resolved the issue and you were on the right track - we resolved by doing a complete site delete and rebuild from scratch. We're reviewing our automated deployment process now to make sure this doesn't happen again. Thanks again for your suggestions!
I had this issue - it was a third party cookie tool running on the front end killing the UMB-XSRF-TOKEN Umbraco token cookie in the backoffice.
https://github.com/umbraco/Umbraco-CMS/issues/4138
is working on a reply...