• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue File not found: example.org.conf

ahoi

Basic Pleskian
After upgrading to 18.0.37 I get this error when I check the Webserver's config


Code:
 {"id":1,"cmd":"plesk repair web -n","type":"progress","message":"Checking Plesk version","level":1} {"id":1,"cmd":"plesk repair web -n","type":"success","message":"Checking Plesk version","level":1} {"id":2,"cmd":"plesk repair web -n","type":"progress","message":"Checking for custom configuration templates","level":1} {"id":2,"cmd":"plesk repair web -n","type":"success","message":"Checking for custom configuration templates","level":1} {"id":3,"cmd":"plesk repair web -n","type":"progress","message":"Checking associations between domains and IP addresses","level":1} {"id":3,"cmd":"plesk repair web -n","type":"success","message":"Checking associations between domains and IP addresses","level":1} {"id":4,"cmd":"plesk repair web -n","type":"progress","message":"Checking for corrupted reference between IP collections and IP\naddresses","level":1} {"id":4,"cmd":"plesk repair web -n","type":"success","message":"Checking for corrupted reference between IP collections and IP\naddresses","level":1} {"id":5,"cmd":"plesk repair web -n","type":"progress","message":"Checking for links between APS applications and subscriptions","level":1} {"id":5,"cmd":"plesk repair web -n","type":"success","message":"Checking for links between APS applications and subscriptions","level":1} {"id":6,"cmd":"plesk repair web -n","type":"progress","message":"Checking for nginx ULIMIT value","level":1} {"id":6,"cmd":"plesk repair web -n","type":"success","message":"Checking for nginx ULIMIT value","level":1} {"id":7,"cmd":"plesk repair web -n","type":"progress","message":"Checking for extra configurations in database not owned by any object","level":1} {"id":7,"cmd":"plesk repair web -n","type":"success","message":"Checking for extra configurations in database not owned by any object","level":1} {"id":8,"cmd":"plesk repair web -n","type":"progress","message":"Checking the configuration of Apache modules","level":0} {"id":8,"cmd":"plesk repair web -n","type":"success","message":"Checking the configuration of Apache modules","level":0} {"id":9,"cmd":"plesk repair web -n","type":"progress","message":"Checking web server configuration. Please wait...","level":0} {"id":10,"cmd":"plesk repair web -n","type":"error","message":"File not found: example.org.conf","level":1} {"id":11,"cmd":"plesk repair web -n","type":"progress","message":"Checking the usage of PHP handlers","level":0} {"id":11,"cmd":"plesk repair web -n","type":"success","message":"Checking the usage of PHP handlers","level":0} {"id":12,"cmd":"plesk repair web -n","type":"progress","message":"Checking for obsolete PHP-FPM configuration files","level":0} {"id":12,"cmd":"plesk repair web -n","type":"success","message":"Checking for obsolete PHP-FPM configuration files","level":0}

Using plesk repair web example.org is succeeding - but a check just after this repair command fails again with the very same problem.

The files are existing btw:

Code:
/etc/apache2/plesk.conf.d/vhosts/example.org.conf
/etc/apache2/plesk.conf.d/vhosts/legacy.example.org.conf
/etc/apache2/plesk.conf.d/wildcards/example.org.conf
/etc/nginx/plesk.conf.d/vhosts/example.org.conf
/etc/nginx/plesk.conf.d/vhosts/legacy.example.org.conf
 
Back
Top