Are you looking for a solution to the Plesk error “FTP failed to retrieve directory listing”? We can help you fix it.
Here at Bobcares, we have seen several such Plesk errors as part of our Server Management Services for web hosts, Plesk users, and online service providers.
Today we’ll take a look at the causes for this error and see how to fix it.
What causes the Plesk error ‘FTP failed to retrieve directory listing’ to occur
Many Plesk users come across this error message while connecting to FTP through FileZilla.
This error indicates that FTP was able to connect successfully. However, it failed at the directory listing stage.
It occurs if the ProFTPd passive mode is not configured on the server.
For instance, the error appears as below.
Command: PASV
Response: 227 Entering Passive Mode (xx,xx,xx,xxx,xxx,xxx)
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
How we fix Plesk error ‘FTP failed to retrieve directory listing’
Now let’s see how our Support Engineers resolve this error message.
Configuring ProFTPd passive mode
- First, access the path /etc/proftpd.d and create a file passive_ports.conf. Then add the below text in it.
PassivePorts 40000 40500 - Then add the ports range 40000 40500 in the firewall
Configuring Firewall
- Log into the Plesk panel and then choose the option ‘Tools & Settings’
- Here choose Firewall >> Modify Rules >> Add Custom Rule
- Now, you name the rule as “FTP Passive Ports” or something else and leave the remaining details as default.
- Next, enter port range 40000 40500 and click ‘Add'(leave the remaining details as default).
- Finally, click on the ‘OK’ button to save the changes and ‘Apply’ so that the rule takes effect.
Now you must be able to access FTP without any error.
[Need any further assistance in fixing Plesk errors? – We are here to help you.]
Conclusion
In short, this error occurs if the ProFTPd passive mode is not configured on the server. Today, we saw the solution provided by our Support Engineers to resolve this error.
0 Comments