Manual Configuration Method for FTP Passive Mode (PASV) with Shared IP (Applicable to Shared IP Elastic Cloud)
Published: 2015-03-13
Shared IP hosts only support pasv (passive mode) upload; see help for details: http://www.west.cn/faq/list.asp?unid=32
The passive mode port is mainly to support the FTP server using passive mode. If you have purchased our company's elastic cloud host shared IP server, then for cloud hosts preinstalled with an integrated environment, by default the system has automatically configured the FTP passive mode port. If the passive mode port is not configured correctly, FTP will not work properly.
If the automatic system configuration fails, or you have installed a clean version, you need to manually configure the PASV port range of the FTP service, the starting port is: Remote Desktop port +2, and the ending port is: Remote Desktop port +4. For example, if your shared IP remote login port is 10000, then your PASV starting port is 10002 and the ending port is 10004.
Below are manual configuration methods for win and linux.
win server (supports 2003, 2008, 2012)
Please download setmsftppassPort.vbs After double-clicking to run, enter the Remote Desktop port (enter the correct port according to the instructions above), and the system will automatically configure it for you (only for the case of using Microsoft FTP; if you use another FTP server such as servU, please configure it yourself).
Note that windows2008 and windows2012 also need to set the firewall's external IP address; this IP is the remote connection IP address.
Open IIS, click the computer name, as shown in ebs-xxx >> then double-click FTP Firewall Support >>, and configure as shown in the figure:

The windows2003 system cannot set an external IP address. Uploading with ordinary FTP software may prompt that establishing a data socket failed, as shown in the figure:

You must use flashxp or FileZilla Client (highly recommended) software to upload; the upload port must be specified as the assigned FTP port.
Linux (only supports servers with wdcp environment installed)
For Linux servers, you need to modify the /www/wdlinux/etc/pure-ftpd.conf file and set the value of PassivePortRange to the correct range, for example
PassivePortRange 10002 10004
ForcePassiveIP 211.149.224.33
10002 10004 are remote port +2 +4 211.149.224.33 is the IP address used for remote connection
Note: This is only for the case of using pureftp. If you use other FTP tools, please configure them yourself.
Only after the above settings can the FTP service of an elastic cloud host based on a shared IP be used normally
