You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use EncryptWeMust on our Azure service fabric cluster to expose https endpoints for our services.
At present, everything works perfectly, i.e. certificates are persisted on the key vault and HTTPS is enabled on our endpoint.
However, our service is exposing from port 9000 (https) and the same service also exposes port 80 (http) for letsencrypt communication. I believe this is for challenge validation.
My question is do we need to always expose port 80 or can that be moved to a different port?
Or can route port 9000 to port 80 as well?
The text was updated successfully, but these errors were encountered:
I am actually not sure. This library doesn't receive a lot of love anymore, since LettuceEncrypt kind of became the "winner" in terms of support and adoption.
We use EncryptWeMust on our Azure service fabric cluster to expose https endpoints for our services.
At present, everything works perfectly, i.e. certificates are persisted on the key vault and HTTPS is enabled on our endpoint.
However, our service is exposing from port 9000 (https) and the same service also exposes port 80 (http) for letsencrypt communication. I believe this is for challenge validation.
My question is do we need to always expose port 80 or can that be moved to a different port?
Or can route port 9000 to port 80 as well?
The text was updated successfully, but these errors were encountered: