Getting HTTP Error 500.30 after successful publishing to Azure
I have created my first Umbraco 9 VS Project.
When publishing the application to Azure everything seems to be successful until I run the page then I get:
HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
I've made a workaround about this and just be careful on using it because this may only applied to my particular case.
I've added a new task into the yaml file to copy the entire media folder into the package to deploy. If you check this Umbraco Deploy doc, I've just took the step #5 (adapting the variable values to fit my data).
Check you are publishing using the correct runtime for your hosting environment? If you are targeting the wrong runtime, you won't even get a log file generated
Check which media provider you are using?
If you are using the file system provider, make sure the folder exists
If you are using Azure, make sure a connection string is present
I've just run into this exact issue - deploying Umbraco 10 from Azure DevOps to an Azure App Service - so would love to get some help here.
Check you are publishing using the correct runtime for your hosting environment? If you are targeting the wrong runtime, you won't even get a log file generated
Where can this be checked?
[UPDATE 1]
Having looked through the artifact created at the Build step there's no folder called 'media'
[UPDATE 2]
Have confirmed that both local Umbraco project & Azure App Service are targeting .NET 6.0
[UPDATE 3]
For transparency here are the associated pipelines and the wwwRoot contents from the Azure App Service, showing that files have deployed, but it's just not enough:
I've managed to get an ASP.NET Core application deployed just fine, though copying that pipeline exactly doesn't work, so it's an Umbraco-specific setting/problem
[UPDATE 5]
Confirmed that it IS an issue with the missing /media/ folder. Used Azure App Editor, then ran this command (the project is UmbracoBasic01):
\> dotnet UmbracoBasic01.dll
Unhandled exception. System.IO.DirectoryNotFoundException: C:\home\site\wwwroot\wwwroot\media\
Huge thanks to Rick Butterfield for that direction
[UPDATE 6]
So I'm having a morning where everything just works, so here is the pipeline I've made which seems to not trigger the /media issue. The important part appears to be making sure the pipeline goes through Build->Publish->Deploy phases, which I'm unsure I fully acknowledged before:
I've run into this a couple of times with Umb v10 on Azure web apps. It is usually a missing file but the logs can be a little misleading - so be sure to go line by line looking for mentions of missing files/folders. Even though my file was in the project I needed to re-add it to force it in there.
Getting HTTP Error 500.30 after successful publishing to Azure
I have created my first Umbraco 9 VS Project.
When publishing the application to Azure everything seems to be successful until I run the page then I get:
HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup
Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect
Hello Morten
Did you find for this issue a solution? I have the exact same Error with Umbraco 9.
Kind regards Edvin
Have you checked the logs on the App environment? You can easily see them using the Advanced Tools.
Also easily reachable by changing your URL of the app from
https://examplesite.azurewebsites.net
tohttps://examplesite.scm.azurewebsites.net
Any news on this? I have the same error publishing on internal servers. Logs are empty.
Thanks in advance!
Found the issue, the
media
folder is missing. I'll work on solving that and will confirm if that is only the issue.It would be great if you could find a solution. And please let me know about it
I've made a workaround about this and just be careful on using it because this may only applied to my particular case.
I've added a new task into the yaml file to copy the entire
media
folder into the package to deploy. If you check this Umbraco Deploy doc, I've just took the step #5 (adapting the variable values to fit my data).Example:
This solution may not be the ideal but it is fine for now in my case and all is working as expected.
@Edvin, I'm sorry the delay on this response.
In case it helps someone else:
I've just run into this exact issue - deploying Umbraco 10 from Azure DevOps to an Azure App Service - so would love to get some help here.
Where can this be checked?
[UPDATE 1] Having looked through the artifact created at the Build step there's no folder called 'media'
[UPDATE 2] Have confirmed that both local Umbraco project & Azure App Service are targeting .NET 6.0
[UPDATE 3]
For transparency here are the associated pipelines and the wwwRoot contents from the Azure App Service, showing that files have deployed, but it's just not enough:
DeploymentYAML
ReleaseYAML
Contents of wwwRoot
[UPDATE 4]
I've managed to get an ASP.NET Core application deployed just fine, though copying that pipeline exactly doesn't work, so it's an Umbraco-specific setting/problem
[UPDATE 5]
Confirmed that it IS an issue with the missing /media/ folder. Used Azure App Editor, then ran this command (the project is UmbracoBasic01):
\> dotnet UmbracoBasic01.dll Unhandled exception. System.IO.DirectoryNotFoundException: C:\home\site\wwwroot\wwwroot\media\
Huge thanks to Rick Butterfield for that direction[UPDATE 6]
So I'm having a morning where everything just works, so here is the pipeline I've made which seems to not trigger the /media issue. The important part appears to be making sure the pipeline goes through Build->Publish->Deploy phases, which I'm unsure I fully acknowledged before:
I've run into this a couple of times with Umb v10 on Azure web apps. It is usually a missing file but the logs can be a little misleading - so be sure to go line by line looking for mentions of missing files/folders. Even though my file was in the project I needed to re-add it to force it in there.
is working on a reply...