We are migrating from Umbraco 13.3.0 to 17.5.0, hosted on Azure App Service with Azure SQL Database.
Initially, clicking Continue on the upgrade screen showed “Unknown error.” After upgrading the Azure SQL Database tier, this message disappeared, and the database migration completed successfully. However, the application still returns an Internal Server Error (HTTP 500) and then redirects to the Umbraco backoffice.
The same application works fine locally without any issues.
Has anyone encountered a similar issue? Could this be related to database migration, Azure SQL performance, or App Service configuration?
Hi friend - welcome!
It’s rather difficult to surmise anything with the above info.
Some logs with actual error messaging would go a long way for us to start to help here.
Also if possible, do the migration to the latest version (17.7.1 currently). This not only gives you patches for known vulnerabilities, but also makes sure that you are not missing any fixes that fix this issue.
I would always recommend you run migrations like this offline locally, as databases can be slow to run migration scripts on hosting, especially if you are using Azure SQL which will throttle the database if you exceed your DTU quota.
Also, I would recommend you first upgrade to the latest v13 (13.16.2) before migrating and ensure you have migrated your data away from obsolete data types such as Nested Content and Grid Layout before proceeding to v17.
As @Luuk says, you should also go to the latest version of v17 if possible as this will contain both migration and security fixes.
We migrated directly from Umbraco 13 to 17 and manually migrated the database locally without using the Umbraco installation wizard. The migration completed successfully, and the backoffice loaded with the migrated content without any issues.
However, when we deployed the same Umbraco 17 code and ran it against the Umbraco 13 database in Azure, we encountered an internal server error during the database upgrade process. The backoffice eventually loads, but it remains in a loading state until we refresh the page.
We also considered whether this could be related to Azure SQL DTU throttling. To rule this out, we upgraded the database tier to Premium P11, but the same issue persisted.
Regarding your suggestion to upgrade to Umbraco 13.16.2 before migrating to v17, I understand the recommendation. However, since the direct migration worked successfully in our local environment using the same approach, I am trying to understand why the issue occurs only in Azure.
When we migrated the database locally and deployed it to Azure, the only other issue we encountered was that the site displayed a maintenance page after adding the culture and hostname. This was resolved by upgrading Umbraco to version 17.7.1, as @Luuk suggested.
At this point, the only remaining issue is the internal server error during the database upgrade in Azure. Since upgrading the database tier to Premium P11 did not resolve it, I would appreciate any suggestions on what else we could investigate.
Without knowing what error you had during the migration it will be difficult to say, but as I said, I would recommend you run migrations locally. You may have hit a timeout, and it may have left something in a partially migrated state.
Are you able to re-do the migration locally and re-upload, or has that opportunity passed?