That should at least get your application working.īut, it might be that you've changed the identity of the application pool in IIS. If the group is not there, you can add the Users group to the folder that's running your ASP.NET Core application in IIS. However, what if that group is not there? Or it doesn't resolve the issue? In Windows 10, give IIS_IUSRS Full Control to your ASP.NET Core Application in IIS In Windows 10, you need to give full access to the IIS_IUSRS group in the path where you are hosting your ASP.NET Core application in IIS. This error is because IIS does not have the correct permissions to render your ASP.NET Core application. The requested page cannot be accessed because the related configuration data for the page is invalid.Ĭonfig Error: Cannot read configuration file due to insufficient permissions 500.19 Error when Running an ASP.NET Core Application in IIS And then IIS throws an error that reads as follows: HTTP Error 500.19 - Internal Server Error You've set up a website in IIS pointing to your published folder. So you've published your ASP.NET Core application. So, that's explore the reasons why this might be the case and come up with some rememdies. They were saying they still couldn't get their ASP.NET Core application to work in IIS, despite following the recommendations in that article.
#WHY IS MY VUDU TO GO APP NOT WORKING HOW TO#
Now the reason why I'm writing this article is because I've had a few people get in contact with me as a result of my article " How to Publish an ASP.NET Core & React SPA to IIS". We are going to explore four potential reasons why your ASP.NET Core Application is not working in IIS.