search

ffMathy / FluffySpoon.AspNet.EncryptWeMust

MIT License
145 stars 30 forks source link

Do we need to open port 80 or can some other port be assigned #229

Open patolax opened 4 months ago

patolax commented 4 months ago

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?

ffMathy commented 4 months ago

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.

patolax commented 4 months ago

I thought this was the lib, quick look at LettuceEncrypt its in maintenance mode.