During Let's Encrypt certificates update cron task, Apache doesn't start in case a there is a certificate for wildcard domain. As a result, Plesk default page is shown instead of domain's content.
After the certificate renewal, the file
/etc/apache2/plesk.conf.d/ip_default/example.com.conf does not exist.
This issue is caused by a Let's Encrypt bug #EXTLETSENC-395 that will be fixed in the future Plesk updates.
Try avoiding use of Let's Encrypt certificates for wildcard domains.
Alternatively, the following workaround may be applied:
- Issue a Let's Encrypt certificate for main domain example.com in Domains > example.com > Let's Encrypt.
- Rename the issued certificate in Domains > example.com > SSL/TLS Certificates from 'Lets Encrypt example.com' to 'No renewable Lets Encrypt example.com', to exclude it from the renewal.
- Assign 'Not renewable Lets Encrypt example.com' certificate to wildcard subdomain '*.example.com' in Domains > *.example.com > SSL/TLS Certificates.
- Re-apply Apache and Nginx Settings in Domains > *.example.com > Apache & nginx Settings by pressing Ok or Apply buttons.
- Repeat the above steps every three months until the bug is fixed.