The following forum(s) have migrated to Microsoft Q&A (Preview): Azure Virtual Machines!
Visit Microsoft Q&A (Preview) to post new questions.

Learn More

cannot open port 443 on Azure VM RRS feed

  • Question

  • I created one Azure VM (centos linux), and I can logon by using SSH through public ip. However I cannot connect with port 443 from outside of Azure though public ip.

    I opened port 443 by doing the folloing:

    added inbound rule in Network security Group), and open port in the firewall-cmd.

    What could be the reason??



    Friday, October 25, 2019 3:02 AM

All replies

  • Hello,

    Below are few suggestions for troubleshooting the issue.

    Please use this tool and see if 443 port is blocked on public IP of the VM.

    If it is blocked, then it could be NSG on subnets level that could be blocking the port.

    Check if there are any NSG's attached to the subnet where the VM is deployed (Example: In Network section when you select the VM, if the VM has NSG only attached to NIC, you should see something like "Impacts 0 subnets, 1 network interfaces").
    If there is NSG attached to subnet and NIC check the rules applied on the Subnet NSG.

    Also, ensure that the source port range is set to *.

    Please check these documentation for reference:

    Please let me know if this helped you solve your issue. Hope to hearing back on this.



    Disclaimer: This response contains a reference to a third party World Wide Web site. 

    Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.

    If the suggested answer helped you resolve the issue, do click on "Mark as Answer" and "Up-Vote" on the answer that helped you solve your issue for the benefit of the community.

    Friday, October 25, 2019 8:38 AM
  • Any update on this? 

    If the proposed answer was useful please remember to "Up-vote" and "Mark as Answer" to help the community easily find the solution. 

    Thursday, November 7, 2019 5:22 PM
  • I am having the same problem - I have tried the above and it isn't working for me either. I have the following inbound rule set up:

    Priority 350
    Port 443
    Protocol Any
    Source Any
    Destination Any
    Action Allow

    I have a network security group set up which contains the above rule and this is associated with the default subnet for the VM. 

    When I try to use the following command to see if the port is open and listening I get no response:
    sudo netstat -tulpn | grep :443

    likewise with:

    sudo ss -tulpn | grep 443

    Any help would be gratefully received.


    Wednesday, December 11, 2019 10:04 AM