• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

FTP users problem

kojot

Regular Pleskian
Hello, since from beggining I have problem with FTP on my server.

Server is Debian 8.2 and Plesk 12.5.30 Update #20

I have no idea what can be...
At beggining I tried to set to use FTP root, and maybe that I something crashed...

Now, for every webspace I created, and FTP user for that webspace, I cant use FTP.
I tried FTP and SFTP, and ports 21 and 22, and Filezilla and WinSCP...
Only I can do, is upload over browser...

Can you help me, where to look, from what point to beggin?


edit:
now I turned firewall down, and I success to connect on FTP without problem...

What can be problem?
I saw before that In firewall all connections for FTP server are Allowed
FTP server - Allow incoming from all
 
Last edited:
Hello,

The config of FTP behind a firewall (client side or server side) is tricky but it is easy to fix if you know what is going on.

Remember that the FTP protocol uses separate TCP connections for the commands and the data transfer. In fact the port of the data connections is chosen "on the fly" and transmitted in the command connection so that the other side can start the stream pointing to the right TCP port.

If you use the "passive" mode, it is the server who starts listening on one port and indicates the client which port to use so that the client issues the connect.

If you use the "active" mode it is the client who starts listening on one port and passes the port to the server who issues the connect (yes that's right in FTP active mode it is the server who connects and the client who listens for the data transfers).

Now here comes the trick: recent versions of Filezilla default to use passive mode and SSL so you need to have the data port to where the client connects open in the firewall. If you switch to active mode (which must be explicitely enabled in Filezilla 3.10+) you need to disable SSL so that your home router detects the port used by your client and establishes an on-the-fly NAT translation.

Since not all routers can be trusted to do the NAT correctly I use the passive mode, reserving a port range for data connection and opening that port range in the firewall. This can be achieved with the following directive under let's say: /etc/proftp.d/passive_ports.conf:

PassivePorts <first> <last>

and then inserting the appropriate iptables rules or whichever firewall you are using to have that port range open to the world.

Hoping this helps,

Miguel
 
Back
Top