https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-setup
a
This message was deleted.
m
Your instance has to solve an ACME challenge for certificates to be issued. If your instance is not publicly reachable this is a bit more complicated. You could use self-signed certificates or manually generated certs. If you still want to use Let's Encrypt, have a look into the documentation: https://cert-manager.io/docs/configuration/acme/#solving-challenges
f
It is public facing rancher.guardner.zip
But it fails to solve its stuck on pending state
I tried to do so in an other container it works in the same ingress but with rancher not
The url key is publicly accessible
m
Might be a routing issue. I was unable to route the IP address behind rancher.guardner.zip from serveral of my systems at different cloud providers.
f
It was down for 40 min due to some issues with the internet provider it will be back online in minutes
followed the guide in https://cert-manager.io/docs/troubleshooting/acme/ but im still getting this
fixed by this and by modifying the configmap values to rke2-coredns https://github.com/compumike/hairpin-proxy
Open in Slack
PreviousNext
Powered by