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

ATENTIE! Daca aveti instalat un CMS care necesita permisiuni speciale pentru unele directoare si / sau fisiere, comenzile de mai jos le vor modifica pe toate.

Schimbi permisiunile tuturor directoarelor si fisierelor din /home/user/web/domain_tld And you set chmod 644 pentru fisiere si chmod 755 pentru directoare.

• How To Fix nginx: [warn] the “ssl” directive is deprecated (Nginx / VestaCP)
• Cum activam TLSv1.3 pe NGINX. VestaCP pe CentOS cu OpenSSL
• Destination Folder Access Denied [Windows Vista]

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

Se vor schimba si user:group daca nu sunt setate cele corecte.

chown -R user:group *

La final verificati atat functionarea website-ului cat si domain_tld.error.log.