# How to fix 404?

**URL:** <https://forums.suse.com/t/how-to-fix-404/38387>\
**Category:** SUSE Rancher Prime\
**Created:** [July 6, 2022, 10:57pm UTC](https://forums.suse.com/t/how-to-fix-404/38387 "2022-07-06T22:57:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Herofa](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/herofa/32/9144_2.png) [@Herofa](https://forums.suse.com/u/Herofa)\
**Post date:** [July 6, 2022, 10:57pm UTC](https://forums.suse.com/t/how-to-fix-404/38387/1 "2022-07-06T22:57:40Z")

</div>

Hi everyone,

today I tried to set up k3s with rancher on my own bare metal server.  
I followed this tutorial: [Rancher Docs: Install/Upgrade Rancher on a Kubernetes Cluster](https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/)  
In addition to that, I have installed the nginx-ingress-controller and I have created a load balancer resource.

```auto
cattle-system service/rancher ClusterIP 10.43.252.143 <none> 80/TCP,443/TCP               
ingress-nginx service/ingress-nginx-controller-loadbalancer LoadBalancer 10.43.169.207 167.235.229.115 80:31905/TCP,443:31332/TCP

```

I confirmed that everything is working by creating a simple webserver-deployment and I could reach it via my configured domain.

Now I tried to install rancher and the installation went fine, but I can’t reach the dashboard (via rancher.mydomain.eu) as I’m getting a 404 error.

This is how the (helm) generated Ingress rule looks like:

```auto
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cert-manager.io/issuer: rancher
    cert-manager.io/issuer-kind: Issuer
    meta.helm.sh/release-name: rancher
    meta.helm.sh/release-namespace: cattle-system
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"
  labels:
    app: rancher
    app.kubernetes.io/managed-by: Helm
    chart: rancher-2.6.5
    heritage: Helm
    release: rancher
  name: rancher
  namespace: cattle-system
  resourceVersion: "3289"
  uid: 7de6d077-4a97-4df8-8051-6a47c5ea81a7
spec:
  rules:
  - host: rancher.mydomain.eu
    http:
      paths:
      - backend:
          service:
            name: rancher
            port:
              number: 80
        pathType: ImplementationSpecific
  tls:
  - hosts:
    - rancher.mydomain.eu
    secretName: tls-rancher-ingress

```

kubectl -n cattle-system get ingress -o wide

```auto
NAME CLASS HOSTS ADDRESS PORTS AGE
rancher <none> rancher.mydomain.eu 80, 443 24m

```

---

<div class="post-metadata">

**Author:** ![shlomi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/shlomi/32/9151_2.png) [@shlomi](https://forums.suse.com/u/shlomi)\
**Post date:** [July 7, 2022, 6:30am UTC](https://forums.suse.com/t/how-to-fix-404/38387/2 "2022-07-07T06:30:13Z")

</div>

Hi,  
can you provide the logs of rancher pods ?,  
And what kind of certificate did you use ?

---

<div class="post-metadata">

**Author:** ![sam30606](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/sam30606/32/10815_2.png) [@sam30606](https://forums.suse.com/u/sam30606)\
**Post date:** [December 26, 2023, 7:59am UTC](https://forums.suse.com/t/how-to-fix-404/38387/3 "2023-12-26T07:59:14Z")

</div>

After installation, the example Nginx Ingress YAML is displayed in the terminal. You can observe a line with `ingressClassName: nginx` , which is causing the issue of getting a 404 error when accessing Rancher.  
This is because, after installing Rancher, the Rancher Ingress YAML didn’t contains the entry `ingressClassName: nginx` .

```auto
spec:
  ingressClassName: nginx

```