Troubleshooting .NET 10 Application Errors Print

Common HTTP Error Codes

HTTP 500.30 - ASP.NET Core App Failed to Start

Cause: Application crashed during startup

Solutions:

• Check that Application Startup File is correct in Plesk
• Verify all required files were uploaded
• Check application logs in Plesk
• Ensure appsettings.json is valid JSON
• Verify database connection strings are correct

HTTP 500.31 - Failed to Load Runtime

Cause: .NET runtime not found or version mismatch

Solutions:

• Ensure your app targets .NET 10
• For framework-dependent deployments, contact support to verify .NET 10 is installed
• Consider self-contained deployment if runtime issues persist

HTTP 500.32 - Failed to Load aspnetcore.dll

Cause: ASP.NET Core Module issue

Solutions:

• Contact support - this is typically a server-side issue

HTTP 502.5 - Process Failure

Cause: Application process crashed

Solutions:

• Check application logs for exceptions
• Verify startup code doesnt throw exceptions
• Check for missing dependencies

Enabling Detailed Error Logging

To get more detailed error information, temporarily enable stdout logging:

1. Edit your web.config file
2. Find the <aspNetCore> element
3. Set stdoutLogEnabled="true"
4. Set stdoutLogFile=".logsstdout"
5. Create a logs folder in your app root
6. Reproduce the error and check the log files

Example web.config

<aspNetCore processPath="dotnet" 
            arguments=".MyApp.dll" 
            stdoutLogEnabled="true" 
            stdoutLogFile=".logsstdout" 
            hostingModel="inprocess" />

Important: Disable stdout logging in production after troubleshooting!

Common Issues and Fixes

Application Shows Old Version After Update

• Restart the application in Plesk .NET Core settings
• Clear browser cache
• Verify new files were uploaded correctly

Static Files Not Loading (CSS, JS, Images)

• Verify Document Root is set correctly
• Check that UseStaticFiles() is in your Program.cs
• Ensure wwwroot folder was uploaded

Database Connection Fails

• Verify connection string in appsettings.Production.json
• Check database server name/IP is correct
• Verify database credentials
• Ensure firewall allows connection

Application Times Out

• Check for long-running startup code
• Verify external service connections (APIs, databases)
• Review application logs for bottlenecks

Getting Help

If you continue to experience issues after trying these solutions, please contact our support team with:

• Your domain name
• The exact error message
• Steps to reproduce the issue
• Any relevant log entries