# 'Bouncing' no route to host

**URL:** <https://forums.suse.com/t/bouncing-no-route-to-host/9668>\
**Category:** Rancher 1.x\
**Created:** [March 2, 2018, 9:02am UTC](https://forums.suse.com/t/bouncing-no-route-to-host/9668 "2018-03-02T09:02:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vs.eric](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vs.eric/32/3254_2.png) [@vs.eric](https://forums.suse.com/u/vs.eric)\
**Post date:** [March 2, 2018, 9:02am UTC](https://forums.suse.com/t/bouncing-no-route-to-host/9668/1 "2018-03-02T09:02:49Z")

</div>

Hi,

Rancher 1.6.14 with Kubernetes 1.8.5 is displaying a very weird issue. When I want to connect to a pod to get the shell or view the logs, either through the Kubernetes dashboard or using kubectl, I get a ‘no route to host’. When I reboot the VM it’s fixed for all pods on that node, but the problem issue just moves to another host in the cluster. Feels like a rancher/k8s pod causing the issue. Anybody experienced this too?  
I really don’t want to give devs SSH access to all nodes just to get to their pods.

Kind regards,

Eric V.