• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Secure the plesk with SSL fails

S

Shorty

Basic Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Web Pro Edition
Hello I wanted to ensure Plesk with SSL and get the following error with the installation.

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/2283269066/49060115236.
Details:
Type: Urn: IETF: Params: Acme: Error: DNS
Status: 400
Detail: DNS Problem: Servfail Looking Up a for 43896-37639.PPH-Server.de-The Domain's Nameservers May Be Malfunctioning; No Valid aaaa Records Found for 43896-37639.PPH-Server.de

What do I have to do to fix that?
 
Do you have an IPv6 address assigned to your domain? Cause it looks like it's trying to find the IPv6 DNS entry which is failing.
 
Do you own PPH-Server.de? DNS domain ownership validation is required for wildcard Let's Encrypt SSL certificates. Plesk can issue wildcard Let's Encrypt certificates for domains that use the Plesk server nameservers.
Try issuing a certificate only for 43896-37639.PPH-Server.de.
 
Wie Sie auf dem Bildschirm sehen können, gibt es keine Wildcard-Auswahl und ja, ich habe dem Server eine IP6 und keine Domäne zugewiesen. Die Domänen haben eine IP4
 

Attachments

  • plesk ssl.jpg
    plesk ssl.jpg
    26.5 KB · Views: 6
43896-37639.pph-server.de doesn't resolve to an IP address. Thus you can't issue a Let's Encrypt for it.
Is that the correct address provided for your server?
 
43896-37639.pph-server.de heißt der Server. Ich greife über die IP-Adresse 4 xx.xx.xx.xx:8443 auf Plesk zu

Info: Ich gehe jetzt ins Bett; morgen muss ich arbeiten.
 
Unfortunately, 43896-37639.pph-server.de doesn't resolve to your server IP address. You won't be able to issue a Let's Encrypt certificate for it.

You can check with your hoster to fix the domain name, or you can use your own domain name.
 
You must log in or register to reply here.

Similar threads

G
Issue Unable to create temporary domain and/or assign a SSL Certificate to domains *.plesk.page
Replies
3
Views
300
Sebahat.hadzhi
Sebahat.hadzhi
T
Issue SSL certificate renewal under cloudflare
Replies
0
Views
542
theplaza
T
R
Issue Problems Issuing a Let's Encrypt Certificate
Replies
6
Views
691
Robin McDermott
R
M
Issue Wordpress MU alias domains with Let's Encrypt - hit the error: Order cannot contain more than 100 DNS names
Replies
1
Views
584
Kaspar
K
H
Issue Lets Encrypt Issue - Type: urn:ietf:params:acme:error:caa
Replies
2
Views
993
HerrMatze
H
Back
Top