rancher: Rancher UI gives 404 backend when using helm chart
What kind of request is this (question/bug/enhancement/feature request): BUG
Steps to reproduce (least amount of steps as possible):
any one of 3
`helm install rancher rancher-stable/rancher
–namespace cattle-system
–set hostname=rancher.mycompany.com
–set ingress.tls.source=secret
helm install rancher rancher-stable/rancher
–namespace cattle-system
–set hostname=rancher.mycompany.com
helm install rancher rancher-stable/rancher
–namespace cattle-system
–set hostname=rancher.mycompany.com
–set ingress.tls.source=letsEncrypt
–set letsEncrypt.email=myemail@mycompany.com `
Result: default backend - 404
Other details that may be helpful:
kubectl get ingress -n cattle-system
NAME HOSTS ADDRESS PORTS AGE
rancher rancher.mycompany.com ip_addr1,ip_addr2 80, 443 48m
Environment information
- Rancher version (
rancher/rancher/rancher/serverimage tag or shown bottom left in the UI): rancher server with helm/stable - Installation option (single install/HA): 2 node
Cluster information
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported):Hosted
- Machine type (cloud/VM/metal) and specifications (CPU/memory):metal
- Kubernetes version (use
kubectl version):
1.18
- Docker version (use
docker version):
19.03.5
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 23 (9 by maintainers)
Congrats to those for whom it is working. I still however has the same problem. Tried with own certificates and letsEncrypt but no go. This 3 node (VM) cluster was brought up with RKE. I tried the v2.4.3-rc4 and the latest but no go. Tried the same syntax as the above who claim to have this version working. When checked the logs for the pods all seems normal except few lines of
2020/05/08 15:23:18 [INFO] Adding peer wss://10.42.2.9/v3/connect, 10.42.2.9 2020/05/08 15:23:18 [ERROR] Failed to connect to peer wss://10.42.2.9/v3/connect [local ID=10.42.1.6]: websocket: bad handshake 2020/05/08 15:23:23 [ERROR] Failed to connect to peer wss://10.42.2.9/v3/connect [local ID=10.42.1.6]: websocket: bad handshakeOur plan was to use rancher across the company to create and manage all our k8s clusters and apps in them, later keep adding VMs to this rancher cluster itself if needed but our hope seems to have met a roadblock. Currently we are going to use RKE for building k8s. We will retain this k8s cluster dedicated only to rancher. May be in future we find a version which just works as per the docs and then we will use it and think of adopting across the departments.I am having the same issue on both rancher-latest/rancher & rancher-stable/rancher when trying to generate the lets encrypt cert
404 page rendered on at the acme challenge
Is there any work-around?
Rancher Deployed on Ubuntu 18.04/k3s/master hosts as VM’s running on vSphere 6.7
Running self signed of course works.