# Can't access gateway on CENTOS VM

**URL:** <https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185>\
**Category:** Ignition\
**Created:** [March 17, 2020, 11:30pm UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185 "2020-03-17T23:30:07Z")\
**Posts on this page:** 8\
**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:** [March 17, 2020, 11:30pm UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/1 "2020-03-17T23:30:07Z")

</div>

I’ve install the 7.9.13 GW on a CENTOS8 VM under VirtualBox. The ignition service is running under the root user, however doesn’t seem to be listening on tcp port 8088, so it’s not accessible.

I have the same setup under Ubuntu VM’s running fine. What should I be looking at?

Thanks!

---

<div class="post-metadata">

**Author:** ![chelton](https://avatars.discourse-cdn.com/v4/letter/c/e8c25b/32.png) [@chelton](https://forum.inductiveautomation.com/u/chelton)\
**Post date:** [March 18, 2020, 12:47am UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/2 "2020-03-18T00:47:31Z")

</div>

Not accessible by the Linux VM or by the host?  
Have you checked the port status?  
Try sudo netstat -tulpn | grep java and see if port 8088 is open  
or “ss -lntu” if netstat isn’t available.

---

<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:00am UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/3 "2020-03-18T01:00:14Z")

</div>

When I said it wasn’t listening on 8088, that was because a simple netstat -a showed nothing listening on 8088. However, taking your advice …

```auto
[bill@localhost ~]$ sudo netstat -tulpn | grep java
[sudo] password for bill:
tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN 1713/java
tcp6 0 0 :::8043 :::* LISTEN 1713/java
tcp6 0 0 127.0.0.1:45900 :::* LISTEN 1713/java
tcp6 0 0 :::8088 :::* LISTEN 1713/java
tcp6 0 0 :::8060 :::* LISTEN 1713/java
tcp6 0 0 127.0.0.1:4096 :::* LISTEN 1713/java
udp6 0 0 :::4445 :::* 1713/java

```

I see something listening on a tcp6 8088. So it turns out to be a FW issue …

```auto
[bill@localhost ~]$ sudo firewall-cmd --state
running
[bill@localhost ~]$ sudo systemctl stop firewalld
[bill@localhost ~]$ sudo systemctl disable firewalld
Removed /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.

```

… solves the problem.

Thanks!

---

<div class="post-metadata">

**Author:** ![chelton](https://avatars.discourse-cdn.com/v4/letter/c/e8c25b/32.png) [@chelton](https://forum.inductiveautomation.com/u/chelton)\
**Post date:** [March 18, 2020, 1:05am UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/4 "2020-03-18T01:05:04Z")

</div>

To open a port.  
sudo firewall-cmd --zone=public --permanent --add-port=8088/tcp  
firewall-cmd --reload

---

<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:11am UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/5 "2020-03-18T01:11:18Z")

</div>

a firewall in a devel vm seems unnecessary.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 18, 2020, 11:25am UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/6 "2020-03-18T11:25:42Z")

</div>

Disagree. I think development VMs should closely match the environment of the corresponding production gateway/VM. Including firewalls and other networking.

---

<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 19, 2020, 2:34pm UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/7 "2020-03-19T14:34:47Z")

</div>

I disagree more. It depends on the production environment. In my case, the production environment will have no VM.

In my case, my VM devel env is only used to manage several ongoing projects.

Sitting on my couch doing development on my laptop for some (offline) project, a FW is totally unnecessary. But if you want to use one on your couch, go for it.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 19, 2020, 4:45pm UTC](https://forum.inductiveautomation.com/t/cant-access-gateway-on-centos-vm/33185/8 "2020-03-19T16:45:32Z")

</div>

> [@wpmccormick](#):
>
> But if you want to use one on your couch, go for it.

Noted.