Mail cert not creating

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:inwtx.net

I ran this command: root@myserver~# ./certbot-auto -d myserver.net -d www.myserver.net -d mail.myserver.net

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
NGINX configured with OpenSSL alternatives is not officiallysupported by Certbot.
Plugins selected: Authenticator nginx, Installer nginx
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for myserver.net
http-01 challenge for mail.myserver.net
http-01 challenge for www.myserver.net
Using default address 80 for authentication.
nginx: [error] invalid PID number “” in “/run/nginx.pid”
Waiting for verification…
Cleaning up challenges
Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/default
Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/default
Could not automatically find a matching server block for mail.myserver.net. Set the server_name directive to use the Nginx installer.

IMPORTANT NOTES:

  • Unable to install the certificate
  • Congratulations! Your certificate and chain have been saved at:
    /etc/letsencrypt/live/myserver.net/fullchain.pem
    Your key file has been saved at:
    /etc/letsencrypt/live/myserver.net/privkey.pem
    Your cert will expire on 2020-02-09. To obtain a new or tweaked
    version of this certificate in the future, simply run certbot-auto
    again with the “certonly” option. To non-interactively renew all
    of your certificates, run “certbot-auto renew”

My web server is (include version): nginx/1.6.2

The operating system my web server runs on is (include version):
Debian GNU/Linux 8.10 (jessie)
Linux 3.16.0-5-amd64 x86_64

My hosting provider, if applicable, is:

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): no

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


Not sure if mail cert was created and not sure what this means:

“Could not automatically find a matching server block for mail.myserver.net. Set the server_name directive to use the Nginx installer.”

Thanks

1 Like

Hi @ranch

please read your older topic - Problem with expired cert

Same situation - you have created the certificate - https://check-your-website.server-daten.de/?q=inwtx.net#ct-logs

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-11-11 2020-02-09 mail.inwtx.net - 1 entries duplicate nr. 1
Let's Encrypt Authority X3 2019-11-11 2020-02-09 inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries duplicate nr. 1

If you don't use a webserver with mail..., why do you want to install the certificate? So change your command -> certonly is enough. Or create a matching vHost. But checking your mail subdomain, there is the wrong certificate with two domain names and there is no mail port.

1 Like

I thought I had been through before, but I also thought the creation string I ended up using would fix the problem forever. This stuff is quite confusing to me.

1 Like

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