• 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.

Resolved Diagnostic and repair

JuanCar

Regular Pleskian
Server operating system version
Almalinux 9.4
Plesk version and microupdate number
Plesk Obsidian 18.0.69 #4
HI
When I launch the tool diagnostic and repair and check FTP&WEb servers i get an issue whit th message
file not found: adomain.com.conf
But the domain works fine and I see the domain.com.conf in

/etc/httpd/conf/plesk.conf.d/vhosts/domain.com.conf
/etc/httpd/conf/plesk.conf.d/wildcards/domain.com.conf
/etc/nginx/plesk.conf.d/vhosts/domain.com.conf
/opt/plesk/php/8.3/etc/php-fpm.d/domain.com.conf

I've modified some domain hosting properties to try Plesk rebuild necessary files, but the problem remains.
Every file has the right permissions.
How can I solve this issue?
 
Hello, @JuanCar . Is the repair utility unable to fix the reported "file not found" error? Can you please try running and let us know if the issue persists after that:

plesk repair web -y domain.com

Is there a wildcard subdomain added for domain.com by any chance? If it is, that could be a result of to a product bug (EXTPLESK-1056) in the Repair Kit extension.
 
Back
Top