# Ignition Gateway with docker connect to Kepware

**URL:** <https://forum.inductiveautomation.com/t/ignition-gateway-with-docker-connect-to-kepware/53090>\
**Category:** Ignition\
**Created:** [November 15, 2021, 6:49pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-with-docker-connect-to-kepware/53090 "2021-11-15T18:49:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [November 15, 2021, 7:00pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-with-docker-connect-to-kepware/53090/2 "2021-11-15T19:00:39Z")

</div>

You shouldn’t need to adjust the bind address for the OPC-UA Server within Ignition to make the outbound connections to KEPServerEx. For the endpoint URL, I’d use `host.docker.internal` (more info in the Docker Docs [here](https://docs.docker.com/desktop/windows/networking/#use-cases-and-workarounds), specifically the section: _I want to connect from a container to a service on the host_) to resolve to your host system. It looks like `192.168.1.95` is actually the IP address of your Ignition Gateway container, not the IP address of your host system.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-gateway-with-docker-connect-to-kepware/53090)._