Error Messages

Through the Error Messages screen you are able to set up, edit and remove the messages that will be displayed when an error occurs on the website. As an administrator, you are able to display your own error messages or simply redirect the user.

An error message is often displayed to the user when something unexpected happens on your web server. There are multiple reasons an error message may be displayed, from broken links and failure to login to program errors. To describe what actually happened, error messages include a code that explains to the user what happened.

myMamut includes a series of default error messages, but you are able to edit them if you wish to do so.

How to edit the default error messages

Create the file that will be representing the error message, for example in HTML.
Use your FTP account to set up the folder you would like to store your error messages in.
Upload the file containing the error message to the error message folder created in step 2.
In myMamut, click Products in the top menu and select your domain through the radio buttons, in case you have more than one.
Click Windows Web Server and then Server Configuration.
Under the Error messages panel, find the error message you would like to edit via the error code in the corresponding column.
Read more about error codes below.
Click Edit.
In the Response drop-down list, select Execute URL.
In the URL/File name field, enter the target URL of the URL of the file you uploaded in step 3. Note that the URL should be written in an absolute path format, excluding the name of the domain.

Note! The absolute path of a folder created directly in the wwwroot folder will be http://www.mydomain.com/my_folder. Once the domain name is excluded, the absolute path is /my_folder/.
Click Save.

The error message has been edited.

How to redirect a customer to another page of your site when a file is not found

Click Products in the top menu.
Select the domain through the radio buttons, in case you have more than one.
Click Windows Web Server and then Server Configuration.
Under the Error messages panel, find the error message you would like to edit via the error code in the corresponding column.
Note! You can read more about error codes below.
Click Edit.
In the Response drop-down list, select Redirect.
In the URL/File name field, enter the URL of the page the customers will be redirected to, for example the homepage http://www.domain.com.
Click Save.

The customer will now be redirected to another page.

Tip! You are also able Remove existing errors messages and Restore them by clicking the respective links in the Actions column.

Error message codes

The most common error codes are:

401 Unauthorised: You do not have the correct permission to access the file/folder.

403 Forbidden: You do not have access to the file/folder and you will not be able to access it by providing login details.

404 Not found: The page you are trying to access does not exist.

405 Method not allowed: A request method that is not supported has been attempted.

406 Not acceptable: A request is returning a response defined as not acceptable in the request header.

412 Precondition failed: The server does not meet the stated preconditions.

500 Internal Server Error: A generic error message given when none of the others are suitable.

501 Not Implemented: The server either lacks the ability to recognise a request or the ability to fulfil it.

502 Bad Gateway: Acting as a gateway or proxy, an invalid response was given from the upstream server.

In addition, each error message can be further defined by the server giving a more specific reason about what happened:

401.1 Unauthorised: Access is denied due to invalid credentials &endash; you tried to login, but the login attempt failed.

401.2 Unauthorised: Access is denied due to server configuration &endash; the web browser and server failed to communicate during the login attempt.

401.3 Unauthorised: Access is denied due to an ACL set on the requested resource &endash; you were able to login, but had insufficient permission to access the content requested.

401.4 Unauthorised: Authorisation denied by filter &endash; an ISAPI filter cannot complete the request due to an authorisation problem.

401.5 Unauthorised: Authorisation failed by an ISAPI/CGI application &endash; An ISAPI or CGI application does not complete the request due to an authorisation problem.