404 on setting up the GCE example.

[jackzampolin]

So I had this running with the default setup. It fetched the certs and was able to see the site up and running! Then I wanted to change some names and reorganize the files so I tore down the cluster and rebuilt it. I haven't been able to get it running a second time! I've gone ahead and created a gist with the appropriate files.

I tried some of the troubleshooting steps from #15 but was again unable to get the certs to authenticate.

Any help would be greatly appreciated @simonswine!

[simonswine]

@jackzampolin thanks for providing the yaml files, helps a lot. Everything looks fine, as even GCE recognises all the services as healthy:

{"k8s-be-31019--abb61364079302df":"HEALTHY","k8s-be-31137--abb61364079302df":"HEALTHY","k8s-be-31751--abb61364079302df":"HEALTHY"}

Can you test that for me:

• Is jackserver reachable as expected under http://jackzampolin.com/?
• Output of kubectl describe --namespace prodenv svc/kube-lego-gce

[jackzampolin]

@simonswine Can reach the server at http://*.jackzampolin.com.

Name:           kube-lego-gce
Namespace:      prodenv
Labels:         <none>
Selector:       <none>
Type:           NodePort
IP:         10.51.255.213
Port:           <unset> 8080/TCP
NodePort:       <unset> 31751/TCP
Endpoints:      10.48.1.6:8080
Session Affinity:   None
No events.

I'm now getting Too many certificates already issued for exact set of domains: jackzampolin.com,www.jackzampolin.com jackzampolin.com:acme which would indicate I have to wait for a week ☹️ and I have done everything right. I'll go ahead and close this unless the above output indicates something is amiss.

[johnparn]

@jackzampolin What did you do to make it work?

I have a similar issue, see #44. I got it working somewhat, then I made some minor changes and now I can only get one site to respond and without TLS.

[jackzampolin]

@johnparn I still haven't been able to make it work. SSL is more of a nice to have for my project (And I've used up my cert reqs this week 🙊) so I've put it on the back burner. I'm going to try the nginx example this week and see if the results are different.

[johnparn]

@jackzampolin Thanks! I'm eager to hear if nginx will work any better.

I've tried different ways of doing it. I have two sites that both needs SSL/TLS and I can get one site up running with a cert, however the second site I start will always return a default backend - 404. I've tried using the same namespace for all sites including kube-lego, separate namespace for all and putting kube-lego in the same namespace as each service. Still just one site will work.

Here are the files that I've used. https://gist.github.com/johnparn/ce0e025e8c015de812c0b84ef8b1faf9

[jackzampolin]

@johnparn So I tried the nginx version today and it worked great at first! Then it started creating/deleting the staticIP on the ingress. Opening an issue. womp