Cannot access web application after

Question

Cannot access web application after

Andrew Sabin 40

Hello Microsoft Azure Support Team,

I have been trying to get a ASP.net and Blazor web application running through Microsoft Azure. When I have deployed it through continuous integration through a GitHub repository the build and deploy jobs have both shown up as successful. The only warning I have gotten from my build job through GitHub has been through the dotnet publish:

Warning: /usr/share/dotnet/sdk/10.0.101/Current/SolutionFile/ImportAfter/Microsoft.NET.Sdk.Solution.targets(36,5): warning NETSDK1194: The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds. [/home/runner/work/*******/*******/******.slnx]

However, when I have tried to access the application through its default domain URL I have been getting an Application error, where when I click on the diagnostic resources link it has given me a Resource not found error, where after doing self-diagnostics, all tests were successful and gave me 200 status codes.

The only other clue as to why my application is not running is that in the Instances section of the Web Application has been giving me a ContainerTimeout error with the message: Container did not start within expected time limit of 230s. Please inspect your container logs for more details.

I'm currently hosting the web application through a Basic(B1) SKU and size tier in a Linux Operating System environment. The dotnet stack that my applications are running on is .Net 8.

I am currently subscribed to the Developer plan for Azure Support services, so I'm available if someone from the team needs to contact me.

Thank you very much for any help you can give me with solving this issue.

Aditya N 2,990 Reputation points Microsoft External Staff Moderator

2026-01-06T07:40:38.6933333+00:00

Hello @Andrew Sabin

Thank you for reaching out Microsoft Q&A. We could see from your query that the container app did not start within expected time.

Could you please let us know if you had a chance to look into container logs to check whether any dependency conflict is happening.

The warning message indicates all outputs are copied into same directory which might create dependency conflict.

Andrew Sabin 40

Hello Aditya,

When looking at the logs it looks like the issue is coming from the entity framework core:

2026-01-06T21:35:24.7152655Z Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.EntityFrameworkCore, Version=9.0.8.0, Culture=neutral, PublicKeyToken=********'. The system cannot find the file specified.
2026-01-06T21:35:24.7152976Z
2026-01-06T21:35:24.7253441Z File name: 'Microsoft.EntityFrameworkCore, Version=9.0.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'
2026-01-06T21:35:27.583712Z /opt/startup/startup.sh: line 20:  2086 Aborted                 (core dumped) dotnet "*****.dll"

The .dll file's name is the same as the project file that I am using for the API/Server.

Would the issue be coming from the version of Microsoft.EnityFrameworkCore or just that the file is missing?

Answer accepted by question author

Aditya N 2,990 Microsoft External Staff Moderator

Hello @Andrew Sabin

Thank you for providing the resolution and helping the community, resolving the compatibility issues caused by version mismatches.Microsoft.EntityFrameworkCore, Version=9.0.8.0 - here it is trying to load the version 9.0.8.0 however .net stack was 8.0 as mentioned in query thus throwing file not found error. Upgrading should have resolved the issue. Thanks again for sharing.

0 comments

2 additional answers

Your answer

Aditya N 2,990 Reputation points Microsoft External Staff Moderator

2026-01-06T07:40:38.6933333+00:00

Hello @Andrew Sabin

Thank you for reaching out Microsoft Q&A. We could see from your query that the container app did not start within expected time.

Could you please let us know if you had a chance to look into container logs to check whether any dependency conflict is happening.

The warning message indicates all outputs are copied into same directory which might create dependency conflict.
Andrew Sabin 40 Reputation points

2026-01-06T21:43:08.27+00:00

Hello Aditya,

When looking at the logs it looks like the issue is coming from the entity framework core:

2026-01-06T21:35:24.7152655Z Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.EntityFrameworkCore, Version=9.0.8.0, Culture=neutral, PublicKeyToken=********'. The system cannot find the file specified. 2026-01-06T21:35:24.7152976Z 2026-01-06T21:35:24.7253441Z File name: 'Microsoft.EntityFrameworkCore, Version=9.0.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' 2026-01-06T21:35:27.583712Z /opt/startup/startup.sh: line 20: 2086 Aborted (core dumped) dotnet "*****.dll"

The .dll file's name is the same as the project file that I am using for the API/Server.

Would the issue be coming from the version of Microsoft.EnityFrameworkCore or just that the file is missing?

Answer 1

Andrew Sabin 40

I was able to solve this issue by upgrading the project's .NET Version from 8 to 10 and change the stack to .NET 10.

0 comments

Answer 2

It seems like you are encountering a few issues with your ASP.NET and Blazor web application deployed on Azure. Here are some steps and considerations that might help you troubleshoot the problem:

Container Timeout Error: The error message indicating that the container did not start within the expected time limit suggests that there may be an issue with the application starting up. You should inspect the container logs to identify any specific errors that occurred during the startup process. You can access these logs through the Azure portal under the "Log Stream" or "Container Logs" section of your App Service.
Application Error: The application error you are experiencing could be related to the application not being able to start correctly due to configuration issues or missing dependencies. Ensure that all necessary configurations are set correctly in your appsettings.json and that any required services are properly configured in Azure.
Warning from Build Job: The warning regarding the --output option not being supported when building a solution may not directly cause the application to fail, but it's worth addressing. Ensure that your build pipeline is correctly set up to handle output paths for individual projects rather than the solution as a whole.
Check .NET Hosting Bundle: Since you are using .NET 8, ensure that the .NET Hosting Bundle is correctly installed on your Azure environment. If it’s missing or corrupted, it could lead to startup failures.
Scaling Considerations: Since you are on a Basic (B1) SKU, consider whether this tier provides sufficient resources for your application. If your application is resource-intensive, you may want to scale up to a higher tier.
Self-Diagnostics: Since your self-diagnostics returned successful results with 200 status codes, it indicates that the Azure infrastructure is functioning correctly. However, the application itself may still have issues that need to be resolved.

If you continue to face issues, consider reaching out to Azure support for more personalized assistance, especially since you are subscribed to the Developer plan.

References:

Share via

Cannot access web application after

2 additional answers

Your answer