Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
patolax opened this issue Mar 15, 2024 · 2 comments
Open

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

patolax opened this issue Mar 15, 2024 · 2 comments

Comments

@patolax
Copy link
Contributor

patolax commented Mar 15, 2024

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
Copy link
Owner

ffMathy commented Mar 15, 2024

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
Copy link
Contributor Author

patolax commented Mar 17, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants