Iis – How to enable incoming and outgoing world wide web traffic in IIS

asp.net-mvccloud-hostinggoogle-compute-engineiiswindows-server-2012-r2

Goal: Access website hosted on a remote cloud's IIS via web-browser.

Case: I wanted to open my IIS server (Windows server 2012 virtual machine hosted on Google compute engine) so that the website running locally on it becomes accessible via WWW.

As per EdSf's comment I need to make some firewall changes initially. So

I have enabled WWW firewall settings

But when I go to that Virtual machine's external IP address, the website is not loading.

Update: Tried allowing remote connections in IIS and I believe this opened IIS to WWW.

The binding config for the site looks like this:

I have enabled both 80 and 443 ports

Now it's running fine on SSL port 443 (except it lacks a SSL certificate). I am unable to access it through http port 80

As per Kamran's comment, I have checked the firewall rules and there seems to be the issue:

The http traffic doesn't seems to be allowed.

How do I change it?

Best Answer

courtesy

I'm writing this post to jot down all the things I need to do during cloudy ASP.NET website deployments.

Get the database connector
Re-Publish project
Grab that awesome URL rewrite module
Set IIS_IUSRS and app pool free
Check that your application pool refers to correct version of .NET
Get re-certified - obviously it's a new server, right?
Import and install certificate
Import the same in IIS

source

Related Solutions

Iis – Remote Desktop Gateway and HTTPS website on same server – possible

What I did eventually is encrypt and tunnel the RDP connections on both servers according to this guide (using Putty and Copssh). We log in to the internal machines by RDPing into them from within the Webserver itself (We understand the risk here).

I also wrote a batch file to automate the login procedure. The script will terminate automatically upon logging off from the internal machine. (note: the ping command delays the remote desktop menu, thus giving the user enough time to enter the SSH password):

start /b putty <user-account>@<ip-address> -L <local-ssh-port>:<ip-address>:3389
ping 123.45.67.89 -n 1 -w 12500 > nul
mstsc /v:localhost:<local-ssh-port> /f
taskkill /f /im putty.exe

IIS Powershell : Assign an existing SSL binding to a website

You get rid of the error by making a more specific binding. You currently have an SSL binding, on another website, bound to all IP addresses.

IIS 7.5 does not support SNI, so this is your only option. Without SNI you cannot have host name headers for SSL; you need one IP address per certificate.

I have enabled both 80 and 443 ports

Best Answer

Related Solutions

Iis – Remote Desktop Gateway and HTTPS website on same server – possible

IIS Powershell : Assign an existing SSL binding to a website

Related Topic