7

First, I upgraded my ASP.NET Core project to 1.1.0. That wasn't smooth at all. Now, when it works, I can't deploy it!

I deploy it to IIS (Windows Server 2012 R2) and I get the error saying

can't validate the certificate ... ERROR_CERTIFICATE_VALIDATION_FAILED!

I added this to my publishing profile:

<AllowUntrustedCertificate>True</AllowUntrustedCertificate>

but that doesn't work in VS2017 RC. So, how can I deploy now? Why you guys do not provide it from a start? This is an essential operation!

Improve this question
2
  • Same issue ... You don't have a fix for this by chance? Commented Jan 24, 2017 at 10:55
  • A fix is in the works, but a workaround is to enable UseMSDeployExe in the pubxml file. Commented Apr 12, 2017 at 4:20

3 Answers 3

Reset to default
4

The issue also appears when you are using wrong credentials: and\or stored password. To check this add into the pubxml file the following line:

<UseMsdeployExe>True</UseMsdeployExe>

this will switch from VSMSDeploy to MSDeploy - it got you more verbose with errors. If you store your password just remove the .pubxml.user file stored near .pubxml file and in Publish setting add the password once more.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

3

Same here. Solved by creating a new publish profile.

Improve this answer

1 Comment

Thanks that worked for me also. Unfortunately the new version doesn't output the deploy command anymore in the output window which was useful for debugging, i.e. Executing command ["C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe" ...]
2

TL;DR

On the publish window, click on settings under summary, press summary and you will see the familiar publish dialog from VS 2015. Press validate connection and enter your credentials, making sure the success icon shows up. Now, try your publish profile from VS 2015, or a create a new one.

Note: After this step, having AllowTrustedCertificate set to true doesn't seem to matter.

Other Info:

I have a similar set up, working on Core 1.1 projects, working on a Windows 7 machine, and deploying to Windows Server 2012 R2 via Web Deploy on IIS.

Initially, I was using Visual Studio 2015 and publish only works if you add <AllowUntrustedCertificate>true</AllowUntrustedCertificate> and <UserName>domain\user.name</UserName> to the pubxml file. Migrating to Visual Studio 2017 CE caused the problem for me. See tldr section for answer.

I hope this helps others. Please comment to verify that this method works.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.