Error 500.35 - ASP.NET Core does not support multiple apps in the same app pool Common solutions to this issue: Select a different app pool to host this app. 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 For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. I have two subsites on my main site. One or the other works, depending on which was published last. How do I go about making sure they are in different app pools. Where do I find the settings to change?
When you’re on shared hosting, you typically cannot create or assign separate IIS application pools. That’s why you’re seeing: HTTP Error 500.35 – ASP.NET Core does not support multiple apps in the same app pool By default, ASP.NET Core runs InProcess, and IIS does not allow multiple Core apps in the same pool in that mode. Since you can’t split them into different app pools, the correct solution is to switch both applications to: hostingModel="OutOfProcess" This allows each app to run in its own Kestrel process behind IIS, even if they share the same app pool. Make sure all of your application use hostingModel="OutOfProcess" in their web.config files
