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

Production port should be 433 if using autocert for SSL certificate #35

Open
abishekmuthian opened this issue Jul 30, 2019 · 2 comments

Comments

@abishekmuthian
Copy link

By default production port is set to 80, it needs to be 443 as there's redirection from 80 to 443.

But in order for autocert's LetsEncrypt first verification to work, the redirection has to be handled by certManager's handler in the fragmenta server(fragmenta/server#8).

When that's done, calling StartRedirectAll is unnecessary as the above will do the same.

Perhaps, since gohackernews was using certificates in key to start with; it worked without the need for initial LetsEncrypt callback after autocert implementation thereby not facing this issue.

@pjebs
Copy link

pjebs commented Nov 3, 2020

How did you get it to work on port 443?

@abishekmuthian
Copy link
Author

@pjebs Please refer to this - fragmenta/server#8.

I used go http.ListenAndServe(":http", certManager.HTTPHandler(nil)) with production port 433, But as Kenny suggests use StartTLSAuto.

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