Asp net ошибка 403

I have downloaded the MVC Music Store ASP.NET application at location C:UsersDEVESHDesktopProjectsMvcMusicStore-v3.0MvcMusicStore-CompletedMvcMusicStore
and added the website on IIS at the same location. I have also given permission to IIS_IUSRS, but when I run localhost I am getting the error:

HTTP Error 403.14 — Forbidden The Web server is configured to not list the contents of this directory.

I have googled it, but have not found a fix. What I am doing wrong?

In my case when I browsed to
site5.com
I got the following error.

HTTP Error 403.14 — Forbidden
The Web server is configured to not list the contents of this directory.

Most likely causes:
A default document is not configured for the requested URL, and directory browsing is not enabled on the server.

And then when I browsed to

site5.com/home/index

I was met with

HTTP Error 404.0 — Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Most likely causes:
The directory or file specified does not exist on the Web server.
The URL contains a typographical error.
A custom filter or module, such as URLScan, restricts access to the file.

All that I did is installed the feature in IIS ASP.NET 4.8 as shown below.

answered Feb 22, 2020 at 10:09

I have encountered similar myself before for 2 reasons;
1. MVC is not installed.
2. The url routing module is not registered (this varies by machine in my workplace for a reason I cannot fully explain — it is not always registered at a system level ), try registering it in the application web.config:

<system.web> 
      ... 
      <httpModules> 
         ... 
         <add name="UrlRoutingModule" type="System.Web.Routing.UrlRoutingModule, System.Web.Routing, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> 
      </httpModules>
   </system.web>

Edit: I forgot to add the location for iis 7+:

<system.webServer> 

      <modules> 
         ... 
         <add name="UrlRoutingModule" type="System.Web.Routing.UrlRoutingModule, System.Web.Routing, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> 
      </modules>
</system.webServer>

answered Jul 13, 2013 at 15:37

This error can happen when, in IIS Manager, the ASP.NET MVC site is pointed to the wrong directory.

In my case, I inadvertently had the site pointed to the solution directory instead of the child project directory. That is, I had the site’s Physical path set to

C:devMySolution

instead of

C:devMySolutionMyProject.

Specific steps to fix this:

1. Open IIS Manager (Start > Run > inetmgr);
2. In IIS Manager, in the left pane, expand Sites;
3. Under Sites, left-click the ASP.NET MVC website;
4. In the right pane, click Basic Settings…;
5. In the Edit Site dialog, change the Physical path to the project directory.
6. Click OK.

answered Jul 10, 2017 at 15:06

This error occurs when the application cannot startup.
So the cause can be anything that prevents your application to start.

• Wrong connection string
• Wrong IIS directory permissions
• An exception thrown in your Application_Start() function
• IOC Container initialization error
• IIS ASP.NET registration errors
• Missing DLL in your bin folder
• etc…

answered Dec 15, 2016 at 16:08

I’ve just had the same problem, but my fix was that the Routing was not configured in the Global.asax.cs file. I’m using Bootstrapper and Castle Windsor, so to resolve this problem I added the following code to Global.asax.cs:

public class MvcApplication : System.Web.HttpApplication
    {
        protected void Application_Start()
        {
            Bootstrapper.IncludingOnly.Assembly(Assembly.GetAssembly(typeof(WindsorRegistration)))
                .With
                .Windsor()
                .With
                .StartupTasks()
                .Start();
        }
    }

Obviously if you are using the basic MVC then you will need to reference the RouteConfig file in the AppStart folder instead:

public class MvcApplication : System.Web.HttpApplication
    {
        protected void Application_Start()
        {
            AreaRegistration.RegisterAllAreas();
            FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
            RouteConfig.RegisterRoutes(RouteTable.Routes);
            BundleConfig.RegisterBundles(BundleTable.Bundles);
        }
    }

answered Oct 21, 2015 at 13:47

In my case, i had multiple projects but i had not defined the starting Project.
So this error was generating.
After defining the startUp project solved the issue.

answered Jan 4, 2017 at 15:10

If project is a ASP.net MVC project it would be about routing.
In my case I changed default routing values:

routes.MapRoute(
           "Default",                                              
           "{controller}/{action}/{id}",                           
           new { controller = "Home", action = "Index", id = "" }  
       );

I changed my code accidentally to:

routes.MapRoute(
               "Default",                                              
               "{controller}/{action}/{JobID}",                           
               new { controller = "Home", action = "Index", id = "" }  
           );

Thats I only changed «id» to «JobId» and default route can not be find.

answered May 9, 2016 at 14:55

answered May 12, 2017 at 17:08

answered Feb 20, 2018 at 22:42

answered Jan 5, 2018 at 21:06

answered Jan 26, 2018 at 0:33

In case anyone comes across this for a project other than MVC:

My project was a WCF project, which runs off .svc files—no default document. As a result I got a 403.14 error at myhost.com/ but as soon as I added a baseAddress path from my web.config file (ex. myhost.com/mybaseaddresspath.svc I got a webpage.

answered Feb 5, 2019 at 17:38

My colleagues made a URL Rewrite rule, which reduced all URLs to a StaticFileHandler; mapped to a file path at the root of my Application physical folder.

(i.e. an over-aggressive URL rewrite means that my Controllers/Actions were not working)

Check your applications’ URL Rewrite rules to confirm they do what you expect.

answered May 9, 2019 at 23:44

I faced the same issue while developing Business Central application.
Open Business Central Application and Edit Web Client Base URL
under Client Services.
You can enter http://localhost:8080/YourWebServerInstance/

answered Sep 19, 2022 at 19:03

I faced similar issue. My controller name was documents. It manages uploaded documents. It was working fine and started showing this error after completion of code. The mistake I did is — Created a folder ‘Documents’ to save the uploaded files. So controller name and folder name were same — which made the issue.

I’m developing an ASP MVC web project. Now I have a requirement which forces me to deploy to an IIS7 inmiddle of development (to check some features). I’m getting the above mentioned error message whenever I try to type the URL of the web site. (Note: development machine: Vista Home Premium, IIS7)

What I have done until now:

Edited the HOSTS file (C:WINDOWSsystem32driversetchosts).

Put two domains in it (127.0.0.1 domain1.com & 127.0.0.1 domain2.com).

Created a folder c:websitesdirOfApplication and deployed from within Visual Studio 8 to this folder.

In IIS7 created a new site with host name domain1.com and application folder the above.

Typing the address domain1.com in Web browser results in the above error (HTTP Error 403.14 — Forbidden — The Web server is configured to not list the contents of this directory.)

I think I’m missing something but don’t know what! Tryed to deploy the files System.Web.Mvc, System.Web.Abstraction & System.Web.Routing wit the same outcome. Whenever I try to hit F5 and run the application, it works fine!

I too ran into this error. All the configuration and permissions were correct.
But I forgot to copy Global.asax to the server, and that’s what gave the 403 error.

I had the same issue. This Microsoft support article fixed it for me.
https://support.microsoft.com/en-us/help/2023146/mvc-2-and-asp.net-4-web-forms-applications-that-use-url-routing-might-return-http-404-errors-when-they-attempt-to-process-extensionless-urls-on-iis-7-and-iis-7.5

In the «Turn Windows Features On or Off» dialog box of the Windows Control Panel «Programs and Features» application, perform the following steps:

1. Navigate to the following node: Internet Information Services —> World Wide Web Services —> Common HTTP Features
2. Make sure that the «HTTP Error Redirection» option is selected.

-or-

1. Navigate to the following node: Internet Information Services —> World Wide Web Services —> Performance Features
2. Make sure that the «Static Content Compression» option is selected. After either option has been selected, click «OK» to save changes.

Re-enabling either the HTTP Error Redirection module or the Static Content Compression module ensures that ASP.NET and IIS correctly synchronize HTTP pipeline events. This enables the URL routing module to process extensionsless URLs.

answered Mar 28, 2011 at 12:49

Please also check, if you are running x64, that you have enabled 32-bit applications in the app pool settings

answered Jul 28, 2011 at 21:47

answered Aug 6, 2015 at 20:48

I read through every answer here looking for something that worked before I realized that I’m using IIS 10 (on Windows 10 version 2004) and this question is about IIS 7 and almost a decade old.

With that said, run this from an elevated command prompt:

dism /online /enable-feature /all /featurename:IIS-ASPNET45

The /all will automatically enable the dependent parent features: IIS-ISAPIFilter, IIS-ISAPIExtensions, and IIS-NetFxExtensibility45.

After this, you’ll notice two new (in my environment at least) application pool names mentioned .NET v4.5. ASP.NET web apps that were previously using the DefaultAppPool will just work.

answered Dec 14, 2020 at 22:14

If the top answers don’t work, look for a config named PrecompiledApp.config in the hosting directory and delete it if it exists. This file prevents IISExpress and LocalIIS to work properly. (And I think that’s a bug) The content of the file in my case was:

<precompiledApp version="2" updatable="true"/>

And I’m 100% positive that was the problem with my case since I tried everything in 2 hours and tested lots of times with this config.

One more thing: You cannot use aspnet_regiis in newer versions of Windows and IIS so try

dism /online /enable-feature /featurename:IIS-ASPNET45 /all

answered Jan 14, 2017 at 11:37

Control Panel > turn windows features on or off > Web Server > Application Development

Check ASP.NET

answered Feb 6, 2020 at 22:50

answered Jan 22, 2013 at 12:44

answered Dec 7, 2016 at 13:08

I tried everything here; nothing worked. Problem was in my Web.config file, somehow dependent assembly binding got changed from minimum 1 to minimum 0.

<!-- was -->
<runtime>
    <assemblyBinding>
        <dependentAssembly>
            <assemblyIdentity name="System.Web.Mvc" />
                <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />


<!-- should have been -->
                <bindingRedirect oldVersion="1.0.0.0-5.2.3.0" newVersion="5.2.3.0" />

answered Apr 6, 2017 at 8:11

I have also encountered this same error, despite all the provided solutions for the following reasons:

• Missing DLLs
• Database connection string points to an inaccessible server.

answered Dec 11, 2011 at 3:55

answered Sep 3, 2012 at 16:49

answered Jan 28, 2013 at 14:00

answered Jul 9, 2015 at 13:34

Also one more things can be possible

install .net framework 4.0 manually

This solution is for IIS7 on window 7

open cmd with administration previleges

go to directory «C:WindowsMicrosoft.NETFrameworkv4.0.30319»

type aspnet_regiis.exe -i

got to your inet manager by typing in run command «inetmgr»

refresh your IIS7

reload the site.

answered Jul 19, 2016 at 8:07

I know you had this problem in an internal host, but I had experienced such an issue before in an external host and in my case it had it’s own resolution, maybe it could save somebody’s time:

In fact my website was STOPPED by some reason which currently I’m not aware of, to check it out if you have the same problem, in WebsitePanel main page go to Web -> Websites then select the domain name of your website from the list, after that in the right side of the page just opened, check if you see the word STARTED, else if you see the word STOPPED, make it get started again. That’s all.

answered Jul 22, 2017 at 12:53

I know this is an old topic, but you can also get this error (when you are debugging) if you have a folder named the same as a route in a controller.

For instance, if you have a UserController, with a route called /User and you ALSO have a folder in your solution called «User» then IISExpress will try to browse the folder instead of showing your view.

answered May 30, 2018 at 22:55

After trying every solution suggested here, I found yet another possible solution: URLScan

The IIS had WebDAV disabled, even in the web.config of my application, WebDAV’s handler and module was removed. PUTs still returned a 403 — Forbidden without any log entries in the IIS logs. (GET / POST worked fine).

Turns out the IIS had an active ISAPI Filter (the URLScan) enabled which prevented all PUTs. After removing URLScan, it worked for me.

answered Feb 7, 2019 at 13:53

My situation was completely different than any of these and the 403:Forbidden error message was a little bit of a red herring.

If your Application_Start() function in the Global.asax module tries to access the web.config and an entry that it’s referencing isn’t there, IIS chokes and (for some reason) throws the 403:Forbidden error message.

Double-check that you aren’t missing an entry in the web.config file that’s attempting to be accessed in your Global.asax module.

answered Sep 16, 2019 at 18:03

In case you’re like me and have an application using NHibernate and the above answers have not resolved your issue.

You should look at the connection string in your application; possibly in the webconfig file to ensure it is correct.

answered Sep 24, 2019 at 18:33

I have been using Identity Impersonate:

<system.web>
    <identity impersonate="true" userName="domainusername" password="password"/>
</system.Web>

When pushing up to the server you have to give the username access to the Temporary ASP.NET Files folder so it can read/write/execute properly:

C:WindowsMicrosoft.NET"frameworkversion""aspversion"Temporary ASP.NET Files

Obviously replace «frameworkversion» and «aspversion» with the versions you are using.

answered May 13, 2014 at 9:40

Step 1: Select the Site For which the HTTP Error is produced in IIS and then click on Directory Browsing as shown in the image below:

Step 2: In the Directory Browsing Window in IIS click on Enable in Actions on the right side as shown in the diagram below:

Now Directory Browsing is enabled for your asp.net website, just restart the web application in IIS and Browse the site in your browser and see the result.

answered Jul 30, 2014 at 21:05

I’m developing an ASP MVC web project. Now I have a requirement which forces me to deploy to an IIS7 inmiddle of development (to check some features). I’m getting the above mentioned error message whenever I try to type the URL of the web site. (Note: development machine: Vista Home Premium, IIS7)

What I have done until now:

Edited the HOSTS file (C:WINDOWSsystem32driversetchosts).

Put two domains in it (127.0.0.1 domain1.com & 127.0.0.1 domain2.com).

Created a folder c:websitesdirOfApplication and deployed from within Visual Studio 8 to this folder.

In IIS7 created a new site with host name domain1.com and application folder the above.

Typing the address domain1.com in Web browser results in the above error (HTTP Error 403.14 — Forbidden — The Web server is configured to not list the contents of this directory.)

I think I’m missing something but don’t know what! Tryed to deploy the files System.Web.Mvc, System.Web.Abstraction & System.Web.Routing wit the same outcome. Whenever I try to hit F5 and run the application, it works fine!

I too ran into this error. All the configuration and permissions were correct.
But I forgot to copy Global.asax to the server, and that’s what gave the 403 error.

I had the same issue. This Microsoft support article fixed it for me.
https://support.microsoft.com/en-us/help/2023146/mvc-2-and-asp.net-4-web-forms-applications-that-use-url-routing-might-return-http-404-errors-when-they-attempt-to-process-extensionless-urls-on-iis-7-and-iis-7.5

In the «Turn Windows Features On or Off» dialog box of the Windows Control Panel «Programs and Features» application, perform the following steps:

1. Navigate to the following node: Internet Information Services —> World Wide Web Services —> Common HTTP Features
2. Make sure that the «HTTP Error Redirection» option is selected.

-or-

1. Navigate to the following node: Internet Information Services —> World Wide Web Services —> Performance Features
2. Make sure that the «Static Content Compression» option is selected. After either option has been selected, click «OK» to save changes.

Re-enabling either the HTTP Error Redirection module or the Static Content Compression module ensures that ASP.NET and IIS correctly synchronize HTTP pipeline events. This enables the URL routing module to process extensionsless URLs.

answered Mar 28, 2011 at 12:49

Please also check, if you are running x64, that you have enabled 32-bit applications in the app pool settings

answered Jul 28, 2011 at 21:47

answered Aug 6, 2015 at 20:48

I read through every answer here looking for something that worked before I realized that I’m using IIS 10 (on Windows 10 version 2004) and this question is about IIS 7 and almost a decade old.

With that said, run this from an elevated command prompt:

dism /online /enable-feature /all /featurename:IIS-ASPNET45

The /all will automatically enable the dependent parent features: IIS-ISAPIFilter, IIS-ISAPIExtensions, and IIS-NetFxExtensibility45.

After this, you’ll notice two new (in my environment at least) application pool names mentioned .NET v4.5. ASP.NET web apps that were previously using the DefaultAppPool will just work.

answered Dec 14, 2020 at 22:14

If the top answers don’t work, look for a config named PrecompiledApp.config in the hosting directory and delete it if it exists. This file prevents IISExpress and LocalIIS to work properly. (And I think that’s a bug) The content of the file in my case was:

<precompiledApp version="2" updatable="true"/>

And I’m 100% positive that was the problem with my case since I tried everything in 2 hours and tested lots of times with this config.

One more thing: You cannot use aspnet_regiis in newer versions of Windows and IIS so try

dism /online /enable-feature /featurename:IIS-ASPNET45 /all

answered Jan 14, 2017 at 11:37

Control Panel > turn windows features on or off > Web Server > Application Development

Check ASP.NET

answered Feb 6, 2020 at 22:50

answered Jan 22, 2013 at 12:44

answered Dec 7, 2016 at 13:08

I tried everything here; nothing worked. Problem was in my Web.config file, somehow dependent assembly binding got changed from minimum 1 to minimum 0.

<!-- was -->
<runtime>
    <assemblyBinding>
        <dependentAssembly>
            <assemblyIdentity name="System.Web.Mvc" />
                <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />


<!-- should have been -->
                <bindingRedirect oldVersion="1.0.0.0-5.2.3.0" newVersion="5.2.3.0" />

answered Apr 6, 2017 at 8:11

I have also encountered this same error, despite all the provided solutions for the following reasons:

• Missing DLLs
• Database connection string points to an inaccessible server.

answered Dec 11, 2011 at 3:55

answered Sep 3, 2012 at 16:49

answered Jan 28, 2013 at 14:00

answered Jul 9, 2015 at 13:34

Also one more things can be possible

install .net framework 4.0 manually

This solution is for IIS7 on window 7

open cmd with administration previleges

go to directory «C:WindowsMicrosoft.NETFrameworkv4.0.30319»

type aspnet_regiis.exe -i

got to your inet manager by typing in run command «inetmgr»

refresh your IIS7

reload the site.

answered Jul 19, 2016 at 8:07

I know you had this problem in an internal host, but I had experienced such an issue before in an external host and in my case it had it’s own resolution, maybe it could save somebody’s time:

In fact my website was STOPPED by some reason which currently I’m not aware of, to check it out if you have the same problem, in WebsitePanel main page go to Web -> Websites then select the domain name of your website from the list, after that in the right side of the page just opened, check if you see the word STARTED, else if you see the word STOPPED, make it get started again. That’s all.

answered Jul 22, 2017 at 12:53

I know this is an old topic, but you can also get this error (when you are debugging) if you have a folder named the same as a route in a controller.

For instance, if you have a UserController, with a route called /User and you ALSO have a folder in your solution called «User» then IISExpress will try to browse the folder instead of showing your view.

answered May 30, 2018 at 22:55

After trying every solution suggested here, I found yet another possible solution: URLScan

The IIS had WebDAV disabled, even in the web.config of my application, WebDAV’s handler and module was removed. PUTs still returned a 403 — Forbidden without any log entries in the IIS logs. (GET / POST worked fine).

Turns out the IIS had an active ISAPI Filter (the URLScan) enabled which prevented all PUTs. After removing URLScan, it worked for me.

answered Feb 7, 2019 at 13:53

My situation was completely different than any of these and the 403:Forbidden error message was a little bit of a red herring.

If your Application_Start() function in the Global.asax module tries to access the web.config and an entry that it’s referencing isn’t there, IIS chokes and (for some reason) throws the 403:Forbidden error message.

Double-check that you aren’t missing an entry in the web.config file that’s attempting to be accessed in your Global.asax module.

answered Sep 16, 2019 at 18:03

In case you’re like me and have an application using NHibernate and the above answers have not resolved your issue.

You should look at the connection string in your application; possibly in the webconfig file to ensure it is correct.

answered Sep 24, 2019 at 18:33

I have been using Identity Impersonate:

<system.web>
    <identity impersonate="true" userName="domainusername" password="password"/>
</system.Web>

When pushing up to the server you have to give the username access to the Temporary ASP.NET Files folder so it can read/write/execute properly:

C:WindowsMicrosoft.NET"frameworkversion""aspversion"Temporary ASP.NET Files

Obviously replace «frameworkversion» and «aspversion» with the versions you are using.

answered May 13, 2014 at 9:40

Step 1: Select the Site For which the HTTP Error is produced in IIS and then click on Directory Browsing as shown in the image below:

Step 2: In the Directory Browsing Window in IIS click on Enable in Actions on the right side as shown in the diagram below:

Now Directory Browsing is enabled for your asp.net website, just restart the web application in IIS and Browse the site in your browser and see the result.

answered Jul 30, 2014 at 21:05

HaoK

added
the

Needs: Author Feedback

The author of this issue needs to respond in order for us to continue investigating this issue.

label

Dec 3, 2021

maurik77

changed the title
asp.net .net 6: Unauthorized access returns 403 instead 401

asp.net .net 6: Unauthorized access returns 403 instead of 401

Dec 6, 2021

HaoK

added
the

breaking-change

This issue / pr will introduce a breaking change, when resolved / merged.

label

Dec 9, 2021

msftbot
bot

locked as resolved and limited conversation to collaborators

Jan 10, 2022