Overview
Apache is one of the web server products used by Plesk and therefore active on all Conetix hosting environments. At times, specific error codes may appear in your error logs which may or may not be useful in diagnosing issues. Understanding the different status codes is also critical to assist with reviewing the logs.
The table below will assist with this diagnosis.
Error Meaning
Below is a list of the error codes, the specific part of importance and if you need to action anything (or if it’s just normal behaviour).
| Code | Full Error | Reason |
|---|---|---|
| AH01068 | AH01068: Got bogus version | Apache (or PHP) may have been recently updated but not restarted. If you have your own VPS this can be manually restarted. All Conetix managed systems, this will be automatically applied. |
| AH01071 | AH01071: Got error ‘PHP message: | If this is just a standard warning, it means there’s an issue with your website but not a critical error. Your website should still be loading and the plugin / code may need updating or something fixed. You should contact your web developer or the plugin developer for further assistance. |
| AH01071 | AH01071: Got error ‘PHP message: PHP Fatal error: | This means there’s been a a FATAL error on your website. If you’re running WordPress, you may also see a critical error message. This one should be looked at further if the URL called for the error is valid |
| AH01071 | AH01071: Got error ‘Primary script unknown’ | This means that a PHP file was called, however the file (script) didn’t actually exist. This one is common where malicious bots are trying to guess filenames on your website. Unless it’s excessive (thousands of requests), it can be ignored. |
| AH01075 | AH01075: Error dispatching request to : (polling) | This means that the request timed out. It could be an indication of server load being too high, a request which relies on an external data source or a complex database query. If a longer timeout is required, this can be adjusted in the PHP settings. |
| AH01079 | AH01079: failed to make connection to backend: httpd-UDS | This is likely to be a temporary error as a backend PHP service is restarting. |
| AH01264 | AH01264: script not found or unable to stat | Similar to the AH01071 just above. |
| AH01276 | AH01276: Cannot serve directory | No index.html exists in the directory requested This is expected where a script or crawler is guessing URL’s and can be ignored. |
| AH01630 | AH01630: client denied by server configuration | The request was blocked by an explicit rule. This may be set by the WP Toolkit (eg, a direct request to a PHP file in the plugins folder) or set in a .htacess file. If the request doesn’t affect your website then it’s likely that the security rules are working as expected. |
| AH01797 | AH01797: client denied by server configuration | Similar to AH01630 above. |
| Connection reset by peer | This occurs when the remote connection disconnects unexpectedly. This may indicate that the remote user or service has intermittent internet connectivity and not a server fault. |
Further Reading
Apache have a full list of errors also published which may give some guidance. If you need further assistance, please contact our support team and we can help point you in the right direction.