(02-27-2016, 05:36 AM)Me.B Wrote: Did you you test first in local before using the WAN ip ? To be sure it's not a routing problem.
Hello, first sorry my english, so, i had a similar problem with FTP of sentora, yesterday a created a AWS free t2.micro instance, using an elastic IP, (that is a Public static IP), but the instance have too a provate address, when i try to conect remotly vis FTP i get a pasive error (no remember exact error), the point is that the FTP was conecting to my public IP, but get request from my Provate IP.
Escenary:
Sentora 1.0.3
Ubuntu server 14.04 virtualized on Amazon AWS
Example:
Private IP: 192.168.1.10
Public IP: 208.1.1.1
FTP conect to 208.1.1.1 an spect a request from that IP, but get requets from 192.168.1.10 and that cause the error. Searching on google, the solution (i dont test it), was use filezilla FTP cliente and configure some paramters, so i search more and find a solution.
Firts the masquerade adresss is for NAT the PUBLIC IP TO THE PRIVATE IP, so that you know, u have to modify: /etc/proftpd/proftpd.conf file (in ubuntu)
MasqueradeAddress 208.1.1.1
there are my public IP.
HERE ARE THE MAGIC
But this only change not solve the problem, beacause the Pasive FTP functionality needs a Range of ports that you have to configure in the same file and of course open in your firewall too ad this line in the /etc/proftpd/proftpd.conf
PassivePorts 1024 1124
save changes, restart your FTP service:
sudo service proftpd restart
Try connect normally via FTP
NOTE: I have too a LAB virtual server (sentora 1.0.3 and ubuntu server 14.04.4) runing in virtualbox on windows 8.1 laptop, using DDNS to internet access, and this no need that config, FTP works with the sentora standar setup
Thats all, i hope tha this info help you, i kno that i have to mention just the port part but is not a particle problem so it can help more people.
Cheers, ciao.
