Posts Tagged ‘error’

How to set custom error page in DirectAdmin?

1. Create your custom error page. This could be for 500 error (internal server error), 404 error (page not found), 403 error (forbidden), 401 error (authorization required), 400 error (bad request).
2. Login to DirectAdmin server control panel.
3. Locate link Custom Error Pages.
4. Choose any file to edit for certain error page.
5. Paste your web page source code to the editor and click Save As.

The same steps valid for every error code. Alternatively you can select error page for each directory by creating .htaccess file in each directory (if there is no .htaccess file).
Copy this line to the end of your .htaccess file:
ErrorDocument 401 http://yourdomain.com/nopassword.html

This code should be for each error you want to set the custom page. Reemember use the correct editor to edit .htaccess (e.g. Notepad ++).

How to check the log of Apache error log?

To check you website apache log you need to:
1. Login to DirectAdmin server control panel.
2. Locate Site Summary / Statistics / Logs.
3. If you want to access full apache log click on Full Error Log or alternatively if you want to check last ’10 lines’ of your apache log click on ’10 lines’ or last ’100 lines’ click on ’100 lines’.

HTTP Error 500 – Internal server error

The server failed to fulfill an apparently valid request.
Response status codes beginning with the digit “5″ indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.

500 Internal Server Error
A generic error message, given when no more specific message is suitable.

HTTP Error 403 – Forbidden

The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. These are typically the most common error codes encountered while online.

403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.