Plesk : FTP error “home directory inaccessible”

Login to domain.com via FTP fails for all users. The following error message is displayed:

Cannot log in, home directory inaccessible

CAUSE

There could be several reasons:

1. This happens if the host name is longer than 15 symbols.

2. Domain resolves to a different IP then the one it has been configured for in Plesk.

3. FTP server configuration is broken.

RESOLUTION

1. To change the host name right-click the My Computer icon, choose Properties. Select Computer Name tab then click Change button. Specify the computer name as desired and click OK. When done, restart your computer.

2. Please check if domain.com resolves to the same IP it has been configured for in Plesk. You can use the following command :

nslookup yourdomain.com

The returned IP should be tha same as the one configured in Plesk for the domain.

3. If the name of your server is shorter than 15 symbols and domain resolves to the proper IP it could mean that something is broken in FTP configuration.

You should follow the steps below to fix the issue:

a. Repair permissions on home folders of problem domains. It can be done using the Control Panel:

Plesk , domains, mark problem domain, Click on Check permissions

b. Re-configure FTP configuration using Plesk command line tool ftpmng.exe as follows:

"%plesk_bin%\ftpmng.exe" --remove-vhost --vhost-name=yourdomain.com
"%plesk_bin%\ftpmng.exe" --reconfigure-vhost --vhost-name=yourdomain.com

c. If this issue happens to every domain you can repair FTP configuration for all domains using commands as below:

"%plesk_bin%\ftpmng.exe" --remove-all "%plesk_bin%\ftpmng.exe" --reconfigure-all

rndc: the key is invalid

Problem:

———
Issue:
———
While starting named, or when running /etc/rc.d/init.d/named status, you get the following error:
rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid.


Solution:

——-
Fix:
——-

Run rndc-confgen.
running rndc-confgen would ouput something like this:
# Start of rndc.conf
key “rndc-key” {
algorithm hmac-md5;
secret “lYzcmf255w8BC6PHTSYCQA==”;
};

options {
default-key “rndc-key”;
default-server 127.0.0.1;
default-port 953;
};
# End of rndc.conf

# Use with the following in named.conf, adjusting the allow list as needed:
# key “rndc-key” {
# algorithm hmac-md5;
# secret “lYzcmf255w8BC6PHTSYCQA==”;
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { “rndc-key”; };
# };
# End of named.conf

do as mentioned in the output, that is, copy the rndc.conf part to /etc/rndc.conf (of course, remove all the existing entries)
in /etc/named.conf, remove the existing key and controls section, and paste the one from the output of rndc-confgen.
restart named (/etc/rc.d/init.d/named restart).
This fixes the issue