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
Regression? Host listening on :2015 with tls defined #651
Comments
Kindly share the Caddyfile. You can mask hostnames or other private values. |
Here is config, output from caddy start up is below. The www. redir possibly is browser cache i never get anything in the caddy logs for the redir even if i add log/errors but i didn't bother to check dev tools in browser.
Output from caddy startup
|
Talked with @abiosoft on gitter. I forcibly defined I'll leave it up to maintainers to do what they wish with this issue. Though I will say the host definition / port / tls option logic can be a little confusing. maybe related to #384 |
I thought Caddy doesn't do automatic http -> https handling/redirect when you specify your own tls certificates, that's only applicable when it is auto. @zacheryph's Caddyfile looks like this.
So I was a bit surprised when he said it's been working pre 0.8.2. |
This is working as expected; Caddy does not enable automatic HTTPS when you bring your own certificates; thus you have to set the port yourself. Caddy treats this as kind of a "manual" mode. |
May I ask for the decision to be reconsidered? It's very surprising to change something as trivial as the certificate and seeing the port change. Principle of least surprise and all that. |
@FiloSottile Yeah, I'm looking into this with 0.9. Automatic HTTPS has lots of moving parts to make it work, and it's difficult to define which parts belong to "managed TLS" and which parts belong to "TLS" in general. I'm thinking that enabling TLS -- no matter where the certificates come from -- should still set up the redirection and port just like with fully managed TLS. |
I have a caddy server with a few domains on it. Two of them use Lets Encrypt, one is using certs (until they expire and I can use lets encrypt on it.) This host has
tls certfile.pem keyfile.pem
. Caddy v0.8.1 starts up fine with this host listening on:80
and:443
. However when I upgraded to v0.8.2 this host is listening on:2015
. I did not change myCaddyfile
at all.The text was updated successfully, but these errors were encountered: