# Ipsec tunnel not pingable when node and webui the same server **URL:** \ **Category:** Rancher 1.x\ **Created:** [November 2, 2018, 8:15am UTC](https://forums.suse.com/t/ipsec-tunnel-not-pingable-when-node-and-webui-the-same-server/12224 "2018-11-02T08:15:31Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nsweetman](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nsweetman](https://forums.suse.com/u/nsweetman)\ **Post date:** [November 2, 2018, 8:15am UTC](https://forums.suse.com/t/ipsec-tunnel-not-pingable-when-node-and-webui-the-same-server/12224/1 "2018-11-02T08:15:31Z")
I have a 5 server deployment. Host1 is running the Rancher Server as well as the Rancher/agent and other docker containers. Containers on the other hosts can ping the Host1, but cannot ping the IP address for ipsec IP on Host1. Containers on other Hosts can ping the ipsec IP on hosts that are not Host1 Host1 containers cannot ping ipsec IP of other hosts. There are no errors in the logs for Host1, ipsec and its sidekicks are all green. Rebooting host did not fix. Restarting ipsec did not fix. Rancher v1.6.23 running on latest CoreOS Stable. ---
**Author:** ![nsweetman](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nsweetman](https://forums.suse.com/u/nsweetman)\ **Post date:** [November 2, 2018, 8:39am UTC](https://forums.suse.com/t/ipsec-tunnel-not-pingable-when-node-and-webui-the-same-server/12224/2 "2018-11-02T08:39:54Z")
Turns out the issue was caused by the Rancher/Agent. Ranger/Agent was install specifying the IP address of the host as the Cattle\_Agent\_IP to ensure the server used the correct IP address, but it appears to have gone sideways after some containers were installed. Redeployed Rancher/Agent on the host, specifying the Host IP as the Cattle\_Agent\_IP and the ipsec for this host started working. credit:[http://forums.suse.com/t/node-disconected-ipsec-problem/9740](http://forums.suse.com/t/node-disconected-ipsec-problem/9740)