Bobcares

HTTP Error 404.3 – Not Found – How to fix it

by | Oct 17, 2019

Website errors always make users panic.

A common error in Windows-based websites is HTTP Error 404.3 – Not Found.

This error happens due to missing script handlers or MIME mapping in the IIS web server.

At Bobcares, we often get requests to fix HTTP errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix the HTTP 404.3 error.

 

What does the HTTP error 404.3 indicate?

Usually, when the server is unable to serve the browser requested page, it shows errors as HTTP status codes. One such error is HTTP Error 404.3 – Not Found.

Here the code 404 indicates that the requested page is not found due to some reasons. Also, it shows a sub status code 404.3. This indicates a MIME restriction. The error message clearly explains this. The typical error message appears as:

HTTP error 404.3 not found.

This error occurs on the website hosted on windows and the IIS web server. Basically, this error can occur If the requested page is script, then an appropriate handler is missing. Or else, if the images or videos are not loading then the corresponding MIME-type is not present. This error can also appear if the ASP.NET feature is not enabled.

 

Fixing the HTTP error 404.3

As the error code describes, the reasons for this error are missing script handlers or ASP.NET features and also because of inappropriate MIME mapping. Let’s see how our IIS Experts fix this error for our customers.

 

Install ASP.NET feature

ASP.NET feature needs to be installed on the server for .NET files to load. If the feature is not enabled we get HTTP 404.3 error.  Let us discuss how our Engineers enable the feature.

  1. Click on Start >> Administrative Tools >> Server Manager.
  2. In server manager, Click on Add roles and features.
  3. Then click on features. Expand the .NET Framework.
  4. Now we select the required ASP.NET framework. After selecting the ASP.NET option ISAPI Filters, ISAPI Extensions, .NET Extensibility options will be selected automatically.
  5. we run the command based on the windows architecture.
  • For 32bit (x86) Windows:

%windir%\Microsoft.NET\Framework\v4.0(framework version)\aspnet_regiis.exe -ir

  • For 64bit (x64) Windows

%windir%\Microsoft.NET\Framework64\v4.0(framework version)\aspnet_regiis.exe -ir

Finally, we verify the domain’s application pool is using the installed framework.

 

 Adding a script handler

Most websites work on scripting languages like PHP, .NET and so on. So, the webserver must have the corresponding script handler to serve the requested page in the browser. Usually, if this is missing the websites show a 404.3 error.

The steps to configure IIS to handle PHP requests are:

  1. Firstly, we open the Internet Information Services(IIS) Manager.
  2. Now in Home>> Server Components we select Handler Mapping.
  3. Next in Action pane, we click Add Module Mapping.
  4. Now a dialog box opens, here we add:
  • Request path: *.php
  • Module: FastCgiModule
  • Executable: “C:[Path to PHP installation]\php-cgi.exe”
  • Name: PHP via FastCGI

Finally, we click OK and confirm the dialog box that appears.

So, to ensure its working, our Support Engineers check the PHP info page, which gives the FastCGI module details.

 

Selecting MIME-type

MIME aka Multipurpose Internet Mail Extensions Type identifies the type of content served to the browser.

So, selecting MIME-type in the localhost is also important. By default, the IIS server has MIME-types installed for common file contents. This includes html for text-based files, .jpeg for images and so on. But, for a new or latest file contents, we need to add it to the MIME-type list. To add this to the IIS server our Support Team follows the steps.

  1. Firstly, open we Internet Information Services(IIS) Manager.
  2. Now, in the Connections panel, we select the site/ application/ directory that needs a new MIME type.
  3. Next, in the Home panel, double-click MIME Types.
  4. Here, the default MIME-types will be present.
  5. Next, select Add option and we add the needed MIME-types.
  6. Finally, we restart the IIS.

Hence, in most cases, selecting MIME-type fixes the error.

 

[Still having trouble in fixing HTTP errors? – We’ll fix it.]

 

Conclusion

In short, the HTTP Error 404.3 – Not Found occurs on a website hosted in windows and IIS web server. Basically, this occurs due to missing script handler or improper MIME-type. Today, we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF