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.