A simple solution to a permissions problem in VestaCP open() public_html failed 13 Permission denied on a configuration with NGINX, PHP-FPM and without Apache. If it is not visible in the web interface, search in doman.tld.error.log.

I'm not necessarily a fan of VestaCP, but if you have a little idea how to configure it NGINX, PHP-FPM Fri Linux and especially the email system, is a good alternative to cPanel. And especially since VestaCP is free and much more flexible.

If you are a novice in configuring web servers, I advise you better NOT to use VestaCP. It has a lot of bugs, it is updated quite rarely (and often big errors appear after the update) and many security problems need to be solved. There are even problems with the destruction of web folders and files in the default installation.

open() /home/user/web/domain_tld/public_html/" failed (13: Permission denied)

How to solve the error VestaCP open() public_html failed 13 Permission denied

CAREFUL! If you have a CMS installed that requires special permissions for some directories and/or files, the commands below will change them all.

Change the permissions of all directories and files in /home/user/web/domain_tld And you set chmod 644 for files and chmod 755 for directories.

• How To Fix nginx: [warn] the “ssl” directive is deprecated (Nginx / VestaCP)
• How to enable TLSv1.3 on NGINX. UpdateCP on CentOS with OpenSSL
• Destination Folder Access Denied [Windows Vista]

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;

User:group will also change if the correct ones are not set.

chown -R user:group *

At the end, check both the operation of the website and domain_tld.error.log.