MsDeploy returns 403 forbidden

Question

We had a web application running on the intranet, and I'm trying to publish it on the Internet using Visual Studio 2010. Iis7 is running on the target server and the website management service is running.

In Visual Studio 2010, my service url is:

https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd

And the site / application:

Default Website / WebApp

It is marked as an IIS application at the destination and allows validation of the untrusted certificate, and I use the administrator account.

Visual Studio returns the following error:

Launch Web Deployment Publish application / package for https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd?site=Default%20Web%20Site ... C: \ Program Files \ MSBuild \ Microsoft \ VisualStudio \ v10 .0 \ Web \ Microsoft.Web.Publishing.targets (3588.5): Error: Failed to complete the network deployment task (remote agent (URL) https://xxx.xxx.xxx.xxx:8172/MsDeploy. axd? site = Default website) may not link. Verify that the remote agent service is installed and running on the target computer.)

The remote agent (URL https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd?site=Default website) may not be contacted. Verify that the remote agent service is installed and started on the target computer. An unsupported response was received. The response header 'MSDeploy.Response' was '', but 'v1' was expected. The remote server responded with an error: (403) Forbidden.

Any ideas on how to publish it without a valid SSL certificate?

Answer 1

If you go to IIS,
Click on the node server in the "Connections" list,
Double-click "Management Service", then you will be taken to the screen with the checkbox "Enable remote connections."
This flag (and the rest of the screen) may be grayed out because the service is running. Just click the Stop link in the Actions panel, then check the Enable Remote Connections box and any other settings you want to change here, then click Apply and Start again in the Actions panel.

This will hopefully allow you to connect using the appropriate credentials to the service from a remote computer. (If the correct ports and stuff are open and all this is jazz.)

I think this helps your situation. At least you won’t get 403, but you may have another MsDeploy error.

Answer 2

I had the same problem. Talk about jumping through hoops ... The solution requires setting up user access and deployment permissions, etc.

• after getting the “NOT FOUND” error, as Shikhan Yakar predicts above, I had to change webdeploy (I needed to re-search the download for “WebDeploy_x64_en-US.msi”) to include all the parameters.
• a new error has appeared, always good, ERROR_USER_NOT_AUTHORIZED_FOR_CONTENTPATH. for this, I looked at deployment errors on the Internet (see link below).

Diagnostics. A non-administrator user tried to work with a web deployment provider for which the user is not currently allowed. Permission — The default installation of Web Deploy 2.0 creates the delegation rules for the service management service, which allows non-administrators to perform operations with this provider. it is possible that the delegation rule needed for this provider has not been configured correctly. Workaround: On the program control panel, start Repair in Web Deploy 2.0. Alternatively, create a delegation rule manually.

Turns out I had to manually create it from the "Configure Web Deployment Handler" section (see link below), using this guide to "Configure WMSVC and IIS Manager Permissions" and "Create Delegation Rules for Web Deployment" problem.

Notes: Diagnosed using "web deployment error codes": http://www.iis.net/learn/publish/troubleshooting-web-deploy/web-deploy-error-codes and is ultimately configured using processes from the “Configure Web Deployment Handler”: http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler