WoWHost UK

Archive for the ‘Customer How To’ Category

Some ISPs block port 25 for the sending of email via SMTP. AOL and Orange are known to be amongst such ISPs, though there are also others. If this happens, setting SMTP to port 587 instead of port 25 will allow you to send email through us.

PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with this error message. This is usually the result of the PHP script trying to load a large file, such as an image, into memory all at once. While it is better if you can arrange for the script not to do such things, it is also possible to increase the memory limit to avoid this problem. To do that, edit (or create in your script’s folder if it does not exist) the php.ini file with your PHP scripts (create it if it does not exist) and add the following line:
memory_limit=16M

You should replace the ’16′ with whatever value is appropriate. The default is 8M (8 megabytes, the 8388608 bytes from the error message).

If this does not resolve the problem, you can also increase the web server memory limit by editing (or creating in your script’s folder if it does not exist) the “.htaccess” file and adding the following line:
RLimitMem 128000000

First of all, check that the link is correctly spelled, and that the correct case is used – INDEX.HTML is not the same as index.html.

Next, check the file paths. A common error is to leave the location relative to another computer’s filesystem, eg:-

<a href=”C:\Documents\MySite\mysite.html”>Link</a>

This is incorrect as it refers to a file on your PC, not on our servers. File paths should either be absolute, eg:-

<a href=”http://mysite.com/mysite.html”>Link</a>

or relative, eg:-

<a href=”mysite.html”>Link</a>, if mysite.html is in the same directory as the page that it’s linking from.

Finally, check that there are no conflicts with other scripts on the site. Many major CMSes such as WordPress and Joomla use URL rewriting that will interfere with the correct operation of links.

This error indicates that there is no valid home page, or that permissions have been set on a page which does not allow you to view it.

Cause 1: Missing or wrongly named index file

When you don’t specify a file name when accessing a site (eg visiting the domain directly as most do at http://www.domainname.com), the server searches through a list of default filenames and will display the first one it finds. Common default names are index.php, default.htm, index.htm and index.html – The first page of your website should use one of these names, with all lowercase letters.

When we create your web hosting account, we place a simple index.html file on the server so that there is something there before you upload your site. If you delete this file and don’t replace it, then you will see the error message above. To fix this, ensure that the first page in you site is called index.html and that the file is uploaded to the public_html directory.

Cause 2: Incorrect Access Control Settings

This error will also be displayed if the directory access settings for your site’s root directory are set with access criteria which you do not meet. Usually these settings are contained in a file called “.htaccess”. This file is sometimes generated manually, but can also be configured by some web development tools, such as MS FrontPage.

If you are using FrontPage, then you should alter the web permissions using this program, and republish your site. In most other cases, manually removing the .htaccess file usually solves the problem.

The path to your website is partially determined by your domain name, but is in the following format:
/home/sites/your-domain-name.com/public_html

If you are using PHP, you can find out this path by entering the following into a php script:
echo getcwd();

Becuase of the way in which we run PHP, you are able to customise its behaviour with php.ini files. These are plain text files (use Notepad if running Windows, TextEdit in Plain Text mode on Mac), which contain directives such as:-

memory_limit = 24M

A complete list of php.ini directives can be found here:-

http://www.php.net/manual/en/ini.list.php

-: you should only set these as per the requirements of your application as other settings may cause your scripts to malfunction or be vulnerable to attack.

If you are running PHP5, you should name this file php5.ini, for PHP4 it should be php.ini . Unless otherwise required, these should be located in the root of your hosting package (ie, above public_html).

php.ini files can be used for very fine-grained control – a PHP script will pick up the settings in the php.ini file closest to it, so you can enable functions for a single folder rather than the whole site – this is useful when running CMSes on subdomains.