fighting for truth, justice, and a kick-butt lotus notes experience.

midpoints LE4D 2.0 – some hints

 30 März 2018 12:31:29
On March, 28th, we released Let's Encrypt 4 Domino aka LE4D . If you are running LE4D v1.x, you must update to v2.0.

Certificate renewal will no longer work with v1.x because of some changes Let's Encrypt made on their Let’s Encrypt API endpoint.

If you are new to Let's Encrypt 4 Domino  you can get it here: https://www.midpoints.de/de-solutions-LE4D

Here are some additional hints to get v2.0 working:

Settings documents are disabled after design update to v2.0


In v2.0, we added a new feature to toggle the status of setings documents.

Image:midpoints LE4D 2.0 – some hints

All new settings are disabled by default. You have to enable them prior to run the agent.

Error: No trusted certificates found


You might see the following error message on the Domino console:
29.03.2018 08:21:39   Agent Manager: Agent  error: Caused by:
29.03.2018 08:21:39   Agent Manager: Agent  error: com.ibm.jsse2.util.h: No trusted certificate found

29.03.2018 08:21:39   Agent Manager: Agent  error:         at com.ibm.jsse2.util.g.a(g.java:21)

This happens most likely after you have applied a Domino FP or HF. In all cases we have seen, the cacerts is replaced with the default cacerts during FP/ HF install.

To fix this problem, you have to import the needed certificates again.

The certificates can be found here https://letsencrypt.org/certificates/

You should import the ISRG Root X1 CA and the two Intermediate certs:

ISRG Root X1 (self-signed)

    ◦        Let’s Encrypt Authority X3 (IdenTrust cross-signed)

    ◦        Let’s Encrypt Authority X3 (Signed by ISRG Root X1)


An “HowTo” about importing the certs can be found here:

http://abdata.ch/add-a-root-certificate-to-ibm-domino-jvm-keystore/


Error: Order’s status (“invalid”) was not pending


You might see the following error message on the Domino console:
28/03/2018 22:51:58   Agent Manager: Agent  error:         at lotus.domino.NotesThread.run(Unknown Source)
28/03/2018 22:51:58   Agent Manager: Agent printing: [ERROR] – Order’s status (“invalid”) was not pending

28/03/2018 22:51:58   Agent Manager: Agent printing: LE4D  – finished!

Due to the change in the underlying ACME protocol, Let’s Encrypt needs to re-validate the HTTP challenge on certificate renewal.
To do this, the challenge token must be accessible on the Domino server on port 80.

If you only have port 443 enabled or forward port 80 to 443, then the challenge will fail and you will see the error message.

Just for clarification. Port 80 is only needed for the first time challenge validation after the upgrade to LE4D v2.0. It is also needed, when you change the configuration and add a new host to the existing list of hostnames.

After the challenge has been validated, you can close port 80 again. It is not needed for certificate renewal.
Kommentare

1Michal Novacek  10.05.2018 10:40:03  midpoints LE4D 2.0 – some hints

Hi Detlev, I just upgraded LE4D and after running letsencrypt agent got an error message:

Agent printing: [ERROR] - Order's status ("invalid") is not acceptable for finalization

Agent Manager: Agent printing: LE4D - finished!

Port 80 is opened and Domino version is 9.0.1FP9HF139.

Any suggestions would be great.

Thank you

Michal

2scholle  12.06.2018 13:07:57  midpoints LE4D 2.0 – some hints

Hi,

ich habe dasselbe Problem:

Agent Manager: Agent error: org.shredzone.acme4j.exception.AcmeServerException: Order's status ("invalid") is not acceptable for finalization

Agent Manager: Agent error: at org.shredzone.acme4j.connector.DefaultConnection.throwAcmeException(DefaultConnection.java:431)

Agent Manager: Agent error: at org.shredzone.acme4j.connector.DefaultConnection.performRequest(DefaultConnection.java:359)

Agent Manager: Agent error: at org.shredzone.acme4j.connector.DefaultConnection.sendSignedRequest(DefaultConnection.java:174)

Agent Manager: Agent error: at org.shredzone.acme4j.connector.DefaultConnection.sendSignedRequest(DefaultConnection.java:154)

Agent Manager: Agent error: at org.shredzone.acme4j.Order.execute(Order.java:133)

Agent Manager: Agent error: at de.midpoints.le4d.manager.Le4dManager.downloadCertificate(Le4dManager.java:255)

Agent Manager: Agent error: at de.midpoints.le4d.manager.Le4dManager.orderCertificateUseHTTPChallenge(Le4dManager.java:207)

Agent Manager: Agent error: at de.midpoints.le4d.manager.Le4dManager.process(Le4dManager.java:132)

Agent Manager: Agent error: at de.midpoints.le4d.manager.Le4dManager.run(Le4dManager.java:97)

Agent Manager: Agent error: at de.midpoints.MPStarter.NotesMain(MPStarter.java:16)

Agent Manager: Agent error: at lotus.domino.AgentBase.runNotes(Unknown Source)

Agent Manager: Agent error: at lotus.domino.NotesThread.run(Unknown Source)

Agent Manager: Agent printing: [ERROR] - Order's status ("invalid") is not acceptable for finalization

Agent Manager: Agent printing: LE4D - finished!

AMgr: Agent 'letsencrypt' in 'le4d_v2.nsf' completed execution

domino linux v9.01 FP10

3scholle  12.06.2018 13:14:08  midpoints LE4D 2.0 – some hints

Bitte den Beitrag löschen,

ich Dummbart habe nicht gesehen dass der HTTP Server nicht lief!

Nachdem ich den Task gestartet habe lief auf le4d durch!

4Detlev Poettgen  12.06.2018 16:51:07  midpoints LE4D 2.0 – some hints

:-)

  •  
  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu

Archive