FTP Usage Instructions: FTP (File Transfer Protocol)

Basic FTP Usage Instructions:

Log-in using your FTP client with the following settings:

  • server: this is the server you are on, which is noted on your account set-up message (eg., or, or [your IP address]),
  • login: this is the log-in you specified; remember that it is always <= 8 alphanumeric lowercase characters and the characters are case SeNsItIvE
  • password: this is the password you specified; remember that it is case SeNsItIvE

The web page & image directory is the ‘public_html’ subdirectory in your account — where all the web site material should be put (it maps to, or

The anonymous FTP file directory is the ‘public_ftp’ subdirectory in your account — where all the publicly-available FTP material should be put. (Non-virtuals and virtuals only have public_html. Public FTP service is only available for fully virtual clients.)
Remember that your account root login directory (eg. /home4/yourdirectory) is NOT publicly accessible, so you must put your files in public_html or public_ftp as appropriate.
Upload HTML, text, Perl (CGI), and other text-only files with the ASCII/Plain-Text mode. Only upload images, sound, video, and other binary files using the binary mode. If something isn’t working, in many cases this could be the problem and you may have to re-upload your files using the correct mode.
Any executables (Perl scripts, C/C++ programs, etc.) must be chmod’ed to 755 and have a .cgi extension. If you do not want to, or are not able to, use Telnet and your FTP program does not support chmod, here is how to do it with the Win95/8 supplied text-interface FTP program (note: we still recommend to use Telnet, if you have a Telnet login account, as that is easier; refer to Telnet usage for details):

  • From the Start Menu, select RUN and enter “ftp yourdom.ain” (or “ftp”, where X is the server number you are on).
  • When prompted, enter your username and password.
  • Change directories to the one that contains the file you want to change file permissions on. (eg. “cd public_html”)
  • (you can use “pwd” to get the current directory and “ls -al” to list it)
  • Then use the following to set the permissions:
  • literal site chmod 755 filename.cgi
  • where “filename.cgi” is the name of the file you want to change
  • This sends a literal command to your site and you may use the chmod command on your files. This will also work for other similar commands, such as chown and chgrp.

SSH Tunneling
The concept behind SSH tunneling is you create a secure “tunnel” between your local host and your server. You can do this for any TCP/IP based connection including FTP and POP. Once that is created, you use your client (whatever that may be, FTP or mail) to connect to one end of the tunnel (your local host). This will automatically “shuttles” you through the other end (your server) and fetch your mail or your files securely. It would be difficult for anyone to penetrate.

We will just outline the steps to use SSH tunnel for FTP here:

1. On your F-Secure or other ssh client, you should be able to do a Port Forwarding
Local Port: 21
Remote Port:21
Remote Hostname: your server name (or your server’s IP)

2. Connect using SSH as usual. Once the connection is up you have a FTP tunnel (more specifically, a Port 21<===>Port 21 tunnel)

3. launch your FTP client,
HostName/Address = localhost or
Remote port = 21 (default)
Passive Transfer = On

4. Connect and transfer files. You will be prompted for login and password for your dedicated server.
Advanced Options Available:

We use the powerful ProFTPD FTP Server. It offers a number of special settings that you can make use of within an .ftpaccess file. This is especially useful for your public anonymous FTP areas and for resold FTP accounts.

ProFTPD Reference lists all the available configuration directives. You can make use of any directives whose “Context” includes .ftpaccess. If you need us to alter any of your site default settings that you cannot change via the .ftpaccess file, don’t hesitate to contact support and we’ll be glad to oblige presuming your requested changes are not a security or a performance risk.

by Richard Norwood