Hi there is going to expire the let's encrypt certificate installed in the docker (linux / letsencrypt) you can help me renew it, thanks !!! maybe permanently !!
renew certificate let's encrypt
-
- OMV 4.x
- Stampey74
-
-
The docker container will automatically renew the certificate.
-
Hello,Your certificate (or certificates) for the names listed below will expire in 10 days (on 18 Oct 19 13:44 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors.We recommend renewing certificates automatically when they have a third of theirtotal lifetime left. For Let's Encrypt's current 90-day certificates, that meansrenewing 30 days before expiration. Seehttps://letsencrypt.org/docs/integration-guide/ for details.I received this email, which is why I worried, maybe I didn't set something up for the auto renewal.
-
-
I think you can ssh into your server and run certbot renew
-
root@OMVxxx:/var/log/letsencrypt# certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
root@OMVxxx:/var/log/letsencrypt# -
You have to check the logs in the config folder of the letsencrypt container
-
-
Where is it?
-
From CLI:
docker logs -f letsencryptor in the docker-gui of OMV: logs
-
I meant these logs: appdata/letsencrypt/log/letsencrypt/letsencrypt.log They show i a cert renew was attempted.
-
-
thank you all, the only thing that renewed me only for two months !!!
-
thank you all, the only thing that renewed me only for two months !!!
habitual renew date.
-
Hi all !
could you please help with renewal of the Let's Encrypt certificate ?
It's expired since yesterday, and It has not been renewed automatically
This is what I found into the log file from the config folder:cronjob running on Sat Sep 21 02:08:00 CEST 2019
Running certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/*********.duckdns.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert not yet due for renewal
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The following certs are not due for renewal yet:
/etc/letsencrypt/live/********.duckdns.org/fullchain.pem expires on 2019-12-13 (skipped)
No renewals were attempted.
No hooks were run.How to perform a manual renewal ?
Thanks
-
-
OK I found the way !
open a SSH to OMV and type the following commands:docker exec -it letsencrypt /bin/bash
certbot renewHave a nice day everybody !
-
Hi everyone, apologies to bring back this thread to active, but what if the docker container itself was not mapped to ports 443 and 80 but instead, as some guides suggest, to 444 and 81 with redirection? That was after following this guide that created a docker-compose file to use for installing MariaDB and NextCloud... I keep port 80 for http and the actual OMV WebUI.
So I successfully log inside the "letsencrypt" container but when I run certbot renew I get the following error (replaced my subdomain with XXXXX):
Code
Alles anzeigenroot@b4166551941a:/# certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/XXXXX.duckdns.org.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Plugins selected: Authenticator standalone, Installer None Renewing an existing certificate Performing the following challenges: http-01 challenge for XXXXX.duckdns.org Cleaning up challenges Attempting to renew cert (XXXXX.duckdns.org) from /etc/letsencrypt/renewal/XXXXX.duckdns.org.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/XXXXX.duckdns.org/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/XXXXX.duckdns.org/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I made sure my modem/router has again open port 80->81 whilst keeping 443->444 to OMV 4.x as usual; I can access NextCloud from outside just fine. But I am not sure if the error of Problem binding to port 80 refers to the external ports of Docker itself, eventually, and not OMV server?
I asked this question here too in the thread for Q&As regarding NextCloud, MariaDB and Let'sEncrypt installation. Thanks in advance for your tips/assistance/insight.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!