-1

Dear All we want to use AZURE Application Gateway to implement SSL in front of our LINUX VM (hosting our node.js microservices).

As per current configuration:

-we have same resource group for both application gateway and linux VM.

-both are on the same virtual network but different subnets (as application gateway needs its own subnet).

-Without application gateway i can access my microservices without any issue.

Could somebody please suggest regarding how to establish a communication between application gateway and our microservices hosted on linux VM.

Gautam Malik
  • 146
  • 1
  • 9

1 Answers1

0

-Without application gateway i can access my microservices without any issue.

When your VM is added to a application gateway, it will not have an impact on the original access. Which your port is your service listening. You could check on linux VM.

netstat -ant|grep <port>

Please ensure your service is listening and you could access the service with curl <privateip>:<port>.

According to your description, I suggest you could add VM's nic to application in backend pool. Like below:

enter image description here

If your service is not listening on 80, you also need check application gateway HTTP setting.

More information please refer to this link.

Shui shengbao
  • 18,746
  • 3
  • 27
  • 45
  • as Lech Migdal said, you need open your service port on Azure NSG(Inbound rule). – Shui shengbao Aug 10 '17 at 07:58
  • Dear @walter we are listening on port 80, i have confirmed the same by using the netstat command as suggested by you tcp6 0 0 :::80 :::* LISTEN" – Gautam Malik Aug 10 '17 at 13:51
  • @GautamMalik Hi, does your VM have public IP, could you assess your service with Public IP address. Add application gateway does not affect it. – Shui shengbao Aug 11 '17 at 01:03
  • yes my VM has an public IP and i can access the micro-services using this public IP, i have searched further and found that if i have curled using the private IP of this VM i am not getting any response code between the range 200-399(as it requires authentication )....therefore i guess the reason may be that default health probe in application gateway consider this as "unhealthy" because when i used custom probe it gives me status unhealthy when using its private IP, could you please suggest if i need to add another router(path) in the node.js application hosted on linux VM. – Gautam Malik Aug 11 '17 at 08:27
  • Do you add a heath probe on application gateway? Do you try delete it and test again. – Shui shengbao Aug 11 '17 at 08:30
  • @GautamMalik Do you select VM or FQDN when you configuration backend pool. – Shui shengbao Aug 11 '17 at 08:30
  • @GautamMalik It seems your probe's configuration has some mistake. I suggest you could VM's nic as backend pool. For probe, please refer to this [link](https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-create-probe-portal). – Shui shengbao Aug 11 '17 at 08:35