# Checking runner ip connectivity... FAILED **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [January 19, 2020, 5:26pm UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634 "2020-01-19T17:26:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![sasikumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sasikumar/32/121815_2.png) [@sasikumar](https://discuss.elastic.co/u/sasikumar)\ **Post date:** [January 19, 2020, 5:26pm UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634/1 "2020-01-19T17:26:17Z")
We have already ECE setup on environment and we are trying to add another to existing ECE setup. While installing ECE on the new host we are getting the below errors. **Can't connect $RUNNER\_HOST\_IP [xx.xx.xx.xx:22000]: Connection refused** Could any one help on this ? Host Details: Operating System: RHEL 7 Docker Version :1.13 ECE Version:2.4.2 ---
**Author:** ![Jugsofbeer](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@Jugsofbeer](https://discuss.elastic.co/u/Jugsofbeer)\ **Post date:** [January 19, 2020, 9:55pm UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634/2 "2020-01-19T21:55:54Z")
Have you disabled the linux firewall and selinux ? Do you have IPv4 AND IPv6 enabled ? ---
**Author:** ![sasikumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sasikumar/32/121815_2.png) [@sasikumar](https://discuss.elastic.co/u/sasikumar)\ **Post date:** [January 20, 2020, 3:37am UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634/3 "2020-01-20T03:37:29Z")
Dear Ben, Yes we have disabled the firewall and selinux as well as we have enabled ipv4 & ipv6. Please note that we are able to ping and able to login via ssh using putty tool. Regards Sasikumar ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [January 21, 2020, 3:35pm UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634/4 "2020-01-21T15:35:20Z")
I believe this test works something like: - Spins up a docker container which binds to `host:22000` - From the install docker container (on the same host), attempts to connect to `host:22000` (the IP you've marked as `xx.xx.xx.xx` would be the IP of the host on which you're trying to install ECE if so, is that right?) So it still sounds like some docker config or (local) iptables or selinux issue. We don't do anything clever with networking, we just allow docker containers access to the host network. To reproduce outside of ECE, you could do something like: - First outside of docker use a tool like `nc` to check - Find some generic docker image that lets you run a command line, do the same `nc` test but with the server running in docker (or look for any config differences between the original host and this one, etc) ---
**Author:** ![sasikumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sasikumar/32/121815_2.png) [@sasikumar](https://discuss.elastic.co/u/sasikumar)\ **Post date:** [January 21, 2020, 4:47pm UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634/5 "2020-01-21T16:47:54Z")
Dear Alex, Thanks for the detailed information. Yes, xx.xx.xx.xx is pointing to host ip address. The major difference, existing ECE host docker version is 1.11 and the new host docker version 1.13. Our plan to docker upgrade(from 1.11 to 1.13) on new host and the move the instance from old host to new host. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 4, 2020, 4:48pm UTC](https://discuss.elastic.co/t/checking-runner-ip-connectivity-failed/215634/6 "2020-02-04T16:48:04Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.