I have been running Umbraco 7.5.4 for a while in Azure, I have 2 copies running on different servers one for production and one for testing, and a local one for development.
So we just pushed an update a couple of days ago and when we try to access the back end its blank sometimes, looking at the console it shows several 500 error for files (mydomain.azurewebsites.net/umbraco/backoffice/UmbracoApi/Dashboard/GetDashboard?section=content 500 (Internal Server Error) ), we hit reload and suddenly it works fine. But as we keep using the backend the errors keep showing up every now and then. It also sometimes happens with the css in the frontend
Now for the fun part, this does not happen neither on the developing machine, nor on the other azure instance that we have. for testing.
The developing/testing instance is on a basic plan and the production site (where the error is happening) is on the Standard 2 plan as recommended. The funny thing is that this did not happen for a year, neither when we updated to 7.5.4, it just started happening with our latest update (we just changed how the user logs in). In the test azure site everything works fine.
We made the config adjustments for the cloud as recommended in the documentation, but it didn't help. We have cleaned up the cache folders and restarted the server, but the problem persists. We even deleted the whole site and copy the test site with no success.
Umbraco intermitent backend 500 error
Hello Everyone,
I have been running Umbraco 7.5.4 for a while in Azure, I have 2 copies running on different servers one for production and one for testing, and a local one for development.
So we just pushed an update a couple of days ago and when we try to access the back end its blank sometimes, looking at the console it shows several 500 error for files (mydomain.azurewebsites.net/umbraco/backoffice/UmbracoApi/Dashboard/GetDashboard?section=content 500 (Internal Server Error) ), we hit reload and suddenly it works fine. But as we keep using the backend the errors keep showing up every now and then. It also sometimes happens with the css in the frontend
Now for the fun part, this does not happen neither on the developing machine, nor on the other azure instance that we have. for testing.
The developing/testing instance is on a basic plan and the production site (where the error is happening) is on the Standard 2 plan as recommended. The funny thing is that this did not happen for a year, neither when we updated to 7.5.4, it just started happening with our latest update (we just changed how the user logs in). In the test azure site everything works fine.
We made the config adjustments for the cloud as recommended in the documentation, but it didn't help. We have cleaned up the cache folders and restarted the server, but the problem persists. We even deleted the whole site and copy the test site with no success.
Any ideas will be appreciated.
is working on a reply...