• 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.
  • 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.

Issue Wordpress MU alias domains with Let's Encrypt - hit the error: Order cannot contain more than 100 DNS names

Matic_S

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.64_build1800241008.13 os_Ubuntu 22.04
Hello all

I am migrating from CWP (Control Web Panel) to Plesk.

I have a few Wordpress MU networks which has more then 100 domains each.
Now I have a problem that I can't issue a Let's Encrypt certificate with this error:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/new-order.
Details:
Type: urn:ietf:params:acme:error:malformed
Status: 400
Detail: Order cannot contain more than 100 DNS names


I would prefer to issue SSL certificate for each domain (as it was with CWP) but in Plesk you need to add each domain as an Alias.

Is there a way to "park" these domains as normal domains and set them a home directory for the main domain that has the network installed?
In this way I can issue a certificate for each domain which would be great.

Hoping to find a solution.

Thank you all
M
 
What you could try is to add domains as additional domains, sharing the same subscription/webspace instead of domain aliases, and then have all of those domains use the same document root (which you can adjust in the hosting settings).
 
Back
Top