java.net.SocketTimeoutException: connect timed out, while connecting from one webapp to the other.

Question

Hi,

I'm getting the following error while connecting from one azure webapp to other in my breakfix env "java.net.SocketTimeoutException: connect timed out". It was working correctly previously. And the same is working in my dev env.

I've tried tcpping command from one azure webapp to another in dev and it sent back a response. But when trying same in breakfix env, no response is received(seq time out). Is it the issue with webapp configuration. How to resolve it?

Answer 1

@VV, Srivatsha It sounds like you are experiencing connectivity issues between two Azure Web Apps. Can you try the below steps to see if they provide any relief? Please let us know the outcome.

1. Check the network security group (NSG) rules for both Web Apps to ensure that they allow traffic between each other. You can do this by going to the Azure portal, selecting the Web App, and then selecting Networking > Inbound port rules. Make sure that the NSG rules allow traffic on the appropriate ports for your application.
2. Check the firewall settings for both Web Apps to ensure that they allow traffic between each other. You can do this by going to the Azure portal, selecting the Web App, and then selecting Networking > Firewall. Make sure that the firewall settings allow traffic on the appropriate ports for your application.
3. Check the DNS settings for both Web Apps to ensure that they are resolving to the correct IP addresses. You can do this by using the nslookup command from a command prompt or terminal window. For example, if the hostname of the Web App is "mywebapp.azurewebsites.net", you can run the following command:

nslookup mywebapp.azurewebsites.net

Make sure that the IP address returned by the command is correct.

Check the application code to ensure that it is correctly configured to connect to the other Web App. Make sure that the hostname and port number are correct, and that any authentication credentials are correct.

Check the Azure Service Health dashboard to see if there are any known issues with the Azure Web Apps service in your region. If there are, you may need to wait for the issue to be resolved before you can connect to the other Web App.