About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
You browse to a site or a folder on IIS and get:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Microsoft's documented causes are about the default document and directory browsing, not permissions. IIS is telling you it received a request for a folder, found no default page to send, and is not allowed to show a list of the files instead.
What you see
- The error page shows HTTP Error 403.14 - Forbidden, with HRESULT: 0x00000000 and the description above (Microsoft Learn, HTTP Error 403.14 - Forbidden when you open an IIS webpage).
- Microsoft's status code list names 403.14 Directory listing denied: the server isn't set up to show a directory listing, and a default document isn't set (Microsoft Learn, HTTP status codes in IIS).
- It happens on a request for a folder, such as the site root, rather than a named file.
Why it happens
When a request arrives for a folder, IIS looks through its default document list in order and sends the first file in the list that exists. Default documents are on by default. Microsoft's configuration reference lists the server-wide defaults as Default.htm, Default.asp, Index.htm, Index.html and Iisstart.htm. Installing ASP.NET adds Default.aspx (Microsoft Learn, Default Document <defaultDocument>).
If no default document can be served, IIS can fall back to a directory listing, but only when Directory Browsing is enabled. Its default setting is off (Microsoft Learn, Directory Browse <directoryBrowse>).
Microsoft's 403.14 page gives the cause as one of these: the default document isn't enabled or configured properly, or Directory Browsing isn't enabled. It follows that the cause can be any of:
- Default documents are turned off for the site or folder.
- The site's home page is not in the list, for example a site whose home page is named
home.htmlorindex.php. - The file is not in the folder IIS is looking in. Microsoft's page says the default document must exist in the site's root folder. It follows that a site pointing at the wrong folder after a deployment, or a deployment that did not copy the home page, gives the same error.
- A lower-level configuration removed it. The
<defaultDocument>element can contain<remove>and<clear>entries that drop files inherited from higher-level configuration.
How to prove the cause
1. Check the default document setting. In IIS Manager, select the site (or the folder), and in Features View open Default Document. Check it is enabled, and note the files listed and their order.
2. Check what is actually in the folder. Find the physical path configured for the site in IIS Manager. Open that folder and check whether any file in the default document list is there. This is the step that catches a wrong path or an incomplete deployment.
3. Check the site's Web.config. Look for a <defaultDocument> section with enabled="false", <clear /> or <remove> entries, which change the list inherited from the server.
4. Test with the file name. Browse directly to the home page by its full name (for example /home.html). If that works, the page is there and only the default document setting is missing. This follows from how Microsoft describes default document handling.
The fix
Add or enable the default document. This is Microsoft's Method 2:
- In IIS Manager, select the site, and in Features View open Default Document.
- In the Actions pane, select Enable if it is disabled.
- If the site's home page is not listed, select Add, type the file name and select OK. Microsoft says the file must exist in the site's root folder and should preferably be first in the list.
Microsoft's configuration reference gives the command-line equivalent, here for a site named Contoso and a file named home.html:
appcmd.exe set config "Contoso" /section:defaultDocument /enabled:true /+files.[value='home.html']
Microsoft also notes that putting the file you actually use near the top of the list helps performance, because IIS checks each name in order.
Correct the folder. If the site points at the wrong folder, or the home page was not deployed, correct the physical path or deploy the missing file. This follows from Microsoft's requirement that the file exists in the root folder.
Directory Browsing (only if you want a file listing). Microsoft's Method 1 is to enable Directory Browsing for the site. Use it only where showing visitors a list of every file in the folder is what you intend; see Risks and limits.
How to confirm the fix
- Browsing to the site root or folder returns the home page, not 403.14.
- In IIS Manager, Default Document is enabled and your home page file is listed.
- The site's IIS log shows the request answered without a 403 status. Microsoft says IIS records status codes in its logs, by default under
inetpub\logs\Logfiles.
What to watch afterwards
- Deployments. It follows from the cause that a release that renames the home page, changes the site's folder or misses a file can bring the error back. Check the root page after each one.
- Web.config changes that add
<clear />to<defaultDocument>. That removes every inherited default document name. - New folders or applications that should have their own home page.
Read next
Related articles you may want next.
- TroubleshootingIIS HTTP Error 500.19 "The requested page cannot be accessed": read the error code, then the configHTTP Error 500.19 means IIS could not use the site's configuration. The HRESULT code in the error tells you which of Microsoft's documented causes you have: bad XML, a locked section, permissions, a duplicate entry, or a missing module.Read article
- TroubleshootingIIS 502 and 503 Errors: Find the Failing Request LayerUse IIS status fields, worker-process evidence and proxy logs to separate application-pool failures from upstream errors and backend timeouts.Read article
- TroubleshootingASP.NET Core Will Not Start on IIS: Diagnose 500.30 and 500.31Match the hosting-module error to runtime, deployment and startup evidence and select a scoped correction.Read article
Risks and limits
- Directory Browsing shows everything in the folder. It is off by default. Microsoft's page offers enabling it as a fix, but it follows that it lists every file in the folder to anyone who browses there, including files you did not mean to publish. For a business website, adding the default document is the fix to use.
- Microsoft's configuration reference says that if both default documents and directory browsing are disabled, IIS returns 404 File Does Not Exist rather than 403.14. A 404 on the site root can therefore have the same cause.
- Microsoft's Method 3 (
appcmd set config /section:directoryBrowse /enabled:truein the IIS Express folder) is for developers using IIS Express, not production IIS. - A 500.19 error, rather than 403.14, means IIS could not read the configuration at all. That is a different problem.
Sources
- Microsoft Learn, "HTTP Error 403.14 - Forbidden when you open an IIS webpage" (KB 942062), last updated 8 January 2025: https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/iis/health-diagnostic-performance/http-403-14-forbidden-webpage
- Microsoft Learn, "HTTP status codes in IIS" (KB 943891), last updated 8 January 2025: https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/iis/health-diagnostic-performance/http-status-code
- Microsoft Learn, "Default Document <defaultDocument>", last updated 6 April 2022: https://learn.microsoft.com/en-us/iis/configuration/system.webserver/defaultdocument/
- Microsoft Learn, "Directory Browse <directoryBrowse>", last updated 21 March 2022: https://learn.microsoft.com/en-us/iis/configuration/system.webserver/directorybrowse
Next step
403.14 means IIS found no default page in the folder it was asked for: check the default document list, then the folder the site actually points to. NetLeverage has looked after business servers since 2002. If your site still shows the error, talk to us through managed support with the site's physical path and its default document list.
This article was originally published on .