# Can't access Easytravel UI's - RHEL 7 VM on Azure (rules created for incoming traffic on ports 8079 and 8094)

**URL:** <https://community.dynatrace.com/t/cant-access-easytravel-uis-rhel-7-vm-on-azure-rules-created-for-incoming-traffic-on-ports-8079-and-8094/20788>\
**Category:** Cloud platforms\
**Tags:** azure, dynatrace-saas\
**Created:** [May 24, 2019, 2:07pm UTC](https://community.dynatrace.com/t/cant-access-easytravel-uis-rhel-7-vm-on-azure-rules-created-for-incoming-traffic-on-ports-8079-and-8094/20788 "2019-05-24T14:07:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattias\_wessma2](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mattias\_wessma2](https://community.dynatrace.com/u/mattias_wessma2)\
**Post date:** [May 24, 2019, 2:07pm UTC](https://community.dynatrace.com/t/cant-access-easytravel-uis-rhel-7-vm-on-azure-rules-created-for-incoming-traffic-on-ports-8079-and-8094/20788/1 "2019-05-24T14:07:50Z")

</div>

Created a RHEL 7 VM on Azure, allowed for incoming traffic at 8079, 8094, installed OneAgent, successfully connected to our saas-tenant and installed EasyTravel for Linux. EasyTravel starts fine and shows up in Dynatrace - and is instrumented fine. So far so good 🙂

My problem is that I can’t connect “externally” from using VM’s external IP and port 8079 and 8094. On my VM I see that it listens on port 8079 and 8094.

Any advice?

---

<div class="post-metadata">

**Author:** ![avdveen](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@avdveen](https://community.dynatrace.com/u/avdveen)\
**Post date:** [May 28, 2019, 1:22pm UTC](https://community.dynatrace.com/t/cant-access-easytravel-uis-rhel-7-vm-on-azure-rules-created-for-incoming-traffic-on-ports-8079-and-8094/20788/2 "2019-05-28T13:22:20Z")

</div>

Sounds like a firewall issue, either local (your machine), your LAN firewall/proxy not allowing the connection or some firewall config on Azure side that’s not set up correctly. If the ports are open, and the external IP is indeed correct, you should be able to connect if all firewalls between you and the VM is in fact open.

Have you tested access via e.g. curl command on the easyTravel VM, locally? Does that connection work?