Facebook
TwitterHi,
One one of our domains I wanted to secure 60 domain aliases using the Plesk extension. However I forgot to uncheck the 'also secure www-' option. Thus resulting in a CSR containing 120 items instead of 60. This was rejected by Let's Encrypt as can be expected. The problem is now that even if I request an SSL for a single alias, Let's Encrypt returns the exact same error as before, 'The CSR contains more than 100 items'.
Can it be that the Plesk extension saves the state of the last CSR if the request fails? Way things are now, it is impossible to correct any error once the rate limit is exceeded.
The VPS has Plesk Let's Encrypt version 2.8.2-529 (Plesk Onyx)
One one of our domains I wanted to secure 60 domain aliases using the Plesk extension. However I forgot to uncheck the 'also secure www-' option. Thus resulting in a CSR containing 120 items instead of 60. This was rejected by Let's Encrypt as can be expected. The problem is now that even if I request an SSL for a single alias, Let's Encrypt returns the exact same error as before, 'The CSR contains more than 100 items'.
Can it be that the Plesk extension saves the state of the last CSR if the request fails? Way things are now, it is impossible to correct any error once the rate limit is exceeded.
The VPS has Plesk Let's Encrypt version 2.8.2-529 (Plesk Onyx)
Last edited:
