Comments (7)
I fixed the JWS issue so ignore that part (I had to delete the kube-lego-account
secret when switching between staging and prod). Still a heads up about the 500s: apparently they are benign?
from kube-lego.
The 503 could come from multiple sources.
Please provide a bit more context:
- Which cloud you are running in?
- Can you reach nginx in general "http://foo.com/" should so the service from ingress?
- Can you verify the k8s services have endpoints assinged?
from kube-lego.
- GKE
- Yes, and SSL is configured and working
- Yes, nginx service has an external IP
from kube-lego.
I think it's normal that you see a couple of 503s before nginx actually routes the traffic to kube-lego. Can you provide a more detailed log?
from kube-lego.
Here's the log from startup up until it actually obtains the cert:
time="2016-06-06T13:07:44Z" level=info msg="kube-lego 0.0.2-4c1dd2c0 starting" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="connected to kubernetes api v1.2.4" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="start event watcher" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="server listening on http://:8080/" context=acme
time="2016-06-06T13:07:44Z" level=info msg="CREATE default/foo" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="Worker: begin processing true" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="ignoring as has no annotiation 'kubernetes.io/tls-acme'" context=ingress name=kube-lego namespace=default
time="2016-06-06T13:07:44Z" level=info msg="update challenge endpoint ingress, if needed" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="challenge endpoints don't need an update" context=ingress name=kube-lego namespace=default
time="2016-06-06T13:07:44Z" level=info msg="process certificates requests for ingresses" context=kubelego
time="2016-06-06T13:07:44Z" level=info msg="creating new secret" context=secret name=foo-tls namespace=default
time="2016-06-06T13:07:44Z" level=info msg="no cert associated with ingress" context="ingress_tls" name=foo namespace=default
time="2016-06-06T13:07:44Z" level=info msg="requesting certificate for foo.com" context="ingress_tls" name=foo namespace=default
time="2016-06-06T13:07:44Z" level=debug msg="testing reachablity of http://foo.com/.well-known/acme-challenge/_selftest" context=acme host=foo.com
time="2016-06-06T13:07:44Z" level=warning msg="wrong status code '503'" context=acme host=foo.com
time="2016-06-06T13:07:45Z" level=debug msg="testing reachablity of http://foo.com/.well-known/acme-challenge/_selftest" context=acme host=foo.com
time="2016-06-06T13:07:45Z" level=warning msg="wrong status code '503'" context=acme host=foo.com
time="2016-06-06T13:07:46Z" level=debug msg="testing reachablity of http://foo.com/.well-known/acme-challenge/_selftest" context=acme host=foo.com
time="2016-06-06T13:07:46Z" level=info msg="initialize lego acme connection" context=acme
time="2016-06-06T13:07:46Z" level=info msg="creating new secret" context=secret name=kube-lego-account namespace=default
2016/06/06 13:07:46 [INFO] acme: Registering account for [email protected]
time="2016-06-06T13:07:47Z" level=info msg="creating new secret" context=secret name=kube-lego-account namespace=default
2016/06/06 13:07:47 [INFO][foo.com] acme: Obtaining bundled SAN certificate
2016/06/06 13:07:47 [INFO][foo.com] acme: Trying to solve HTTP-01
time="2016-06-06T13:07:47Z" level=info msg="responding to challenge request" basePath="/.well-known/acme-challenge" context=acme host=foo.com token="fehKLcN4MKvX-2fgkCOmss9qzcq805wvXHws_shI8_Y"
2016/06/06 13:07:48 [INFO][foo.com] The server validated our request
2016/06/06 13:07:48 [INFO][foo.com] acme: Validations succeeded; requesting certificates
2016/06/06 13:07:49 [INFO] acme: Requesting issuer cert from https://acme-v01.api.letsencrypt.org/acme/issuer-cert
2016/06/06 13:07:49 [INFO][foo.com] Server responded with a certificate.
from kube-lego.
That's a completely normal output, I have just have to move the 503 output from level warn to debug/info.
The first self-test requests fail, because nginx reconfiguration takes some time. kube-lego is just retrying with an exponential back-off...
from kube-lego.
👍
from kube-lego.
Related Issues (20)
- The tls-sni challenge has been disabled due to strong credibility of a vulnerability report HOT 4
- Adding heptio/contour support HOT 1
- Wildcard Certificate Support HOT 2
- Pull the complete certificate chain HOT 1
- Unsupported ingress class HOT 1
- renewal expiry date is incorrect HOT 1
- Support for Letsencrypt wildcard certificate HOT 1
- Let's Encrypt Wildcard Support HOT 9
- How safe is it to use Kube Lego in producation on v1.9+ of Kubernetes? HOT 2
- If one of the domains in an ingress fails reachability, kube-lego should not try to authorize any of the domains
- Pod kube-lego not starting HOT 4
- read udp i/o timeout HOT 4
- Does not seem to work on k8s 1.8.8-gke.0 HOT 6
- Failed to list *v1beta1.Ingress HOT 1
- creating new secret
- Auto-renewal of certificates is not being triggered in 0.1.6 HOT 2
- Memory Leak?
- kubernetes 1.10 on GCP cant create a GCE loadbalancer ingress without secret
- Add: kubernetes.io/tls-acme: 'true' annotation
- Archive the kube-lego repository
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kube-lego.