-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Traefik stopped serving on upgrade to v1.1.0-rc3 #807
Comments
@ShakataGaNai When you say
Can you give more details? Anything in the DEBUG logs? |
No pages loaded for any site over HTTPS, nor did it log any hits. The above log was everything with the one IPv6 hit at the bottom of the log was an attempt over HTTP (which is 302'd over to HTTPS per the traefik.toml config). I could roll forward again and try something else, if you have a suggestion for getting better diagnostics out of this. |
@ShakataGaNai Could you provide all your DEBUG logs (I don't see any frontend created in provided logs)? |
I experencied the same thing on CoreOs + Kubernetes. I will try to give you some logs later on. |
Just tried |
I found the issue. Fix is coming. |
Fixed by #814. Could you test using Docker image |
Hello,
The certificate is still valid but must be renewed i guess. It would be better if traefik respond to https request even with an expired certificate or if the renewal failed :) |
@osixia thanks for testing. |
Sorry it seems ok, litle caching pb 😳 |
Hey @osixia, great that you're issue is solved. Therefore, I gonna close that issue for now :) |
I just got the same errors when trying to upgrade from 1.0.3 to 1.1.0.. Lot's of |
@thomasf your issue(s) seems not linked with this closed issue. Can you open a new one providing more info? |
ok |
I was getting tired of all the LetsEncrypt renewal reminder emails and I saw the issues had been resolved in the latest, so I figured I'd give the latest RC a try (via DockerHub). I shutdown & removed the old traefik, pulled & launched the latest version and it didn't serve any traffic. The healthpage worked and I think HTTP traffic worked, but TLS based traffic did not (which is 100% of what I use).
Here's the logs from starting the container. The truncated section in the middle is where its reading out all the docker configs.
Also attached is my traefik.toml
As I was testing in production, I rolled back to latest release (1.0.3) and the system ran fine again.
The text was updated successfully, but these errors were encountered: