Website Error Messages (24 Articles)

An account or pending order under that domain already exists in our system

There are two possible reasons for you to receive this message: Another customer already has an account with this domain name or you're trying to use a generic domain for your account. In such case, please use a different domain for your purchase. Somehow, you've tried to order an account previously and the order process has stalled. In such case, please contact our Sales department via the Live Chat link on top of the site and we will assist you further. …

The web service to this account has been limited temporarily!

If you see this message on your website, this means that we've limited the access to it either because your site was hacked, or because you've exceeded some of our resource limitations. To proceed, press the  Get Limit Removed button which will lead you to your User Area where you will find detailed infromation on the limitation applied on your…

My Facebook application is displaying ‘Method Not Allowed’

If you are encountering this problem with your Facebook application hosted on your SiteGround hosting account, then your application is most likely based on HTML. By default POST is not within the allowed methods for HTML files because that language cannot process POST queries. Even though Facebook are aware of this, their API is structured to always execute a POST query to the target URL to validate its availability. When the target is HTML, it is highly likely to encounter the "Method Not Allowed" error. In order to prevent facing this error you need to change the way Apache handles requests to HTML files. The most commonly used method is to force HTML files to be handled by PHP. You can do this by creating an .htaccess file in your application's main directory, and adding the following line: AddHandler application/x-httpd-php52 .html .htm .shtm If you are having difficulties applying this fix to your Facebook application, hosted on a SiteGround hosting account, please feel free to contact our Technical Support Team and we will apply the required modifications for…

What to do if your website has been marked by Google as harmful

If you see the following warning when you visit your site: This site may harm your computer . this means that your website has been marked by Google as harmful because it contains malicious code. The first thing to do is remove all the badware/malicious code from your pages and fix the security vulnerabilities that allowed the code to be inserted in your files. It is important to fix those vulnerabilities in order to prevent such issues from happening in the future. You can try cleaning your files by yourself. You should always keep your applications up to date, so after removing the malicious code, an upgrade of your scripts is highly recommended. Alternatively, if you experience difficulties cleaning the files yourself, you can contact your host and ask for further assistance. Once the cleaning of your website is completed, you can check your website with the Google Diagnostics page. Just visit: http://www.google.com/safebrowsing/diagnostic?site=http:// www.yourdomain.com where www.yourdomain.com is your actual domain name. After you have done all of the above, you should request a review from Google's Webmasters Tools. If you don't have a Google Webmasters Tools account, you can create one for free at: https://www.google.com/webmasters/tools . Once you have created a Google Webmasters Tools account, go to the Overview page and click on the Request a review link. Then, follow the instructions on the page in order to file a Request for review of your website. Bear in mind that usually it takes approximately 10 business day before your request is reviewed and the status of your website is…

HTTP error codes explained

There are multiple HTTP codes that you may come across. Below you can find a summary of the most popular HTTP error codes: "200 OK" - You will not see this code when browsing a regular page. It means that the requested document has been processed and sent to you. "301 Moved Permanently" - Often web designers create the so-called 301 redirects. This means that instead of the file you are browsing to, the server will point you to a different directory or a file set in the redirect rules. "400 Bad Request" - The Web server considers the data stream sent by the client (your Web browser) 'malformed' i.e. it has not sent a complete HTTP request. In such cases the web server is unable to process the request. Almost always this error is caused by bad programming. "401 Unauthorized" - You are most probably trying to access a password protected directory using wrong credentials. In such cases you should check whether you are using the correct login details. If you wish to have your credentials reset, you can do this using the " Password Protect Directories " tool in your cPanel. "403 Forbidden" - This error message means that you are trying to open a folder or a file you do not have access to. If you are receiving this error message on your website, you should check the .htaccess files in your web hosting account for any restrictive rules. "404 Not Found" - You are browsing to a non-existent page or a folder. In such cases you should check if the link you are trying to access is correct. In addition, if any SEF functionality on your pages is not working correctly, your application may forward you to the wrong URL. "500 Internal Server Error" - The most common reasons for this error are bad script code, an invalid .htaccess file, wrong file/folder permissions. For more information on that matter, you can check on this article .…

Cannot modify header information – headers already sent by …

If you receive a warning on your pages similar to the one below: "Warning: Cannot modify header information - headers already sent by (output started at /home/user/public_html/index.php:581) in /home/user/public_html/system/sessions.php on line 180" there are a few things you can do in order to fix the issue: 1. You should check for any empty lines at the end of your .php files. This is a common issue with some web applications. Simply remove the empty line at the end of your script( after the final "?>" or "php>" string) and check your website again. 2. You can make a local php.ini file in the folder of your script and add the following line in it: buffer_output = on For more information on php.ini files, you can refer to this article . 3. If the warnings are not affecting the functionality of your website, you can simply hide them. Detailed instructions on how to do this can be found here .…

I’m getting a ‘MySQL server has gone away’ error in my application

There are two main reasons for this error message to show: 1) The MySQL query you are trying to execute takes too long and the MySQL server times out. The solution for this issue is to optimize your database for the queries which fail. 2) You have a crashed table in your database. The solution in this case is to repair and optimize your database. If a particular table crashes often and repairing/optimizing it does not help,  this most probably means that the table's structure has an issue with our MySQL server setup. In such cases the easiest way to fix a crashed MyISAM table for good is to change its database engine from MyISAM to InnoDB. More information on how to do this can be found in this article .…

Error: Sessions directory is not writable

By default, such an error is received when you use a custom php.ini file and the directive "session.save_path" is not set. In order to resolve it please add to your php.ini file this: session.save_path = /tmp The above change should be done in each directory you receive this…

HTTP Error 503 – Service unavailable

This error means that the Webserver is currently unable to handle the HTTP request due to a temporary overload. If you receive this error often please log in to your Customer's area and go to "Get support". Check if you don't have any CPU / memory abuse tickets opened for your web hosting account. If there are no such tickets please open a new Site-Down ticket for further investigation.…

HTTP Error – Bad Gateway

This error indicates a server side problem. Please log in your Customer area and check if there are any server status notifications. If there are no such, please submit a Site Down ticket.…

Error: Server Not Found

Such an error usually means that your domain is not pointing to the correct server. If you have a web hosting account with SiteGround, you can check these articles on how to transfer and / or point your domain to our servers .…

Connection to The Server Was Interrupted Error

The most common reason for the connection to the server was interrupted error is network or local connectivity issue. If you receive it you can try the following: Disable your local firewall while troubleshooting it; Disable your local antivirus software while troubleshooting it; Contact your local Internet service provider for additional assistance; Check your mail account settings are set according to our tutorial …

I am receiving 503 Service Temporarily Unavailable error

This error is usually caused by the web server limitation to stop working after 29 UNIX CPU load. Such errors should be very rare and we are taking all measures to ensure the server's load does not go beyond performance critical levels. However, if this error continues to show frequently on your pages, it might also indicate a problem with your account. Please log in your Customer Area and check if there are any active tickets or server notices for your account in your Help Desk. If there are no such tickets or notices, you should open a new ticket from the Site-down category. For detailed instructions how to post a ticket please refer to our Get Support Guide. …

Site shows PHP warnings / errors

PHP warnings / errors show for various reasons. In case you get such PHP messages on your website, you can do the following: 1) If it is just a warning and your scripts work properly you can disable the php warnings. This can be done with a custom php.ini file containing the following line:   display_errors = off You can create this file using your cPanel > File Manager. Please note that you should place this file in every folder where you need the custom settings to apply. 2) Try to resolve the issue. PHP warning / error messages are quite descriptive and you can often find the solution for the issue in the message. You can also Google-search for possible solutions of your problem. Almost certainly someone before you has had the same problem and found a solution for it.…

I am receiving Internal Server Error 500 after I uploaded my site files.

If your FTP client uploads the files with permissions higher than 755 you will receive Internal Server Error 500. We do not allow higher than 755 permissions due to the fact that our Apache web server runs the PHP interpreter as a CGI in SuExec mode and such permissions are considered a security risk. More information on how to change file/folder permissions can be found in our cPanel tutorial .…

An application installed through Fantastico gives errors

Reasons for errors after Fantastico installations vary. If it is a new installation, you can try reinstalling it from scratch. If the application starts giving errors after you've made some modifications, try reverting them. You can also check the application's forums and documentation for more information about the errors you get. If you believe the problem is related to your hosting service, you can contact your host for assistance.…

I am getting the following error: “Fatal Error: Maximum Execution time of 30 seconds exceeded in…”. Can you please see what is wrong or what is causing this error?

This error means that the script you use needs more time than the max execution time allowed on the server. If your website is hosted on a VPS, please contact our us and we will increase the execution time for your server. If your account is hosted on a Shared Hosting Server, however, you should consider an optimization of the script, so that it executes faster. Alternatively, you could go forward to a VPS or Dedicated Server …

My application cannot connect to my database.

If your application cannot connect to the database you should make sure that: Your application is using the correct MySQL hostname: localhost Your application is using the correct MySQL database / username / password. You can follow this tutorial for detailed instructions how to create them. You can also check cPanel's video tutorial for additional information. Don't forget to specify your MySQL username and database with the prefix yourusername_ in front of its given name. For example, your cPanel username is siteground and you have named your database joomla . In this case you have to refer to your database as siteground_joomla ; MySQL works on the default TCP port 3306. …