# Gateway is accressed on VirtualBox Host-Only Ethernet Adaptor

**URL:** <https://forum.inductiveautomation.com/t/gateway-is-accressed-on-virtualbox-host-only-ethernet-adaptor/32522>\
**Category:** Ignition\
**Created:** [February 23, 2020, 5:32pm UTC](https://forum.inductiveautomation.com/t/gateway-is-accressed-on-virtualbox-host-only-ethernet-adaptor/32522 "2020-02-23T17:32:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wpmccormick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/wpmccormick/32/13940_2.png) [@wpmccormick](https://forum.inductiveautomation.com/u/wpmccormick)\
**Post date:** [February 23, 2020, 5:32pm UTC](https://forum.inductiveautomation.com/t/gateway-is-accressed-on-virtualbox-host-only-ethernet-adaptor/32522/1 "2020-02-23T17:32:49Z")

</div>

I’m running an Ignition Gateway in Windows 10, where I also have VirtualBox setup. The VirtualBox configuration includes 2 VirtualBox Host-Only Ethernet Adapters, each with an IP on a different network than the Windows 10 machine. Regardless of whether or not I have a virtual machine running, the Ignition Gateway is accessible on port 8088 of each of the Host-Only IP’s, in addition to the host machine’s IP.

How do I stop Ignition from being accessible on the VBox Host-Only IP’s?

EDIT: Another way to ask this question is; How to control what interface the Gateway listens on?

Cheers!

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 24, 2020, 12:15pm UTC](https://forum.inductiveautomation.com/t/gateway-is-accressed-on-virtualbox-host-only-ethernet-adaptor/32522/2 "2020-02-24T12:15:39Z")

</div>

Assuming v8:

Networking → Web Server → Public HTTP Address

 ![2020-02-24_7-13-32](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/042153932de319aaf57599c58601f9a39b3b937c.png)

---

<div class="post-metadata">

**Author:** ![wpmccormick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/wpmccormick/32/13940_2.png) [@wpmccormick](https://forum.inductiveautomation.com/u/wpmccormick)\
**Post date:** [March 18, 2020, 1:43am UTC](https://forum.inductiveautomation.com/t/gateway-is-accressed-on-virtualbox-host-only-ethernet-adaptor/32522/3 "2020-03-18T01:43:18Z")

</div>

This issue really had more to do with the VM network config.

The default VB VM network config includes a single NAT interface, whic is good for getting out of the VM, but not back in. In order to get back in (i.e. access the gateway from the host), a 2nd Host-Only VirtualBox Adapter should be configured. Also, it works out well to enable the DHCP server in the Host Network Manager.