ThePCGeek
ThePCGeek
That may very well be something specific to your config/setup. I've tested it many many times with 0 issues. Re-tested just now with Debian 12 vm's for nodes and no...
its part of the repo. https://github.com/ChrisThePCGeek/k3s-ansible-traefik-rancher/blob/e60eb1e0886b79a06d81fd3d980a7e300f69ca60/ansible.cfg
Super old issue, closing as resolved
Yeah that's the idea I had, I think it would work to verify an email server was up and working. could even trigger a fail if the send doesn't work...
make sure your ingressroute is right with the correct annotations. it should be similar to this. ```yaml apiVersion: traefik.io/v1alpha1 kind: IngressRoute metadata: name: ext-dashboard annotations: kubernetes.io/ingress.class: traefik-external namespace: kube-system labels:...
thats my production one, the only difference is I have added TLS and removed the insecure http port. also I use my internal DNS to point to the external traefik...
No problem. at this level the OS it's on really doesn't matter. To be honest I don't know why its giving you an error. its definately getting to traefik because...
DNS is configured properly as well? such that traefik-ext points to the external IP for traefik and not the first one? in your case ending .181 from your vars file
just trying to see what could possibly be the cause, other thing I can think of is enabling the debug logs and then watching the logs from the rancher UI...