We are working on our SharePoint 2013 Azure internal sites to make internet accessible. Here are the steps performed:
- Assigned a public IP and created DNS entry. Host name is getting resolved to public IP on performing nslookup.
- Extended the existing web application to internet zone and IIS web site is available for extended web application.
- Created CSR and successfully installed SSL certificate provided by the vendor. Binding has been also completed from IIS.
- AAM has been completed.
- Our WFE VMs have virtual IP and internal IP. Do I need to create a DNS entry for my domain which I am trying to access mapped to virtual IP of the server?
- I can see an load balanced HTTPS end point has been created on Azure Portal with protocol as TCP and 443 as both internal and external port but in Access Control List I can see action as "Deny". Do I need to change it to permit ?
- What we have done is we have added a DNS entry for our domain and IP mapped to one of the reserve IP address (not virtual IP of any of the WFE servers). Is this maybe the issue?
When I am trying to access SharePoint site from internet, I am not able to access and getting "Page cant be displayed" error.
We are not still not able to access the site on the internet. When we are doing a tracert to the host name, after some hops we are getting "Request Time Out".
On IE we are getting a "This page cant be displayed" error. From fiddler we are getting a "502:Connection Failed" error. I am not sure what and where could be the error.
Is any change is required at load balancer or IIS?