Kubernetes problem after generating ACME Certificate

[henne]

Hi,

I have created an ACME certificate to be able to use the reporting and using SSL, as without I had mixed content using http behind a reverse proxy doing https.

But after a reboot kubernetes is not working anymore. In Apps I get a spinning wheel and this error in Running Jobs:

Code:

Error: Cannot connect to host 127.0.0.1:6443 ssl:default [Connect call failed ('127.0.0.1', 6443)]

I cannot unset the pool or move it anymore, I guess the kubernetes file is using the old wrong certificate. How Can I fix this?

Cheers Chris

 

[truecharts]

This is interesting, we've never seen this among our many testers, saidly enough, so definately worth the report.

TrueNAS is generally considered to be an appliance, so even though you might be able to hack a fix in yourself, the best solution (during RC and BETA for sure) would be to directly file a bugreport on the iX Systems Jira and to be sure to attach a debug as well.

 

[henne]

I tried to move the pool, delete certificate and also tried k3 kubectl from command line. And not really done a change, all failed, after a third reboot, it is now working all good and stable.