IIS 10.0 Detailed Error - 404.0 (2024)

FAQs

How to fix 404 error in IIS? ›

To resolve this problem, verify that the file requested in the browser's URL exists on the IIS computer and that it is in the correct location. Use the IIS Microsoft Management Console (MMC) snap-in to determine where the file requested must exist in the IIS computer's file system.

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.

This is a location issue with your endpoint, you're hitting the server but there isn't anything on that route. You need to check the implementation details of your API and pass the correct URL for that request. Shouldn't the content type be application/json (raw/json in the body) instead of text/plain?

If Postman fails to send your request, you may be experiencing connectivity issues. Check your connection by attempting to open a page in your web browser. Some firewalls may be configured to block non-browser connections. If this happens you will need to contact your network administrators for Postman to work.

The resource is either moved or deleted

So, whenever you move files to another folder or remove them, a 404 error is returned by the server since a requested resource or file is not found. When this happens, users may attempt to access it using the old URL or a broken link, resulting in an error.

Does 404 error mean I was blocked? ›

Understand the Error

A 404 error means that the server cannot find the requested URL. A 410 error means that the resource requested is no longer available. Essentially, the page has been deleted. A 429 error means the user has sent too many requests in a specific timeframe.

Go to IIS logs and check if there is a sub-status code for the 404 error. Go to Request Filtering in IIS Manager to make sure there is no rule affecting ASP.NET pages. Check if the other websites hosted in IIS work. Create a new website and application pool to try accessing your ASP.NET pages.

All you need to do is clear the last directory in the URL. The link for the page you are looking for should be visible on the previous page. If it is not to be found on that page then you can also go back to the previous page and look for the correct link there.

To address this issue and prevent 404 errors from showing when the page is reloaded or when a direct link is accessed, you should consider implementing server-side routing and handling of all routes in your React application.

The <httpErrors> element contains a collection of <error> elements, each of which defines an error message that IIS uses to respond to specific HTTP errors. You can add custom error messages to IIS by adding an <error> element to the <httpErrors> element in the Web. config file for your site, application, or URL.

One of the first steps to troubleshoot IIS issues is to check the logs. IIS logs can provide valuable information about the requests, responses, errors, and events that occur on the web server. You can access the logs from the IIS Manager console, or from the %SystemDrive%\inetpub\logs\LogFiles folder.