• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Unable to install Let's Encrypt certificate for temporary domain

tuba-truba

New Pleskian
Server operating system version
CentOS 7
Plesk version and microupdate number
Plesk Obsidian Web Admin Edition 18.0.53 Update #1
I tried creating a temporary domain to setup a new site and got the following: sharp-alien.SERVER-IP.plesk.page
During setup I got an error message:

An issue occurred while securing the domain sharp-alien.SERVER-IP.plesk.page:

Could not issue a Let's Encrypt SSL/TLS certificate for sharp-alien.SERVER-IP.plesk.page.

The authorization token is not available at http://sharp-alien.SERVER-IP.plesk.page/.well-known/acme-challenge/55hi-dsadsadsadadsadsa.
To resolve the issue, make sure that the token file can be downloaded via the above URL.

The temporary domain is not accessible with the following error
NET::ERR_CERT_COMMON_NAME_INVALID
For some reason it the temporary domain is shown to have a certificate of one of my other domains.

The other domain is also on this server, has it's on (non-Let's Encrypt) cert, but I never had issues adding new domains before (temporary or otherwise).

Important thing to mention is that my plesk domain looks like this https://plesk.mydomain.com:8443/, and the certificate that's detected on the temporary domain belongs to mydomain.com

I tried disabling SSL/TLS support but got the same error. I'm essentially unable to access the temporary domain and that's why Let's Encrypt fails as well.

Anything obvious that I'm missing? Any help is appreciated and I can provide more info if needed.
 
Obviously the nameserver entry for the domain is missing. Can you try to create a new plesk.page-domain and see whether that is accessible?
 
Obviously the nameserver entry for the domain is missing. Can you try to create a new plesk.page-domain and see whether that is accessible?
I tried, but I still get the same result.

The page does get created, and there's a screenshot of the default Wordpress theme in Plesk dashboard. But after that it becomes inaccessible.
I really think it's because of the wrong SSL cert it gets assigned, but I don't know how it happens (it hasn't happened for other domains) and not sure how to fix it.
 
The "wrong SSL cert" is a result of the situation where no domain SSL cert can be assigned. In that case the fallback - the server certificate - is set. That is a symptom, not the cause. The cause is that for some reason the domain is not linked to a nameserver entry. Else you would be able to at least ping the domain using the domain name. In order to issue a domain-validated SSL certificate, the domain must be active and accessible through the internet on your server.

Is your server publicly on the Internet or are you behind a NAT router? Is the IP address in the temporary domain your public IP address or your local IP address behind your router?
 
Back
Top