Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status No Plans to Implement
Workspace Nomad
Categories Nomad (Web)
Created by Guest
Created on Mar 14, 2023
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit DMA-I-363 Nomad Web to respond to LetsEncrypt requests on port 80 while also responding to Nomad Web requests on port 443.

Nomad Web to respond to LetsEncrypt requests on port 80 while also responding to Nomad Web requests on port 443 Merged

Environment: Nomad Web 1.0.6 is running on a Domino 12.0.2 server (no Safelinx). Domino uses one IP address and host name while Nomad Web uses another IP address and host name. Nomad Web uses the LetsEncrypt TLS certificate from certstore.nsf.

Customer created that certificate for the Nomad Web host name before installing Nomad Web when Domino's HTTP stack would respond to the Nomad Web IP and host name. Now that Nomad Web is installed, Domino is bound to its own IP and host name. The Nomad Web IP and host name is only answered by Nomad Web on port 443 as configured in the nomad-config.yml file. So now LetsEncrypt cannot renew the certificate because Nomad Web does not respond to verification requests on port 80.

There's a way to achieve this, but this is a bit complex which is by registering another Domino server and run two DPARs or else manually manage the TLS certificate. This is highly impacting the business of some of the clients especially because smaller companies would see a lot of value in Nomad if it was simple to install and leveraged LetsEncrypt.

  • Guest
    Mar 18, 2023

    It's really Domino HTTP which currently needs to respond to the ACME HTTPS-01 challenges.
    You can redirect port 80 to port 443 on this server or any other Domino server. Any Domino server in the same Domain can respond to the challenge.

    I understand that this a small environment and there is no other server. Plus you only want Nomad web to be exposed?
    We have no seen this use case before. But this sounds like an approach that could be implemented if the Nomad server would listen to port 80 and reply to the challenge, which is stored in certstore.nsf where Nomad today already reads the TLS credentials document.
    I don't know how big the bussines case is. But technically it would be possible that Nomad web could respond to the challenge.

    But if you need solution today, you could open port 80 only for ACME requests on the Domino side today.

    Daniel Nashed