Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
DmitriyK
Basic Pleskian
The message came:
Unable to generate the web server configuration file on the host <site-audit.com.ua> because of the following errors:
Template_Exception: AH00526: Syntax error on line 9 of /etc/apache2/plesk.conf.d/server.conf:
DocumentRoot must be a directory
file: /opt/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
Please resolve the errors in web server configuration templates and generate the file again.
Unable to generate the web server configuration file on the host <site-audit.com.ua> because of the following errors:
Template_Exception: AH00526: Syntax error on line 9 of /etc/apache2/plesk.conf.d/server.conf:
DocumentRoot must be a directory
file: /opt/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
Please resolve the errors in web server configuration templates and generate the file again.
DmitriyK
Basic Pleskian
I understand that the mistake is not only for me Issue - Apache unable to start
If you can not play, can you give access to the server?
If you can not play, can you give access to the server?
This is a completely different case.
Have you checked that found directory (DocumentRoot) exists on a server? And why there are so many these directives? Have you tried to use
# plesk repair web
command?
You have found location of DocumentRoot with the command
# grep 'DocumentRoot' /etc/apache2/plesk.conf.d/server.conf
As I see on your screenshot it is /var/www/vhosts/default/htdocs
Now check that this directory exists on a server with
# ls -ld /var/www/vhosts/default/htdocs
What is the ouptut?
P.S. Please do not use any language except official forum language English. Thanks.
P.P.S. Please post text instead of screenshots. Thanks.
# grep 'DocumentRoot' /etc/apache2/plesk.conf.d/server.conf
As I see on your screenshot it is /var/www/vhosts/default/htdocs
Now check that this directory exists on a server with
# ls -ld /var/www/vhosts/default/htdocs
What is the ouptut?
P.S. Please do not use any language except official forum language English. Thanks.
P.P.S. Please post text instead of screenshots. Thanks.
DmitriyK
Basic Pleskian
Checking Plesk version .............................................. [OK]
Checking for custom configuration templates
Some custom configuration templates have been found. The custom
templates have higher priority than default templates in case of
configs generation.
Please check documentation for details:
https://docs.plesk.com/current/redirect.html?book=advanced-administration-guid e-linux&page=68693.htm[WARNING]
Checking for the JkWorkersFile directive in the Apache configuration [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for corrupted reference between IP collections and IP
addresses ........................................................... [OK]
Checking for links between APS applications and subscriptions ....... [OK]
Checking for the Zend extension declaraion in php.ini ............... [OK]
Check symbolic links for latest virtual host config files ........... [OK]
Checking for system users home directories consistency .............. [OK]
Checking for records with empty name field in the Configurations table[OK]
Checking for nginx ULIMIT value ..................................... [OK]
Checking for extra configurations in database not owned by any object [OK]
Repairing web server configuration
Reinstall SSL/TLS certificates and set the default certificate for all IP addr esses? [Y/n]
Checking for custom configuration templates
Some custom configuration templates have been found. The custom
templates have higher priority than default templates in case of
configs generation.
Please check documentation for details:
https://docs.plesk.com/current/redirect.html?book=advanced-administration-guid e-linux&page=68693.htm[WARNING]
Checking for the JkWorkersFile directive in the Apache configuration [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for corrupted reference between IP collections and IP
addresses ........................................................... [OK]
Checking for links between APS applications and subscriptions ....... [OK]
Checking for the Zend extension declaraion in php.ini ............... [OK]
Check symbolic links for latest virtual host config files ........... [OK]
Checking for system users home directories consistency .............. [OK]
Checking for records with empty name field in the Configurations table[OK]
Checking for nginx ULIMIT value ..................................... [OK]
Checking for extra configurations in database not owned by any object [OK]
Repairing web server configuration
Reinstall SSL/TLS certificates and set the default certificate for all IP addr esses? [Y/n]
DmitriyK
Basic Pleskian
404 error is not for "domain not found", but "resource not found" (e.g. a page, a file).
To catch all non-existent subdomains, create a subdomain with the wildard * character, for example *.mydomain.ru. Then place content into its home directory that returns the desired action, e.g. a PHP script that returns a 404 error code. Maybe you can simply choose to redirect the wildcard subdomain to an existing domain.
The question is a different topic. Maybe you can choose to create a separate thread for future add-on questions that have different topics.
To catch all non-existent subdomains, create a subdomain with the wildard * character, for example *.mydomain.ru. Then place content into its home directory that returns the desired action, e.g. a PHP script that returns a 404 error code. Maybe you can simply choose to redirect the wildcard subdomain to an existing domain.
The question is a different topic. Maybe you can choose to create a separate thread for future add-on questions that have different topics.
