Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Issue Error 503 and User share
- Thread starter jojod
- Start date
-
- Tags
- plesk 18.0.38
Hello,
this behaivor sounds weird... could you share some log's to identify why some websites are showing 503?
"how do I re set the system user on the files?"
Try to reapair the file-system/permissions of the doc-root on the domain:
this behaivor sounds weird... could you share some log's to identify why some websites are showing 503?
"how do I re set the system user on the files?"
Try to reapair the file-system/permissions of the doc-root on the domain:
Bash:
plesk repair fs YOURDOMAIN.TLD -yHello,
In the logs of the domain where there is the error 503 we have:
AH01276: Cannot serve directory /var/www/vhosts/domain.ml/httpdocs/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm,index.shtml) found, and server-generated directory index forbidden by Options directive
I have tried to reapair the file-system/permissions but it did not find any errors.
Look, the system username is Jordan but the permissions of all files seem to be in the name of the user SHARE
In the logs of the domain where there is the error 503 we have:
AH01276: Cannot serve directory /var/www/vhosts/domain.ml/httpdocs/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm,index.shtml) found, and server-generated directory index forbidden by Options directive
I have tried to reapair the file-system/permissions but it did not find any errors.
Look, the system username is Jordan but the permissions of all files seem to be in the name of the user SHARE
Hello, @jojod as far as I understand there are 2 issues:
1. Incorrect ownership
it can be fixed recursively by execution of this commands:
2. for another domain you got 503 with the message in log about "No matching DirectoryIndex" it looks curious, because usually 403 error leads to provided snippet from logfiles. So anyway I suggest you try the solutions from these articles:
Cannot access a website directory in Plesk: 403 Forbidden and A domain in Plesk intermittently shows error 403 or 404: incorrect Document Root is parsed by the webserver
1. Incorrect ownership
it can be fixed recursively by execution of this commands:
# find /var/www/vhosts/example.com/httpdocs/ -type f -exec chown user_example:psacln {} \;
# find /var/www/vhosts/example.com/httpdocs/ -type d -exec chown user_example:psacln {} \; more details can be found here: How to restore default permissions in the virtual host directory on Linux?2. for another domain you got 503 with the message in log about "No matching DirectoryIndex" it looks curious, because usually 403 error leads to provided snippet from logfiles. So anyway I suggest you try the solutions from these articles:
Cannot access a website directory in Plesk: 403 Forbidden and A domain in Plesk intermittently shows error 403 or 404: incorrect Document Root is parsed by the webserver
You can just use chown -R user:group /di/re/cto/ry, no need to fiddle around with find.
This problem is solved the name of the index file was not the right one...
Please open a new threat for a new/different problem, this makes it much easier for people to find your problem and help you and even for people who search for the same problem too.
Kind regards,
