Hello! I am new to this, and I might find some help with my issue here. I've just deployed a k3s and within it I deployed rancher, it works fine if I use the local ingress rule, but when I try to use it externally, it just won't work. I am forwarding all port 80 traffic with a Cloudflare tunnel. My guess is that since rancher always tries to redirect to https, it will never be able to connect just through the http port. Is there a way to tell Rancher to just not redirect http traffic to https? Thanks!

Yeah it wants 443 because that's the only way to encrypt the traffic. Otherwise all your passwords and auth will fly over unencrypted.

I understand that, but I already encrypt all traffic through the Cloudflare tunnel, so really I don’t need to encrypt it again, is there a way to serve the web ui using http and not https? I tried setting tls as external updating it with helm, but no luck…

What does your rancher expose ingress look like?

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: rancher
  annotations:
    field.cattle.io/publicEndpoints: '[{"addresses":["192.168.31.155"],"port":80,"protocol":"HTTP","serviceName":"cattle-system:rancher","ingressName":"cattle-system:rancher","hostname":"192.168.31.155.nip.io","path":"/","allNodes":false},{"addresses":["192.168.31.155"],"port":443,"protocol":"HTTPS","serviceName":"cattle-system:rancher","ingressName":"cattle-system:rancher","hostname":"rancher.fire-pro.org","path":"/","allNodes":false}]'
    meta.helm.sh/release-name: rancher
    meta.helm.sh/release-namespace: cattle-system
    nginx.ingress.kubernetes.io/backend-protocol: HTTPS
    nginx.ingress.kubernetes.io/proxy-connect-timeout: '30'
    nginx.ingress.kubernetes.io/proxy-read-timeout: '1800'
    nginx.ingress.kubernetes.io/proxy-send-timeout: '1800'
    nginx.ingress.kubernetes.io/ssl-redirect: 'false'
    #  key: string
  creationTimestamp: '2025-10-06T22:36:48Z'
  generation: 26
  labels:
    app: rancher
    app.kubernetes.io/managed-by: Helm
    chart: rancher-2.12.2
    heritage: Helm
    release: rancher
    #  key: string
  namespace: cattle-system
  resourceVersion: '254684'
  uid: 7e6879d6-adec-44ff-9fbe-e4cac28c9d5b
  fields:
    - rancher
    - <none>
    - 192.168.31.155.nip.io
    - 192.168.31.155
    - 80, 443
    - 28h
spec:
  rules:
    - host: 192.168.31.155.nip.io
      http:
        paths:
          - backend:
              service:
                name: rancher
                port:
                  number: 80
            path: /
            pathType: ImplementationSpecific
      vKey: 707244775
    - host: xxxxxx      http:
        paths:
          - backend:
              service:
                name: rancher
                port:
                  number: 80
            path: /
            pathType: ImplementationSpecific
      vKey: 3013849366
#    - host: string
#      http:
#        paths:
#          - backend:
#              resource:
#                apiGroup: string
#                kind: string
#                name: string
#              service:
#                name: string
#                port:
#                  name: string
#                  number: int
#            path: string
#            pathType: string
  tls:
    - hosts:
        - rancher.fire-pro.org
#    - hosts:
#        - string
#      secretName: string
  backend:
    {}
#  defaultBackend:
#    resource:
#      apiGroup: string
#      kind: string
#      name: string
#    service:
#      name: string
#      port:
#        name: string
#        number: int
#  ingressClassName: string
__clone: true
cacheObject:
  useNestedBackendField: true
  showPathType: true

My internal local way to access it is via

<http://192.168.31.155.nip.io|192.168.31.155.nip.io>

and I want the external way to be

<http://rancher.fire-pro.org|rancher.fire-pro.org>

, I already set up the tunnel to redirect all traffic from

*.<http://fire-pro.org|fire-pro.org>

in the Cloudflare tunnel to

<http://localhost:80>

, and the DNS setup for the domain is done, I tried with a sample NGINX app, and it does work, the problem is with rancher itself

Yeah I was going to say that

``` tls:

- hosts:

- rancher.fire-pro.org```

is gonna force traffic to https/443