Filezilla will not connect to server using Secure File Transfer Protocol (SFTP)

Filezilla will not connect to server using Secure File Transfer Protocol (SFTP)


Filezilla is unable to connect to the server using the Secure File Transfer Protocol (SFTP), however regular file transfer protocol (FTP) works fine. Additionally, you have confirmed that the required ports for the Secure File Transfer Protocol have been enabled on the firewall. The generic port for SFTP is port 22 and the port for FTP is 21, port 20 may be required if the server is running the ftp services in passive mode.


  1. SSH into the server and edit the /etc/ssh/sshd_config file, if your config is in another location you can use the “locate sshd_config” to identify that location.
  2. Once in the file find the following commented out line: #Subsystem sftp /usr/lib/openssh/sftp-server Leave the line commented out, if its not commented, go ahead and comment it out using a hash tag (#).
  3. Below the commented out line add: Subsystem sftp internal-sftp  then reboot the server.
  4. Your Filezilla should now be able to connect.

Magento – Forbidden 403

Symptoms: When you attempt to browse to your Magento installation or Magento directory you receive a 403 Forbidden Error.

Solution: This is a normal web server response when the requesting user does not have the rights to access the content it is trying to access. To resolve this issue check the following information:

1. Check the owner of the folder for /httpdocs/ and all subdirectories for the magento installation. The correct owner should be as follows:  username:usergroup

In a Plesk 11.5 hosted environment this would be:  yourusername:psaserv

If the user is root (which often happens with command line installation) change the owner of the files in httpdocs or the subfolder with the magento installation using SSH and type:  chown -R yourusername:psaserv httpdocs/*

RSA server certificate CommonName (CN) `plesk’ does NOT match server name!?

Problem: RSA server certificate CommonName (CN) `plesk’ does NOT match server name!?

Solution: The RSA certificate is being referenced back to the server’s control panel, as such, the domain name doesn’t match the server name. Please note this message is harmless and can be ignored.


1. Under your Plesk Control Panel, go to Websites & Domains > Secure Your Sites > Add SSL Certificate

2. Name your certificate

3. Make sure the domain name matches your site, remove www.

4. Click Self-Signed, your SSL Certificate has now been generated. Please note, this is a self-signed unsecure certificate, do not use this for PCII.


1. Under your Plesk Control Panel, go to Websites & Domains, Click on Show Advanced Operations on the bottom of the screen.

2. Select Website Scripting and Security

3. Under Security, make sure Enable SSL Support is checked, in the pull down select the certificate you just created.

4. Click OK.

This should resolve the error message 🙂

Plesk: Test Directory located in /httpdocs/test/

Description:  In default Plesk Installations a folder called Test is created under httpdocs/  this folder contains a series of scripts designed to perform “hello world” type tests to confirm that those scripting languages can be used.

If the test scripts are no longer needed you can remove the directory

If you would like to keep the scripts but prevent access to them, you can either:

1. chmod the directories to 700 and files to 644; or

2. Move the test folder out of the httpdocs/ directory into a non-webaccessible directory for later use.