Unable to start debugging in VS2015 for Azure web app - azure

I'm using VS2015 Update 1 to try and debug my site which I've uploaded in Debug mode to an Azure web app (NOT a vm). I am working from my work domain.
I've been following instructions similar to found here https://samlman.wordpress.com/2015/02/27/another-cool-way-to-remotely-debug-azure-web-sites/
I have:
Published my website in Debug configuration
Enabled Remote Debugging from the management console
Made sure my VS edition is set to 2015
Enabled Websockets (from trying to connect via websockets)
Checked that the firewall allows VS remote debugger, remote debugger monitor and remote debugger discovery through.
Checked the website is up and running (set it to always on just in case)
I have tried right clicking my app service in Server Explorer and "Attach Debugger".
I then tried to connect using Debug > Attach to process and using the qualifier mysite.azurewebsites.net as instructed on various blogs. Even tried transport as Websocket, Remote as well as Default.
All methods get me the following:
I then used Fiddler to see if I could find the answer from web traffic but no joy with that.
Would appreciate any suggestions to get me around this problem!
Edit
Under scm -

There was another firewall I wasn't aware of on the domain that was blocking the debugger.
Edit:
Ports requested
outbound:
UDP 3702
TCP 4020
TCP 4021
Port assignments are given here on MSDN page

Related

After adding SSL to local IIS "Unable to start debugging on the Web server"

Visual Studio 2015 (Loaded as Admin), Web API 2, Windows 10.
I have Local IIS with a subdomain sub.mylocalsite.com mapped through the hosts file to 127.0.0.1. The Web API 2 is loading and I am able to debug and do all the activities as expected.
On IIS, if I add a secure binding, with the proper self-signed certificate (without disabling the non-secure binding, i.e. keeping two bindings) and do an IIS Reset, I am able to access the https Web APIs as expected, however, when I click run to start debugging I get the standard error from VS of Unable to Start Debugging.
Please note that I tried both setting the start URL as http://sub.mylocalsite.com and https://sub.mylocalsite.com to no avail
Any solution?
I experienced the same thing, then saw this blog post. Try attaching to worker process, per this blog post:
https://blogs.msdn.microsoft.com/vijaysk/2007/10/17/visual-studio-debugging-websites-that-require-client-certificates/
The most important requirement for the pretty F5 key to work in Visual Studio is NTLM/Windows Intergated Authentication. Only then can it auto-attach to the IIS worker process. And this is where our trouble starts. Client certificates is a kind of an authentication mechanism. When you configure a website to require client certificates you are changing the authentication mechanism.
So if you are developing a website off an IIS server and you need to debug it with client certificates then you cannot just open your web project in visual studio and start debugging it. But what you can do is attach to the process running your code manually.
Open your project in Visual Studio and set a breakpoint as you usually do
Debug menu > Attach to Process > Select the process running your code.

AWS working for IIS, but not for NodeJS on the same port

I am using AWS EC2 instance on Windows Server 2008 R2, I deployed an application in IIS on port 80. I am able to access it anywhere. The security group is as follows:
HTTP TCP 80 0.0.0.0/0
Then, I installed NodeJS for windows and deployed a simple node application to the same port. When I browse to localhost on the server I see my application working, but when i browse from a different pc, I cannot access it. How is it accessible from IIS but not from NodeJS?
I've seen this question on stackoverflow and the answer is ussually to set the TCP port in security groups in AWS cosole but I've already done that and it doesn't work. Any other ideas?
For those who are having the same issue, if you install nodejs you will need to change some windows firewall settings to expose the port:
Open Start Menu -> Administrative Tools -> Windows Firewall with Advanced Security
Click "Inbound Rules" from the left window
Click "New Rule..." in the Actions window on the right side
follow the prompts to customize the rule and be sure to add the port that your nodejs application is using. Make sure to name the rule so that you recognize it later
In the Inbound Rules window find and double click the rule you just created. Under Programs and Services, select "This Program:" and browse to your node.exe file.
Last but not least make sure this port is open in AWS console security group inbound rules too.

Configure IIS to access Deployed website globally (through WAN) [NOTE: I have static IP]

I am completely new bie to IIS.
I have a very basic knowledge about how to configure IIS.
Today I have a requirement to access website Globally through WAN (through internet from any PC all over world) which I have deployed in my Local IIS.
The website=> SilverLightBusinessApplicationWeb
which you can see in my below screen shot can be open in LAN nicely.
so I only looking for how to open it in WAN?
So anybody please suggest me a simple steps or instruction for it.
You can see two screen shot of Internet Information Service (IIS) Manager.
NOTE: 1. I also have static IP 2. i am using IIS7.0 with Windows-7
Thank you so much…..
1. Screen Shot1
2. Screen Shot2
This question is probably better off on ServerFault. However, providing you have everything set up on your machine, you just need to open and forward port 80 to your host machine and set up a domain or access the site directly via external IP providing your bindings are set up correctly.
EDIT From a security point of view, it would be better practice to do as Germann said by having your public facing web server in its own DMZ.
Finally i have got it........
the steps i have followed are......
define port forwarding at router for that i have enter following values in my router's forwarding page.
--IP address of my PC
--port number which is open(you can see screen shot Brouse*:80(http) which shows port 80
is open for website on my IIS.
finally i have opened website on my IIS by : .http://mystaticip:port/xyzfolder/xyz.html.

Applying SSL certificate in IIS manager and "The process cannot access the file because it's being used by another process" error

I applied a self-signed SSL certificate in IIS manager to Default Web Site(added the HTTPS binding) and after that when I'm trying to start the web site, I'm getting the following error message:
"The process cannot access the file because it's being used by another process. (Exception from HRESULT: 0x80070020) ". But when I remove the HTTPS binding, everything works fine.
So, what is the problem? What might have I done wrong?"
Have you tried the Microsoft Support Article that mentions this process error occuring when you try to start a Web site in the Internet Information Services MMC snap-in
If you're trying to do this on a local machine, Skype can block the https port (443). To stop this:
Skype - Tools > Options > Advanced > Connection, then uncheck 'Use port 80 and 443 as alternatives for incoming connections'. Then quite Skype (right click in task bar, 'Quit Skype'), and try starting the website again in IIS.
VmWare Workstation 8 grabs 443 for its VM Sharing feature. You can disable it in the settings. http://communities.vmware.com/thread/341114
Yes exiting the Skype desktop app fixed this for me also.
If your running Windows 8(.1) the Skype App (Windows Store App) doesn't use the local 443 port if you can live without installing the desktop Skype app. Also you can pin it to your taskbar. This solution is good enough for me since I don't need all of the features the desktop version offers.
You may want to use some sysinternals tools to see if the file is really used by another process. I recommend Process Explorer. Once you've located the culprit, you can usually see why it opens the file.
If you can't find any process, maybe your code tries to open the file; check for any file handlers you may not have closed.

Unable to start debugging on the web server. The underlying connection was closed. The connection was closed unexpectedly

All of the sudden I'm getting the following error on my local web server (Win7 64bit, IIS 7.5). I've uninstalled & reinstalled IIS locally and it didn't fix it. IIS is set to start up automatically and I can see that the service has been successfully started. Upon a fresh reboot if I go into IIS and click on start website I get the following error:
The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020
If I try to start debugging on my local website project I get the following error:
Unable to start debugging on the web server. The underlying connection was closed. The connection was closed unexpectedly.
Any ideas on what I can try? I've been doing research on the issue and Microsoft suggest making sure no other service is listening on the same ports. I've verified that this isn't the issue.
Try changing the web site to use a port other than 80 (suggest 8080 for example) and see it if will start. If so that's a sure sign of another service using port 80 (Skype is a common culprit for this).
Application pool's identity password changed?
I know this is an old post, but I can't believe how many times I've been bitten by this. Some shops use integrated security for SQL, and often then on your local IIS needs your network login for the application pool. When your password expires, and you forget to change your password here, start banging your head on the wall... DOH!
Open IIS. Select Application Pools. Select the application pool used by your app. Click Advanced Settings... Select Identity, and the little "..." button to update your user/password.

Resources