https://rancher.com/ logo
#general
Title
# general
f

famous-grass-8099

12/01/2022, 11:11 PM
Hello Rancher Team, I’m new to rancher and trying to setup v2.6 over single node with docker. I am having following errors. Appreciate If anyone can help. Here is how my setup is. single node docker image running behind nginx as reverse proxy (it is docker-compose.yml having both containers). That single node is behind AWS classic load balancer. following are the errors being logged by rancher node (docker-compose logs -f).
Copy code
rancher-server_1  | 2022/12/01 04:54:09 [ERROR] Failed to handle tunnel request from remote address 172.19.0.2:49716 (X-Forwarded-For: 44.230.106.196, 172.31.30.132): response 400: websocket: the client is not using the websocket protocol: 'websocket' token not found in 'Upgrade' header
rancher-server_1  | 2022/12/01 04:54:09 [ERROR] Failed to handle tunnel request from remote address 172.19.0.2:49716 (X-Forwarded-For: 44.230.106.196, 172.31.30.132): response 400: Error during upgrade for host [c-sxlgx]: websocket: the client is not using the websocket protocol: 'websocket' token not found in 'Upgrade' header
I have another AWS EKS cluster. I am trying to import in above rancher instance. It is showing
waiting
status.
c

creamy-pencil-82913

12/01/2022, 11:30 PM
don’t put it behind all that stuff. rancher wants to use websockets for both browser and downstream cluster connections and one or both of those things are breaking it.
also, the docker container is not supported for anything except for dev/proof-of-concept use. For anything approaching real world use you should be deploying the Rancher helm chart to a real Kubernetes cluster. K3s is good to use for that.
f

famous-grass-8099

12/01/2022, 11:44 PM
@creamy-pencil-82913 Thanks for your response. You are right, I observed websocket from browser and downstream. I’ll give it a try over eks.
14 Views