Knowledgebase : File Transfer Protocol

You have created a FTP Account through Plesk Control Panel, but when you try to connect your FTP site you get this error "error 530 User cannot log in, home directory inaccessible."

Server Configuration:

  • Windows Server 2008 or 2008 R2
  • Plesk Control Panel
  • IIS 7 or 7.5
  • Microsft SQL Server 2005, 2008, 2008R2

Solution:

  1. Connect to your server using RDP
  2. Connect to SQL Server using Microsft Management Studio Express
  3. Expend Datatbases
  4. Expand Plesk Database
  5. Expend Tables
  6. Right Click on dbo.domains and Click Edit  Top 200 Rows
  7. Check if your domain "Status" has any other status than 0, if the status is already set to 2, 4, 16, 64, 256 set it ot "0".
  8. Close the table and recreate the FTP Account in Plesk Control Panel.
  9. Now try to connect your FTP site. You should be able to login and browse site's Files and Folders.

Feel Free to leave your comments.

As well as uploading your website, WISE-FTP will also allow you to back up your website content.

 

Step 1
Open WISE-FTP and click Connect in the top left corner.

 
 

Step 2
The Site manager window will appear, choose your profile and click Connect at the foot of the screen.

 
 

The screen is split into two sections. On the left hand side of the screen will be a list of the files on your computer. On the right hand side of the screen will be a list of files located on your webserver.

Step 3 

In the left hand pane, highlight the folders you would like to back your website up to. In the right hand pane, select the files or folders you would like to back up.


In the following example we will back up all the files on the web server to a folder on our local machine named “Back up of my website”.

 
 
Step 4
Click the download button to back up your website in the folder you specified.
 
 

Step 5
Once complete you should see your website files copied over onto your local computer. This can be checked by looking in the left hand window pane.

 
 

Full documentation on WISE-FTP can be found at: http://www.wise-ftp.com/download/Users_Guide_WISE-FTP_5.zip

Further support is also available at: http://www.wise-ftp.com/support/index.htm

 

The following article provides System Administrators with instructions to help them implement an FTP solution to allow for successful file exchange with their servers from remote locations.

Benefits of FileZilla:

  • secure file transfer via SSL/TLS (can be required) or even Kerberos
  • takes up little hard drive space (max is ~10.3 MB)
  • comes without the IIS security concerns you would have if you deployed FTP services via Windows (IIS required)

To install FileZilla server, please follow these steps:

  1. Log into your server through Terminal Services or Remote Desktop Connection.
  2. Open a Web browser and load http://sourceforge.net/project/showfiles.php?group_id=21558
  3. Scroll to the bottom and download the latest install file under FileZilla Server, FileZilla_Server-0_9_23.exe.
  4. Once the download completes, run the .exe file.
  5. Read the License Agreement and choose "I Agree" to proceed.
  6. Select the components you wish to install and click Next
  7. Select the Destination Folder and click Next. We recommend using the default settings. 
  8. Select how the services should be started and click Next. We recommend using the default settings. 
  9. Select how the server interface should be started and click Install. We recommend using the default 
  10. Click Close to finish the installation.
  11. Click OK to connect to the FileZilla server

 


In active mode FTP the client connects from a random unprivileged port (port number > 1023) to the FTP server's command port, port 21. Then, the client starts listening to port N+1 and sends the FTP command PORT N+1 to the FTP server. The server will then connect back to the client's specified data port from its local data port, which is port 20.


Firewall on Active FTP - what ports should be opened on server and client side?

On server port 20 and port 21 must be opened on the client (home user) ports higher than 1023 must be opened for successfull ftp connection and transfer of files.

In passive mode FTP the client initiates both connections to the server, solving the problem of firewalls filtering the incoming data port connection to the client from the server.


When opening an FTP connection, the client opens two random unprivileged ports locally (port number > 1023 and port number+1). The first port contacts the server on port 21, but instead of then issuing a PORT command and allowing the server to connect back to its data port, the client will issue the PASV command.


The result of this is that the server then opens a random unprivileged port (P > 1023) and sends the PORT P command back to the client. The client then initiates the connection from port (port number+1) to port (port number) on the server to transfer data.

The passive FTP protocol is very good because a lot of connections on internet are over ADSL, cable... and clients use routers to connect to the internet. Routers usualy filter data so active ftp protocol can not be used. This problem is solved with active file transfer protocol.

Firewall on Passive FTP - what ports should be opened on server and client side?

On server port 21 and ports (port number > 1023) must be opened. On client side no change is needed.

This is a quick tutorial on using FileZilla.

Computer / Software You Will Need:

  • A PC running Microsoft Windows, Linux, or Mac OS X 10.5 or newer.
  • The free FTP software, which you can download by clicking FileZilla.

 

Individual Server Settings:

  • Username - This is your username to access your account on our server.
  • Password - This is the password assigned to you by the system admin or the owner of the hosting account.

 

Using FileZilla

After you have downloaded and installed FileZilla, double click the icon to launch the program.

  1. Click on File then select Site Manager.
  2. You will see the "Site Manager" window pop up. Click on "New Site"
  3. You will want to change the values to match your account.
    1. Type in the New FTP Site Name: (Can use any name like "My website ")
    2. Host: Type in the host address: (Your FTP address like ftp.domain.com)
    3. Logon type: Select Normal
    4. User: This is your username. If you do not have this information, you can get it from your Welcome_Email.
    5. Password: This is your FTP password. If you do not have this information, you can get it from your Welcome_Email.

When the above steps are complete, click 'Connect' to connect to the server. (You will automatically be connected in your own folder).

Short for File Transfer Protocol, the protocol for exchanging files over the Internet. FTP works in the same way as HTTP for transferring Web pages from a server to a user's browser and SMTP for transferring electronic mail across the Internet in that, like these technologies, FTP uses the Internet's TCP/IP protocols to enable data transfer.

FTP is most commonly used to download a file from a server using the Internet or to upload a file to a server (e.g., uploading a Web page file to a server).

FTP is a TCP based service exclusively. There is no UDP component to FTP.

There are two ways to communication with FTP and that is: active and passive.

FTP is an unusual service in that it utilizes two ports, a 'data' port and a 'command' port (also known as the control port). Traditionally these are port 21 for the command port and port 20 for the data port. The confusion begins however, when we find that depending on the mode, the data port is not always on port 20.

When you set up your webhosting, we will automatically create some directories within your webspace for you.

  • httpdocs

  • logfiles

After connecting to your web space with an FTP program you will be automatically logged into the httpdocs folder. You can naviage up a level to see the other directories we have created.

 

  • httpdocs: All your web content should be stored in this directory, or a sub-directory of this. Your home page should be within this directory and should be named index or default. Within the httpdocs folder, you will see that another subdirectory has been created.

  • cgi-bin: The cgi-bin directory is for files that require execute permissions. For example Perl or Python scripts, or compiled CGI. HTML and PHP files will not work if placed in this directory.

  • logfiles: The logfiles directory contains the raw logfiles for your domain. This is where any monitoring software such as Matrixstats will get the information needed to show you website statistics. You should not upload any files to this directory.

 

 

FTP software will allow you to upload files in different formats. Perl and Python scripts should be uploaded in ASCII, while compiled CGI should be uploaded in binary.

 

What to Call your Home Page

When someone visits a folder on your website, the webserver will look for the default document within your httpdocs folder. Our webservers are configured to look for a file called index or default, to display as your home page.

 

While it is good practice to have just one default file within your htdocs folder, if you have more than one, the server will display whichever is highest on its precedence list. The order that it chooses a default page is slightly different, depending on the type of server you are using.

 

Below is a list of default files, with the highest priority at the top.

  • default.html

  • default.asp

  • index.htm

  • index.html

  • index.php

  • index.pl

  • default.aspx

To help secure our network and access to customer accounts, we have disabled anonymous FTP connections. Anonymous access enables a user to connect to a system through FTP without the need of a username and password. Through that anonymous FTP connection, the user has the potential to upload and distribute any type of content through your account resources without your knowledge. For example, a user could FTP into your account, upload a large number of music files for public distribution. As the account owner, you would be held accountable for any and all bandwidth overages and damages caused by the distribution of the music files.