Issue Can't issue SSL certificate!? Help!

[carlsson]

Server operating system version

Ubuntu 20.04.6 LTS

Plesk version and microupdate number

Obsidian Version 18.0.58 Update #2

Short story:
Wordpress site is located on another server.
Email is located on our server.
DNS is hosted by the registrar.
How can I install a Let's Encrypt certificate with the help of Plesk?

Long story:
I have a client that moved their site to another Wordpress service (Kinsta) because their home page designer wanted that.
They still have email on our server though.
The DNS is hosted by the registrar.

I started to get annoying "Can't issue certificate for the domain" emails.
So I looked into this, and it turns out that Kinsta is using the same subdomain as Let's Encrypt, ie "_acme-challenge" (why do they do that!?).
To solve it I was thinking to temporarily delete the Kinsta CNAME record, and create a Let's Encrypt certificate, but I get errors.

"Your domain in Plesk is hosted on the IP address(es): 123, but the DNS challenge used another IP: 456.​

​

Make sure that the IP address(es) specified in the domain's DNS zone match the IP address(es) the domain is hosted on."​

Furthemore, Plesk says that the Domain is not resolvable.
How can I get rid of that error?

​

What is the proper setup here?

Please help, I'm a little bit confused.

 

[Peter Debik]

This configuration is not possible yet. You can vote for the feature here: Issue Let's Encrypt Wildcard (and others) certificate without main domain in SAN (use DNS-01 challenge only)

 

[carlsson]

That explains it. Thanks!

Is it possibe to get rid of the annoying "Domain is not resolvable"? It doesn't seem to matter though, but it's nice to have a clean interface.

 

[Peter Debik]

When you have the DNS component installed on the system, the server believes that it is the responsible DNS server for the domain. You need to tell your server that it is only secondary to your external nameserver. Documentation: Plesk as a Secondary DNS Server
However, I am not sure whether this is right for you, because it might just be the case that this is not secondary but a superfluous installation of Bind when you are not using it anyway. In that case you could equally well remove your local DNS component.

 

[carlsson]

When you have the DNS component installed on the system, the server believes that it is the responsible DNS server for the domain. You need to tell your server that it is only secondary to your external nameserver. Documentation: Plesk as a Secondary DNS Server
However, I am not sure whether this is right for you, because it might just be the case that this is not secondary but a superfluous installation of Bind when you are not using it anyway. In that case you could equally well remove your local DNS component.

Thanks for the input Peter. However, I like to have the DNS component so I easily can copy the DKIM records. And maybe I want to use the server as a DNS in the future. Does it do any harm to have it installed?

This is the only case I have where the hosting is elsewhere, and some other strange problems have arised due to this.

 

[Peter Debik]

Does it do any harm to have it installed?

No, it just occupies some disk space and consumes some cpu time, but nothing major.