• 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 Default Site Set to None, Getting 503 Error

BBJohn

New Pleskian
Hi Everyone,

We are trying to use LetsEncrypt certificates to protect the Plesk IP/Hostname. We have done this successfully on most of our servers but are having an issue with one where we can't access the default site when it is set to None. We get a 503 error when browsing to the IP, so the letsencrypt validation isn't working.

I can't find where the logs are for the default site, there is no /var/www/vhosts/default/log folder, and tailing the access_log and error_log in /var/log/apache2 and /var/log/nginx don't show me anything.

Any thoughts on what to check?

Thanks
 
Well, as it always happens, I figured something out after I posted for help. :)

There were some weird symlinks in /etc/apache2/plesk.conf.d/ip_default, i cleaned that up and things are working right for the default site being set to none now.
 
Back
Top