• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk Panel 11.5.30 U#22 - got stuck on: 'Entering Passive Mode', spontaneous

jeanmm

New Pleskian
Hi,

After the problem-free running of a busy website for some weeks, on Plesk Panel 11.5.30 U #22 with CentOS 6.4 (up-to-date).
All FTP users spontaneous got stuck on: 'Entering Passive Mode' today.
It seems that after that, any additional attempt would crash the FTP server making it total inaccessible.

- There are no further server, OS or Plesk changes made after going live. (The server operated for some time in a test environment before without problems).
- More than enough memory, processor and hard disk capacity.
- Nothing changed to the firewall.
- Restarting the server physical or the FTP services does not help.
- Creating another user or recreate old users won't work, even if it is created from scratch.
- The /usr/local/psa/var/log/xferlog log only refers to activities after the fix. Apparently nothing was formerly kept?

* Website files are allocable via the Plesk File Manager, Terminal etc.
* Website runs fine for its user, mods and guests.

It seems that there is a problem with the Plesk firewall.
Allowing the System policy for incoming traffic does fix it but it could turn into a huge security problem so that's not desirable.

Adding passive ports to the FTP configuration file and in the firewall as custom rule fixed the problem for now.
But this as a dirty fix or workaround so that moderators could do, at least there job.

So whats wrong, How can this happen all of a sudden? Are these known issues? Please provide a correct solution.
 
Last edited:
Back
Top