Last post Jan 24, 2021 12:14 PM by mywatermelon
Jan 24, 2021 12:14 PM|mywatermelon|LINK
Recently I add a large feature to my asp.net core 5 websites.
All runs well on local without any error.
However, after I published it to the server, my website(for example:www.abc.com) reports this error:
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
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more information visit:
I am afraid I can not publish my code here for it is an enterprise project.
Soon I found out the problem. If I uncheck the option of Enable ReadyToRun compilation, all runs well without any error on the server.
It seems it is the problem of the ReadyToRun.
I tried another way to find the problem. I published my website with ReadyToRun to a subdomain website(for example test.abc.com) and about to debug it with Visual Studio Remote Debugger.
But the subdomain website does not report any error and runs well now!
I want to find out the problem while I don't know what should I do next.
Could you please give me a suggestion? Thank you.