• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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