Web Deploy connection timed out - iis

I've previously had Web Deploy up and running without any issues. Following a company wide installation of Bitdefender, Web Deploy has stopped working. I've tried the following without any success
Added the following rule to Bitdefender firewall
Local Address: Any
Remote Address: our server IP port 8172
Protocol: TCP
Direction: Both
IP: Any
Network: Home / Office
Permission: Allow
Using the following telnet command, telnet [IP address] 8172, I get a blank screen.
Navigating to the URL for the publishing server connection, I'm prompted with a login and then a blank screen.
I don't have Fiddler, or anything similar, running.
I've tried on other machines in our office yet I get the same response.
Re-installed Web Deploy via Web Platform Installer Recommended Server Configuration for Web Hosting Providers and using command prompt I've restarted the agent services with the following commands
net stop msdepsvc & net start msdepsvc
net stop wmsvc & net start wmsvc
I've added IIS Manager Permissions to the appropriate site in IIS, using the server administrator account (which worked in the past) and configured web deploy publishing.
I'm running out of ideas of what to try so I'd appreciate any suggestions.
When attempting to validate the connection in Visual Studio I see the failed notification, "The operation has timed out".

The problem is in the Policies for Content Control. Exceptions need to be added for the sites you would like to web deploy to.
Click on policies, then go to the policy that applies to your development system. In my case this was "IT Policy." If you don't know, you can go to Network and drill down through Active Directory to find what policy applies.
Next, go to Content Control => Traffic. Check the boxes for Web (HTTP traffic) and Traffic Scan exclusions. Then add the URL or IP address for whatever system you are trying to deploy to (We used IP).
Hope that helps!

Related

Allow remote web server administration of Azure server core VM

I am trying to configure a server code 2016 VM on Azure to allow access from IIS on a remote server (outside of Azure) - I have been following documentation from here and here.
When I try to connect to the Azure servercore server from IIS (File, Connect to a Server, provide server name/port and credentials), I am getting the following error:
"Could not connect to the specified computer.
Details: Unable to connect to the remote server"
I have added the firewall rule as noted in the steps I have been following with no success. I believe that this may be a security group issue, but web searching has drawn a blank - I have not been able to find anything on connecting IIS to a VM on Azure in order to allow web server administration.
Any help would be much appreciated, preferably in simple steps - I'm a programmer who has had a devops task dropped on him, and as such have minimal understanding of Azure's mechanics and terminology!
Thanks!
So the error was due to the misconfigured NSG. Need to open up port 8172.

Azure WebDeploy Failing

I've been happily deploying my website to Windows Azure, but this morning I get the following error...
Web deployment task failed. (Could not connect to the remote computer ("xxxxx.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)
I can load the website and data is coming back from the WebAPI I have. I've looked at the link which suggests the following....
You can ping the remote machine
That the msdepsvc or wmsvc service
is started on the remote server.
Your firewall is not blocking
incoming connections of your ports on the destination. If you used
the default installation, then it would be 80 for msdepsvc and 8172
for wmsvc.
I've tried the ping, which doesn't work, but then a ping to the actual site doesn't work either (and the site works). As these are Azure servers I'm unsure how to check points 2 & 3.
Another site that I deploy to Azure has worked, so there must be something about this project
I'm hoping someone can point me in the right direction to look.
In the end I fixed the issue, by upgrading from "Shared" to "Basic", and then switched back again, this must of caused some sort or reset at the MS backend.

Cannot Connect to Windows Azure VM (Server 2012 R2) Web Deploy Service

I can't seem to be able to deploy a site to a windows server 2012 r2 running IIS and Web Deploy in Azure VM. I have verified that the port is open, the credentials are correct and the site name as well. I tried using http: and https: also tried using msdeploy.axd end point and the MSDEPLOYAGENTSERVICE one nothing. Check is the services are running and if I can connect to the machine which at can on port 80 to the default site. Tried connecting from multiple connections I get the same result...
Could not connect to the remote computer ("<computer name>.cloudapp.net"). On the remote computer make sure that Web Deploy is installed and that the required process ("Web Deployment Agent Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE. Unable to connect to the remote server.
After dealing with this for about an hour now, I figured out how to fix this on my Azure Virtual Machine.
First the obvious
Check that port 8172 (if you're using default settings) is open in your firewall
Check that the processes MsDepSvc and WMSVC are running.
Check that the site name is correct.
Management Service
In ISS, at the root level of the server, check your settings under Management Service.
It should have Enable Remote Connections checked:
Did you download the full package
This was the one that got me, I hadn't installed everything.
On the bottom of the WebDeploy page: http://www.iis.net/downloads/microsoft/web-deploy
You can download the full package, and then just install everything.
You don't mention if you have an endpoint configured for your Azure VM. If not, make sure you create an endpoint with a private port of 8172.
EDIT: Here is a troubleshooting guide for web deploy that includes the error message you've encountered. Additionally, from my own experience I have managed to mistype the site name and not install .NET and seeing similar errors.
Helpful but in the end in our case it was TLS mismatch. Check both machines can do TLS 1.2 if you are forcing it. Have put more detail here https://fuseit.zendesk.com/hc/en-us/articles/360000328595. Cheers

Can't create an Azure web site

Help! When I try to creat a web site on Azure, I receive the following error message:
There was no endpoint listening at https://geomaster.azurewebsites.windows.net/subscriptions/2762018c-1ace-4b11-a55d-7b69d004cca3/webspaces/eastuswebspace/sites that could accept the message.
I was able to create 2 sites about 3 months ago without any problem. My subscription is an active pay as you go account. I'm not trying to do anything advanced, just a web site connected to a SQL DB. The SQL DB creates without a problem. I was also able to create a virtual Win2008 machine. Azure reps have said my account is fine. I don't know where else to look. Thanks
-ph
If your development machine is behind a proxy server, the problem could be caused by the machine's proxy server settings. Have a look at them via Control Panel / Network and Internet / Internet Options / Connections tab / Lan Settings and try checking the box for 'Automatically detect settings' if it isn't.
Solved: Azure Problem - There was no endpoint listening at that could accept the message
Windows Azure Package Deployment Failed with Error - "There was no endpoint listening"
Same for me. Seems they simply do not have enough recourses atm.
refs:
http://social.technet.microsoft.com/Forums/windowsazure/en-US/611545bc-a061-4107-9240-597b60131b8b/error-creating-azure-website
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/389cba4f-8943-4f56-8b0e-9f9066154337/error-creating-azure-website

WMSVC works, Web Deploy Agent throws 401

I'm trying to get msdeploy working from the command line, and can successfully test against the WMSVC directly (using HTTPS, port 8172) with both a local admin account and using an IIS Manager user account. Here's the command line:
> msdeploy -verb:dump -source:appHostConfig=MyWebsite,wmsvc=myserver,username=iisuser,password=password -allowuntrusted
So, wmsvc= directs msdeploy to use https://myserver:8172/msdeploy.axd . However, because the target host firewall doesn't allow port 8172, I'd really like to use the Web Deployment Agent Service over port 80. But, it responds with a 401 when I change wmsvc to computerName:
> msdeploy -verb:dump -source:appHostConfig=MyWebsite,computername=myserver,username=myserver\localadmin,password=password
where computername= directs msdeploy to use http://myserver/MSDEPLOYAGENTSERVICE . In a browser, that URL prompts for username/password, and returns a blank page (if authenticated), so it seems to be listening and authenticating properly. Also, I've added full rights to the site root for NETWORK SERVICE.
What's the difference in using the Web Deployment Agent Service over the standard WMSVC? Thanks in advance!
As far as I've discovered so far, the differences are:
WMSVC is tightly bound with IIS, whereas the remote agent appears not to be
WMSVC users can be windows or IIS users, and you can delegate permissions via the IIS manager so they can run some tasks under other security accounts etc. You can also control the paths that they are allowed to do things under.
Remote agent users can only execute tasks within the context of their own account on the machine: you control what they can do directly through the windows security mechanism.

Resources