New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Umbraco 9.5.1: Backend UI not displayed after login when deployed in a VM behind Azure application gateway V1. #12580
Comments
Which WAF rule causes this needs investigation. |
This appears to be a Umbraco issue as there are mandatory rules that cannot be disabled in the Application Gateway V1 + WAF. WAF ModSecurity is detecting SQL injections!!
|
Hey there @nikhilramabhadra and sorry for the late response! This sounds like an excellent question for the forums where our friendly community can help you find the best solution for your requirements. Make sure to head on over to https://our.umbraco.com and ask follow up questions there. |
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
9.5.1
Bug summary
We migrated our site from Umbraco on .NET 4.7.2 to Umbraco .NET 5 9.5.1. I deployed it in production which is behind an Azure application gateway V1. The site is https and configure with a certificate.
When we try to login we see (ModSecurity Action) errors as seen in the attached picture. Even in the case of .NET 4.7.2 we would see errors with Angular but it would login.
It logs in but none of the backend UI is displayed. Test environment has no gateway and works fine.
Please help.
[https://our.umbraco.com/forum/using-umbraco-and-getting-started/109269-umbraco-951-errors-logging-into-backend-when-deployed-in-a-vm-behind-azure-application-gateway-v1](Umbraco Forum Query)
)
Specifics
Error occurs in Chrome 102.0.5005.63, Edge 102.0.1245.39
Steps to reproduce
Deploy Umbraco 9.5.1 behind Microsoft application gateway v1.
Login to back end and check UI.
Expected result / actual result
The backend UI with tree should be displayed.
The text was updated successfully, but these errors were encountered: