For me it was as simple as enabling the CGI module for apache2:
a2enmod cgi service apache2 reload
Simple steps to ensure Pure-FTPd works on an EC2 instance:
1. Enable passive mode
sudo echo "50000 50100" > /etc/pure-ftpd/conf/PassivePortRange
2. Allow access to Public IP
sudo echo "public_ip" > /etc/pure-ftpd/conf/ForcePassiveIP
3. AWS Security Groups
Allow ports 50000 – 50100 to be open to anywhere
4. Restart Pure FTPd
sudo /etc/init.d/pure-ftpd restart
5. Test FTP access
Simple bash script using the AWS Cli to backup EBS Volumes.
I used a free tier micro EC2 Amazon AMI to act as the backup generator.
AWS Interface
1. Create new policy with permission to create snapshots:
– Security, Identity & Compliance > IAM
– Policy > Create policy
– Create Your Own Policy
– Give a relevant name and insert the following into the Policy Document:
Continue reading
After installing WHM on EC2 I started to setup the individual CPanel accounts with FTP accounts.
When trying to connect via FTP with a new account I got the following error with Filezilla:
‘Failed to Retrieve Directory Listing’
From carrying out some research it turns out that a range of passive ports need to be added to your Security Group. To find the passive port range used by Pure-FTP, shell into the servers and run the following:
vim /etc/pure-ftpd.conf
Search for Passive and you should see (version 60 of WHM):
PassivePortRange 49152 65534
Add this port range (49152 – 65534) to your Security Group and test with FileZilla.
* Make sure ForcePassiveIP is set to the correct external IP
**Try to lock down the passive port range to an IP range where possible
Recent Comments