certeraio
commented
3 years ago Hi @anestevemo
This is similar to some discussions going on here: https://github.com/certera-io/certera/issues/15
The issue is that port 80 is needed due to how things currently work. The certificate for your Certera instance uses HTTP-01 validation, which requires port 80 as that's the only thing that Let's Encrypt can use predictably: https://letsencrypt.org/docs/allow-port-80/
One thing I'm considering is changing how the Certera instance cert is obtained. One idea is to allow for the DNS configuration to be set before starting Certera for the first time. If the config is in place, it'll use DNS-01 validation instead of HTTP-01.
In the meanwhile, a work-around is to use a dedicated machine for your Certera instance where port 80 is available, instead of sharing it with another resource. It's best practice to have the Certera instance on its own for security and many other reasons.
I'm trying to install Certera in a produccion server in order to manage our Let's Encrypt certificites but I'm facing an issue at the installation progress:
System.IO.IOException: Failed to bind to address http://[::]:80: address already in use. ---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use
Our 80 port is already in use by a webservice, due to this reason, I tried to change default port 80 without success...
I figure out where to make thoose changes but I don't know how to compile the code after the modifications. Is there any way to compile the source code? Something like "Config / make / make install".
Kind regards, Antoni.