This can occur if you are uploading your images using FTP and using the Binary setting rather than ASCII. Also, your images may be getting corrupted during transfer from your computer to your website. Try using a different location from which to upload your files.
There are several possible reasons why your images are not showing up on your pages as expected:
(1) The image file is not located in the same location as specified in your IMG tag.
(2) The image does not have the same file name as specified in your IMG tag.
(3) The image file is corrupt or damaged.
(4) The image file never actually got uploaded.
Broken links or images cannot be caused by problems on the server side. They can only be caused by incorrect HTML coding or errors in uploading image files to our servers.
Troubleshooting broken images should begin with the following steps:
(1) Position your cursor over the broken image and right-click your mouse. A popup menu should appear with several options.
(2) Left-click on the option to view Properties. The Properties dialog will display the Address/URL of the image as it is defined in your HTML page. It should look similar to this:
Obviously, you want to substitute your domain name, subdirectory, and image file names where appropriate. The most common image formats in use on the web today are GIF, JPEG and PNG, so your image will, more than likely, end with either the .gif, .jpg or .png file extension.
The URL that is displayed in the property dialog shows the location that your web page is telling browsers to look for the image. Write down the path, or copy and paste it into your favourite text editor so that you can refer to it later.
Now that you know where the image is supposed to be and what it’s supposed to be named, verify that it’s there. Go to your Control Panel and click on ‘File Manager’. You will need to click on the public_html folder. The path represented by “www.mydomain.com” is your “public_html” directory, so the first place to go is to that directory. Check and see if your image is in the correct directory in the path that you have above and that the filename is correct.
You can also use FTP or Telnet (SSH) to log in to your account and navigate to the directory named in the path you’ve identified above. When you first log in to your account, you will be in your “root” or “system” directory (unless you have your client configured to automatically open in a subordinate directory.) Use the “cd” command to change directories in SSH.
Continue navigating until you reach the subdirectory (myimagedir in the example above) in which your image (myimage.gif in the example above) is supposed to be found. Once you’re there, try to locate your image file (myimage.gif in the above example). FTP clients will automatically display all the files located in the current directory. In telnet (SSH), to get a directory listing, type “ls -a” (without the quotes) and hit enter.
Chances are that by now you’ve discovered the problem. If the image file is not there, either put it there by clicking ‘upload’ in your File Manager or adjust your image tag so that it reflects the correct location.
Here are some important things to remember:
1. UNIX is CaSe SeNsItIvE. As far as our Linux servers are concerned, myimage.gif, MyImage.gif, and myimage.GIF are three completely different files. Check your file name — the filename in your directory and the filename in the path included in your web page must match EXACTLY. If they don’t, change one or the other so that they do.
2. The case sensitivity issue holds true with directory names, too. MyImageDir and myimagedir are treated as two distinct directory names. Make sure the directory names match, too.
And after all that if it still doesn’t work –
If the system path of the image file matches the URL of the browser path *exactly*, and the image still doesn’t show, then the image file may be damaged or corrupt. Make sure the image loads on your local computer (try it out in your browser) and then upload it again (in BINARY mode, if using FTP).
If it still doesn’t work, please ask for assistance.
As a first step, check the following points:-
Is your domain on the correct name servers? To use our hosting package, your domain name needs to be on our nameservers. You can check this at https://webhostingplus.uk/hosting/domain-search/. Do note that this may take a little while to update.
If you have purchased web hosting, remember that it can take up to 24 hours for the DNS changes to point your domain to your web space. During this time you can view your site using the temporary URL in your Web Hosting Plus Control Panel.
If your name servers and DNS are correct then check that you have uploaded the files to the public_html folder and make sure the index page has a small [i] in index.html and not Index.html. If your site has a differently named index page (such as index.php or index.cgi), ensure that the default index.html file has been removed.
Also make sure that you have uploaded the files using the right transfer mode: most of the FTP clients check that for you automatically but a few don’t. text/script/html files have to be uploaded using text or ASCII Mode. Images have to be uploaded using BINARY Mode.
If all of these points have been confirmed, please contact Support who will be happy to assist.
Your FTP account may be locked, for more information, consult the article on FTP locking. All accounts are locked by default for security reasons.
Firstly, ensure that you are using a good FTP client – we recommend FileZilla. Some FTP clients make it very difficult to find the settings that you need to change.
Secondly, check your settings. These can be found in your Web Hosting Plus Control Panel, but are typically:
Server or Hostname: ftp.yourdomain.com (or your FTP IP address as seen in your Control Panel)
Password: your FTP password (can be changed in your Control Panel)
Depending on your FTP client’s settings, you may have more options. Common ones include SFTP (which should be off), and Passive/Active transfers (which should be set to Passive).
Additionally, check your firewall (Norton, ZoneAlarm, AVG Internet Security, etc) – try switching it off and attempt to connect – if it works then the issue lies with your firewall and not with our services.
Finally, take a look at any errors that you see when connecting. A common one is “530 Login Incorrect” – this suggests that your username or password is incorrect. Other errors are fairly descriptive, and a quick Google search will often reveal solutions.
FTP (File Transfer Protocol) is the simplest and most secure way to exchange files over the Internet. The most common uses for FTP is to download files from the Internet, and to upload your website files to your hosting space. The ability to transfer files back-and-forth makes FTP essential for anyone creating a website, amateurs and professionals alike.
An FTP client is software that is designed to transfer files back-and-forth between two computers over the Internet, in this case connecting your computer to our hosting servers. FTP client software needs to be installed on your computer and can only be used with a live connection to the Internet. Popular FTP clients are SmartFTP, FTP Explorer and Core FTP – you can find these and more at www.download.com. FireFTP is a popular FTP plugin for the Firefox web browser which is available at the FireFTP website.
The classic FTP Client look is a two-pane design. The pane on the left displays the files on your computer and the pane on the right displays the files on the remote server.
File transfers are as easy as dragging-and-dropping files from one pane to the other or by highlighting a file and clicking one of the direction arrows located between the panes.
Additional features of the FTP Client include: multiple file transfer; the auto re-get or resuming feature; a queuing utility; the scheduling feature; an FTP find utility; a synchronize utility; and for the advanced user, a scripting utility.
The most common problems with FTP and uploading your files are usually caused by having entered incorrect FTP login details in the connection settings, or security settings and hardware (such as firewall, antivirus, local area network rules, routers, etc) preventing connection such as for example by blocking ports 20 and 21.