Issue Unable to create temporary domain and/or assign a SSL Certificate to domains *.plesk.page

[gruppoe-agle]

Server operating system version

Ubuntu 24.04.2 LTS

Plesk version and microupdate number

Plesk Obsidian v18.0.68_build1800250228.09 os_Ubuntu 24.04

Hello!

I've this problem:
I need to create a temporary domain in Plesk but the system returns a lot of times a "temporary error".
When I successfully create the temporary domain I receive this message:

Domain gracious-merkle.IP ADDRESS.plesk.page resolve problems detected:
The domain is not resolvable. To put your website online, correct DNS Settings

Also when i try to generate an SSL Certificate I receive this message:

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/2214856185/488570140766.
Details:
Type: urn:ietfarams:acme:error:dns
Status: 400
Detail: DNS problem: SERVFAIL looking up A for gracious-merkle.IP ADDRESS.plesk.page - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for gracious-merkle.95-211-246-224.plesk.page - the domain's nameservers may be malfunctioning

This problem rised yesterday and is present in the two Plesk server I use
* Plesk Obsidian Web Host Edition 18.0.68 <- UBUNTU ( as in tag)
* Plesk Obsidian Web Admin Edition 18.0.67 Aggiorna #3

 

[ddb_banio]

Hi - another one facing the same issue. It looks like none of the temporary domains previously created from the panel are working. We were offering this feature to our customers as it is in the panel, but now these sites are all down.

 

[Sebahat.hadzhi]

We are already aware of the issue and our team is actively working on fixing it. At this point, I cannot provide any ETA or a workaround apart from waiting. I would like to apologize for any possible inconvenience caused.

 

[Sebahat.hadzhi]

Just wanted to follow up and confirm that everything should be back to normal now. If you are still encountering any issues, please let us know.

 

[shago]

Hi, I have the same issue, suddenly all the temporary domains don't work for me.

 

[Sebahat.hadzhi]

At this point, there is no known issue with temporary domains. @shago , can you please provide some more details on the issue you are experiencing? Steps to reproduce and the exact error message you see will be great.

 

[JayJay69]

Hi support, I am getting this issue with temp domains

This is what I get when creating a new temp domain
Your temporary domain name
An unexpected error occurred.

This is what I get when trying to renew existing temp domains

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/2163840605/567222082446
Details:
Type: urn:ietfarams:acme:error:dns
Status: 400
Detail: DNS problem: SERVFAIL looking up A for cranky-torvalds.XX-XXX-XX-XX.plesk.page - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for cranky-torvalds.9XX-XXX-XX-XX.plesk.page - the domain's nameservers may be malfunctioning

Any help would be appreciated
Thanks

 

[Sebahat.hadzhi]

Hello, @JayJay69 . Could you please confirm if the error is still occurring? It could have been caused by a temporary connectivity issue.

 

[dam_troe]

Hi,

I’m facing the same issues.

Everything was working fine until Friday, 17.08.2025, when the errors started occurring.
Since then, it has not been possible to create SSL certificates for new temporary domains, and I’m getting the same error logs as mentioned above:

SSL/TLS-Zertifikat konnte für xxx.P-ADDRESS.plesk.page nicht ausgestellt werden.

Details:
Let's Encrypt-SSL/TLS-Zertifikat konnte nicht ausgestellt werden für xxx.P-ADDRESS.plesk.page.plesk.page.
Die Autorisierung dieser Domain ist fehlgeschlagen.

Details:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/481903560/570322124807
Type: urn:ietfarams:acme:error:dns
Status: 400
Detail: DNS problem: SERVFAIL looking up A for cranky-poitras.P-ADDRESS.plesk.page - the domain's nameservers may be malfunctioning
DNS problem: SERVFAIL looking up AAAA for cranky-poitras.P-ADDRESS.plesk.page - the domain's nameservers may be malfunctioning

The errors vary between missing NS records and missing A or AAAA records.
Interestingly, I was able to create a single SSL on Saturday afternoon, but before and after that only errors occurred.

Server support told me that temporary domains need to be older than one hour in order to create SSL certificates. However, this does not seem to matter — even after waiting 48 hours for a temporary domain, the issue persists.


Sometimes, even the creation of temporary domains fails with an error (“couldn’t create temp domain”), but usually this disappears again after a few attempts.

 

[tomjaycocks]

Hi,

I’m facing the same issues.

Everything was working fine until Friday, 17.08.2025, when the errors started occurring.
Since then, it has not been possible to create SSL certificates for new temporary domains, and I’m getting the same error logs as mentioned above:




The errors vary between missing NS records and missing A or AAAA records.
Interestingly, I was able to create a single SSL on Saturday afternoon, but before and after that only errors occurred.

Server support told me that temporary domains need to be older than one hour in order to create SSL certificates. However, this does not seem to matter — even after waiting 48 hours for a temporary domain, the issue persists.


Sometimes, even the creation of temporary domains fails with an error (“couldn’t create temp domain”), but usually this disappears again after a few attempts.

I have the exact same issue. On Friday I managed to get it to secure a temp domain but with a new package on the same server, it's back to the usual mixture of errors. None of my other servers have this issue, just my new one that was created last week (All servers are Alma9 with the exact same setup).