Domain shows 403 error after using Move Domain feature: Forbidden You don't have

[Suhitha]

Question: Domain shows 403 error after using Move Domain feature: Forbidden You don't have permission to access / on this server.


Applicable to:

• Plesk for Linux

Symptoms

• Domain example2.com shows the following error message after moving it to another subscription (example.com) in Domains > example2.com > Move Domain:

Code Select Expand

403 Forbidden
You don't have permission to access / on this server.
Server unable to read htaccess file, denying access to be safe

• The following error appears in Domains > example2.com > Logs:

Code Select Expand

[core:crit] (13)Permission denied: AH00529:/var/www/vhosts/example.com/example2.com/httpdocs/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/var/www/vhosts/example.com/example2.com/httpdocs/' is executable, referer: https://example2.com/

• Repairing permissions for example2.com shows:

Code Select Expand

There is incorrect ownership on some items in the WWW root directory of the domain 'example2.com' ........................................... [ERROR]
- Incorrect group of /var/www/vhosts/example.com/example2.com/httpdocs:
expected is psaserv (1002), actual is psacln (1003)


• The ownership of the httpdocs folder got changed after moving:

Code Select Expand

# ls -ld /var/www/vhosts/example.com/example2.com/httpdocs/
drwxr-x--- 2 user psacln 4096 Sep 2 09:16 /var/www/vhosts/example.com/example2.com/httpdocs/
Note: The psaserv group is expected instead of psacln.


Cause

Product issue:

• #PPPM-12251 "Moving the main domain of a subscription to a different subscription now sets the correct ownership of the domainâ��s document root directory."

Fixed in:

•   Plesk Obsidian 18.0.31 27 October 2020 (Linux)

Resolution

Please consider updating your server:

• How to install Plesk updates

Workaround

If update is not possible for some reason you may try the following

                      workaround

As a workaround until the bug is fixed, repair permissions:

1.Connect to the server via SSH

2.Execute the following command for the affected domain:

Code Select Expand

# plesk repair fs example2.com -y