This article is specific to customers who may have exceeded normal usage for our servers. We have listed the top reasons that can cause high usage below along with articles that can help you address those issues. If we have sent you a resource overage warning we likely also included some data from the server that can point to what specifically is causing the issue. If it is a known issue, we have also included tips to help you address it. If not and you would like a second look by our system administrators, simply reply back to the message and our system administration team can further assist you.
1. Brute Force Attack
2. Wordpress Caching
3. Wordpress Admin Ajax
4. Imap I/O
5. Hacked Account
6. Robots
If you are seeing many hits to something like a wp-login.php you may follow these steps to prevent future attack attempts.
You can resolve this resource intensive issue by installing either W3 Total Cache or WP Super Cache.
This can easily resolved by following the guide explaining more about wordpress heartbeat.
Currently the best actions you can take are requesting for your email to be archived and change your email client settings to reduce how many times your email account re-checks for new emails. For assistance on this you may contact our support depoartment.
Here are the best ways to recover after having a hacked website/account.
This issue can be resolved by setting up a limit of how many times a robot may crawl your website.
If you need further assistance reply to the resource overage email and our systems administration team will be happy to assist you in any way they can.
A 200 response code means the connection has been successful and the browser will serve the websites content.
This code explains that the connection is only requesting parts of the website such as just the code with a wget command, this code can be fairly common.
This code lets the browser know that the url has been moved permanately to a new location and to forward all future request to the new location.
This code is very similar to 301 but instead of a permanent move, it is temporary.
This code is a way to redirect web applications to a new URL.
This indicates that the browser has a cached copy of the website and the website has not had any modications since the browsers last visit.
The server is not able to process the clients request due to something wrong with the client (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Similar to 403 Forbidden, but specifically for when authentication is required to continue to the website.
The request was valid, however the server is refusing the connection due to configuration settings.
The file requested resource could not be found but may be available again in the future. If your website is showing many 404 hits and you are using Wordpress SuperCache then you should switch to WP Total Cache as this plugin will cache the 404 page to prevent additional account resources. You can read more on 404 errors here.
A request was made to the website which was different than it was programmed to handle such as using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
This code means that the server has blocked the request via mod_security. For more information on this code please read this article.
The request is larger than the server is willing or able to process.
This error is generally specific to something written in the .htaccess file that is not valid syntax or the website file permissions are in correct.
The server was not programmed to handle the type of request, or it was not able to fulful the request.
| Email: | support@WebHostingHub.com | Ticket: | Submit a Support Ticket |
|---|---|---|---|
| Call: |
877-595-4HUB (4482) 757-416-6627 (Intl.) |
Chat: | Click To Chat Now |