Web Application deployed on VM took too long to respond.

Anubhuti Gupta 5 Reputation points
2023-02-08T06:11:28.0266667+00:00

I have successfully deployed a react web application through Windows WSL on my Azure VM. But after when I configured the DNS name, the link shows, "the site took too long to respond". I am able to access the website via the public IP address of the VM though.
How can I resolve the issue?
User's image

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,108 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jackson Martins 9,641 Reputation points MVP
    2023-02-08T07:11:07.9066667+00:00

    Hi @Anubhuti Gupta

    did you open the ports through the NSG? what about the windows firewall?

    If you have any antivirus, try to disable too

  2. vipullag-MSFT 24,106 Reputation points Microsoft Employee
    2023-02-27T11:13:33.15+00:00

    Hello @Anubhuti Gupta
    You have mentioned that the previous response provided by Jackson Martins was not helpful.

    You mentioned "I am able to access the website via the public IP address of the VM though." this means the ports is open and is accessible.

    Suggesting few more things that you can verify to see if that helps solve your error, The application gateway is unable to reach the backend server within the configured timeout period.
    -Check if there is a firewall in the way. If there is, you may be hitting the TCP timeout. Use the tcpping tool to test connectivity.
    -Check if DNS is accessible. Use the nameresolver tool to see if DNS is working. If it's not, you may have a firewall or Network Security Group (NSG) blocking access to DNS or it could be down.
    -Check if the FQDN of the backend has been entered correctly.
    -Verify the port configuration, Re-configure the DNS name once, verify that the DNS name is correctly configured and pointing to the correct IP address of the VM.
    -Check the Application Logs generated by your web application to see if there are any errors or issues that could be causing the problem.
    -Restart the application, few times restarting the application can resolve this issue.
    I also see another issue you have opened where you mentioned "and now the DNS name for my web application I deployed on the particular Virtual Machine, does not work"
    https://learn.microsoft.com/en-us/answers/questions/1168404/how-to-fix-add-an-inbound-network-security-group-r
    Are these issues related?

    0 comments