Unable to Connect to FTP
FTP connection issues are most commonly caused by firewall restrictions. Unlike standard web traffic, FTP requires multiple ports to handle both commands and data transfers simultaneously.
Configure Passive Port Range
If you have a firewall (either local on the server or an external hardware/cloud firewall), you must allow the FTP Passive Port Range inbound. This range is used for transferring file lists and actual file data once the initial connection is established.
Required Inbound Port Range
30000 : 31000
Protocol: TCP
Cloud Providers
If you are using a provider like AWS, Google Cloud, or Azure, remember to update your Security Groups or Network ACLs in their respective dashboards, as well as any internal server firewalls (like UFW or Firewalld).
Quick Checklist
- Ensure Port 21 (Command Port) is open.
- Ensure the Passive Range (30000-31000) is open.
- Verify you are using the correct FTP Username (usually the website name or a custom user created in the dashboard).
- Check if your FTP client is set to Passive Mode.