Azure remove error

Dear Sir/

madam,

please see error and correct it.

Awaiting your reply,

Best Regards,

Fabrice

go to github link :https://github.com/Thibaut501/pos and see

How to correct the

error.

Awaiting in reply,

Fabrice

Hi @Thibaut Fabrice

Thanks for reaching us regarding your issue as per provided details from deeper investigation we have found the reason behind the issue: your ASP.NET Core application is failing to start (resulting in the HTTP Error 500.30) because of several unhandled exceptions that occur during the initialization process. The diagnostic logs clearly capture these in EventLog.xml, specifically:

• SQL connection failures when attempting to open the database (10 occurrences – typically caused by firewall blocks, incorrect connection strings, or transient issues).
• Assembly loading problems during hosting startup (5 occurrences – often due to missing dependencies or runtime targeting mismatches).
• File system permission errors when trying to create directories (3 occurrences – Azure App Service has a sandboxed file system, and certain paths are restricted, especially on the Free tier).

These startup crashes are happening repeatedly due to frequent site restarts and the resource limitations of the Free SKU App Service Plan, which also explain the worker allocation failures and occasional 503 errors you're seeing.

Could you please follow the below steps to fix the issue

1. Upgrade the App Service Plan to at least Basic (B1) tier. The Free tier is great for testing but has shared resources and quotas that can cause instability in production scenarios. Upgrading will provide dedicated VM resources and eliminate many of the allocation/restart issues. Azure App Service plans overview: https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans
2. Resolve the SQL connection issues. Check your connection string in the App Service Configuration, and in your Azure SQL Database, go to Networking > Firewalls and virtual networks > set "Allow Azure services and resources to access this server" to Yes. Adding retry logic in your code can also help with any transient errors. Connect an App Service app to Azure SQL Database: https://learn.microsoft.com/en-us/azure/app-service/tutorial-dotnetcore-sqldb-app
3. Fix the file system errors. Avoid writing to restricted paths—use the persistent storage under /home/site/wwwroot or, better yet, switch backup operations to Azure Blob Storage to bypass local file system limitations entirely. App Service sandbox and OS functionality: https://learn.microsoft.com/en-us/azure/app-service/operating-system-functionality
4. Address assembly loading. Ensure you're publishing as self-contained for the correct runtime (e.g., win-x64) and clear your local NuGet cache before redeploying. Troubleshoot ASP.NET Core on Azure App Service and IIS: https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-9.0

After making these changes, redeploy and keep an eye on the Log Stream in the portal to confirm a clean startup. Most customers see the 500.30 disappear once these root causes are fixed.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.