When I hit my k3s cluster with Traefik enabled, attempting to access the http resource returns a 404, but accessing it via https (thereby defaulting to 443) functions.
To be clear, what I mean is:
curl -k http://[myurl][well-known]
produces a 404, but
curl -k https://[myurl][well-known]
produces the token in the format:
[token]%
And Let's Encrypt is hitting my website fine, but 404ing on port 80 for this resource is stopping the certificate from being issued.
I'm using cert-manager and I'm trying to set up rancher, to be clear, but I'm a bit of a novice and learning, and I'm happy to provide any info that might help. This same problem comes up every time that I try to set up rancher via Let's Encrypt and I think it's a routing issue, but I'm not sure where to look or what to do to fix it.
If you offer me assistance, please assume I know very little.
Help would be appreciated and I'm happy to provide any additional information that might help.
As an update, I've manually created another certificate resource via a manually created ClusterIssuer, and it also has the same issue. I may try to swap to DNS challenges instead, but I would prefer HTTP.
I did, and I even deployed the example resource on a different domain on a different cluster at https://whoami.nauseatinglycute.com/ using the same firewall settings.
That worked, but I think there's a conflict between the ingress rancher creates and the ingress for Cert-Manager that Traefik creates and I'm not sure how to diagnose or solve that.
Based on the tutorial the only thing I can think to check would be the ingress.
I attempted to install Harbor and I am running into similar results with a properly configured issuer per the tutorial. I can provide additional information or the output of commands if it would help.