This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After configuring IIS on azure vm, I browsed default website locall and it is accessible. But when I tried to browse website outside of VM, it is not accessible throwinh HTTP error 401. I have read a lot of articles but those were old. I don't find any latest solution for VM with 2019 datacenter and latest IIS. I created a VM in amazon and without any issue it started working as VM got ready. I have spent more than 3 days to find solution.
Inbound rule for HTTP 80 is configured in NSG.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 82%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
Check IIS log to view if IIS received request and what the sub status code is. Compare the sub status code with this docs.
Check IIS if enable anonymous authentication and enable directory browsing.
If you have set firewall to allow outside request but still get this error, I think it's more likely that Amazon or Azure has some restrictions, and the first thing you need to check is whether the VM provider has some restrictions.
Hello @Mohammad Bin Qasim Niaz ,
In Azure VM, apart from configuring the NSG rule, you should also create a windows firewall rule to allow inbound TCP connections on the required port. Just RDP into your VM, open Windows Defender Firewall and add the rule.
Hi @Bruce Zhang-MSFT ,
I did check but found no issue. As well, anonymous authentication and directory browsing are enabled.
I just deleted vm and created new one which worked.
Hello @Prrudram-MSFT ,
I had created an inbound rule in Windows Defender Firewall, but it had not worked.
I just deleted vm and created new one which worked on new VM.
Great, @Mohammad Bin Qasim Niaz that the feature is working for you. Can you mark the response as an answer so that the community visitors can get benifited? Thanks
@Mohammad Bin Qasim Niaz ,
I can reproduce the error and able to fix the issue. I created a windows 2019 data center SKU with default values (and public IP). Then, when I tried to log into the machine, the IIS feature was not enabled by default, and I installed the feature. When I access the default website, I can browse the default IIS website.
I am not able to access the website from the outside. To make it work, I did open port 80 for HTTP access to the website via the internet. To do this, follow the below steps:
After these changes, I can browse the website from the outside.
I understand you did the same steps. Can you please confirm if a public IP is configured for the VM?
----------
(If the reply was helpful, please don't forget to upvote and accept as an answer, thank you)
Ravi Kanth
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 72%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
I am soooo not surprised. Microsoft is sh%ty again even in default setup of its software! The default website just DOESN'T work BY DEFAULT! Such primitive logic and yet no luck!
Instead, you just setup linux machine with basic Apache/Ngnix, and voila.
Maybe those are just signs to us: "guys, f%ck IIS, this is the 19th century, none uses it anymore, please go to linux with ngnix"!
The worst thing is that in case of "I just reinstalled my Virtual Machine", you just don't have any confidence it won't happen again, because you don't have clear understanding what caused the issue! "Well, there are some files corrupted!" Really? Maybe I should tell that to my customers: "Oh, you know, Microsoft is somewhere corrupted... you know?!"
Any default ngnix/apache setups just don't have that for the DEFAULT EMPTY websites!
Hi Boleslav
It is important to identify where the issue is in case the default website is inaccessible outside of the VM.
Like, previously suggested, the common blocker in this case is NSG rules, you need to allow inbound traffic on port 80 from the internet.
If that is already done and still there is an issue accessing the website from outside of the VM, it needs to be debugged from 2 aspects, one the IIS and two networking.
I recommend raising a support case with azure technical support for a deeper investigation.
I also recommend following the code of conduct for Microsoft Q&A being a user on this forum. Any kind of abuse in the Q&A community forum will result in your profile being banned from the community.
It has nothing to do neither with networking nor FireWall. It happens even locally on localhost! By default! When with other VM setup it works well, again, BY DEFAULT. That's why it's so frustrating!
This issue needs deeper investigation, Azure technical support team will be able to check and help on this. I would recommend you open an azure support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.
@RaviKanth-5629
Thanks for your prompt response.
I have done whatever you have pointed here. But when I browsed website publically, I get below error.
This page isn’t working
If the problem continues, contact the site owner.
HTTP ERROR 401
I don't understand what and where I should do changes to browse website publically. I have made public IP static.