Michael Sync

Michael Sync

Crisp, minimal personal blog

29 Oct 2013

WebDeploy 3 – Error in publishing an ASP.NET website to Amazon EC2 IIS


Here is the error that I got when I publish a website from Azure VM to Amazon EC2 VM. I am using the following MSBuild command to do the deployment and I got Web Deploy 3.0 installed on EC2 VM.

1
2
3
4
5
6
7
msbuild /p:Configuration=Release /p:OutputPath=bin 
        /p:VisualStudioVersion=11.0 /p:DeployOnBuild=True 
        /p:DeployTarget=MSDeployPublish 
        /p:MsDeployServiceUrl=https://my-super-cool-server/msdeploy.axd 
        /p:AllowUntrustedCertificate=True /p:DeployIisAppPath=YourWebSiteInstanceName 
        /p:MSDeployPublishMethod=WMSVC /p:username=root 
        /p:password=SuperComplexRootPassword

Error Message

[VSMSDeploy] C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(4196, 5): error ERROR_DESTINATION_NOT_REACHABLE: Web deployment task failed. (Could not connect to the remote computer (my-super-cool-server""). On the remote computer, make sure that Web Deploy is installed and that the required process (“Web Management Service”) is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.) [14:58:46][MyWebsite\MyWebsite.csproj.teamcity] Project MyWebsite\MyWebsite.csproj.teamcity failed.

VSMSDeploy-update

Solution

As this post is not about how to use WebDeploy to deploy a website, I am not going to write the detailed steps here. If you are new to using the webdeploy, please read this post “Automating Deployment with Microsoft Web Deploy” The reason that I got this error is that the default for Web Management Service is not enabled by default in EC2. The solution is to enable the port 80 (which you might already enabled it for your website) for Web Deployment Agent and port 8172 for Web Management Service in both the server’s firewall and EC2 Security Group.

  • Web Deployment Agent Service : Port 80
  • Web Management Service : Port 8172

EC2 Security Group

Hope it helps for those who are using MS deploy for publishing website on IIS.

Reference: