• 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 11.0.9 Panel - FTP no more working

Christian Schopf

New Pleskian
Dear Sir or Madam,

I run a virtual ubuntu server and after the plesk update from 10.04 to 11.09 it isn't possible anymore to login to the Server via FTP with my root Account.
Logging in with an FTP Account for Webspace is working well.

What can I do? Maybe anyone other with this problem?

It seems that you integrated a proFTP Alpha

Code:
[*]  Upgrade of supplied components. Panel 11.0 includes the following components:

[B]ProFTPD 1.3.4a[/B]
phpPgAdmin 5.0.3
PHP 5.3.10 for customer websites
PHP 5.3.10 for the Panel web interface
phpMyAdmin 3.5.6
openssl-0.9.8 on CentOS 5
BIND 9.8.1-P1
nginx 1.3
 
root FTP is dangerous. Why you don't use file manager under plesk panel to manage all files?
 
Don't try to add the root user in the FTP config.

Instead, use SFTP (FTP over SSH).

You can download a package such as WinSCP which allows you to connect via SSH and transfer files to and from the server in a similar way to using an FTP client.

Please be aware, however, that if you want to do so as root you will have to allow root logins via SSH, which is itself dangerous.
If you must do this, at the very least use keys instead of passwords (see puttygen which is part of the full putty installation file).

And ideally you should disable root logins and instead create an additional user, then connect via WinSCP using that user and upload your files to that user's home directory. Then login via ssh as that user, su - root, and copy the files to the necessary location (being sure to then chown them to the correct user and not leaving them owned by root)

Or, if you have a static IP, it is "reasonably safe" to allow root logins (but still via a key not password) as long as you firewall port 22 to only allow logins from your IP (it is useful to have a backup static IP you can connect from in case your IP changes unexpectedly or your connection goes down temporarily)
 
Back
Top