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

Environment: Nomad Web 1.0.6 is running on a Domino 12.0.2 server (no Safelinx) and 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 and 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 and 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.

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

There's a way to achieve this, but it's 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 specifically the smaller companies because they would see a lot of value in Nomad if it was simple to install and leveraged LetsEncrypt.

Attach files

Enter a subject

Admin

Timothy Clark

Reply
| May 4, 2023

With the information provided by Daniel, it seems that this would solve the problem. I'm going to place this idea in "No Plans to Implement". But if you still think it's needed, then please continue to vote for it.

0 reply Hide replies

Admin

Timothy Clark

Reply
| May 4, 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

0 reply Hide replies

2 MERGED