Problem with SSL Lets Encrypt & Roundcube in that place

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: lie.as

I ran this command: Lets Encrypt webmail.lie.as

It produced this output:
Could not issue an SSL/TLS certificate for webmail.lie.as
Details

Could not issue a Let’s Encrypt SSL/TLS certificate for webmail.lie.as .

The authorization token is not available at http://webmail.lie.as/.well-known/acme-challenge/42YkCEBO_1XigkfzbiEDXCcsuA-fozGGVQcw_9X1To4.
To resolve the issue, make sure that the token file can be downloaded via the above URL.
See the related Knowledge Base article for details.
Details

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/1674715365.

Details:

Type: urn:ietf:params:acme:error:unauthorized

Status: 403

Detail: Invalid response from https://webmail.lie.as/.well-known/acme-challenge/42YkCEBO_1XigkfzbiEDXCcsuA-fozGGVQcw_9X1To4 [95.168.169.207]: “\n\n404 Not Found\n\n

Not Found

\n<p”

My web server is (include version): Apache + Nginx

The operating system my web server runs on is (include version): Ubuntu 18.0.4

My hosting provider, if applicable, is: leaseweb.com

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
Plesk Obsedian

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

1 Like

Hi @unknys

what’s the client you use?

That’s not possible. Port 80 - only one webserver can answer.

Checking your subdomain there is a Plesk - https://check-your-website.server-daten.de/?q=webmail.lie.as

So I hope you use the internal Plesk client. Not Certbot or another client.

Port 80 - there is a nginx. So your vHost configuration may be buggy.

Is the subdomain defined in your Plesk?

1 Like

FYI: The way Plesk works: website served on Apache, then proxied by Nginx.

From Let’s Debug, this domain have an invalid CAA record that will prevent issuance.
https://letsdebug.net/webmail.lie.as/85454

It seems like you used a third-party DNS provider and not pointing your NS records to your lease web instance.
(That might allow you to use DNS validation)

Thank you

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.