This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ofbiz-tools.git
The following commit(s) were added to refs/heads/master by this push:
new 33c866e Copy from README.md Attic the "Letsencrypt certificate
update" part
33c866e is described below
commit 33c866ed2543553d7926cdca7a017642a5d08a53
Author: Jacques Le Roux <[email protected]>
AuthorDate: Tue Jul 29 16:02:03 2025 +0200
Copy from README.md Attic the "Letsencrypt certificate update" part
That has been useful today:
https://lists.apache.org/thread/8p4ml2lo9hqcj6fo56w1djrqpyomnkyw
---
demo-backup/ofbizdocker/README.md | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/demo-backup/ofbizdocker/README.md
b/demo-backup/ofbizdocker/README.md
index ff81973..f970d6f 100644
--- a/demo-backup/ofbizdocker/README.md
+++ b/demo-backup/ofbizdocker/README.md
@@ -52,3 +52,22 @@ A weekly cron job, /etc/cron.weekly/docker-system-prune,
runs the `docker system
## Viewing logs
For each demo instance (stable, next and trunk), the logs are respectively
accessible under /home/ofbizdocker/[demo-stable|demo-next|demo-trunk]/logs
+
+## Letsencrypt certificate update
+It was a time when every 3 months we needed to manually update our Letsencrypt
certificate. It was automated before, it's now again, so no worries. Anyway, if
necessary it's quite easy to do so. Simply connect to the demo VM and run
+
+ sudo certbot renew
+
+I got this message today (2020-04-17):
+
+ Processing /etc/letsencrypt/renewal/ofbiz-vm1.apache.org.conf
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
+ Cert not yet due for renewal
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
+ The following certs are not due for renewal yet:
+ /etc/letsencrypt/live/ofbiz-vm1.apache.org/fullchain.pem expires on
2020-06-08 (skipped)
+ No renewals were attempted.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
+
+and always since: it's OK. Nothing to do, it's automated. :)
+In case you get an issue, simply restart the VM and restart the demos. That
happened once: https://issues.apache.org/jira/browse/INFRA-23637
