I am also having this same problem.

Would be great to have news on this

We are encountering the same issue. Seems like such a fundamental problem that has been unresolved for years.

It's been raised with MS since 2019: https://developercommunity.visualstudio.com/t/iis-web-app-manage-task-should-replace-the-certifi/547395

I'm having the same problem, does anyone have a workaround?

I'm having the same problem, does anyone have a workaround?

Removing the certificate (PowerShell) before executing this task

I found the problem. The output of "netsh http show sslcert" is different in new version of windows server vs older ones. The number of empty lines at the beginning varies.

Problematic file

The following line is there twice in the script and assume that the relevant information is at line 4 but for newer windows, the information is at line 6. I think this should be modified and be more robust.
$isItSameBinding = $result.Get(4).Contains([string]::Format("{0}:{1}", $hostname, $port))

I don't have time in the short term but the idea would be either to skip empty lines or having a regex searching for the relevant line.

Created this report bug - please upvote!

https://developercommunity.visualstudio.com/t/IISWebAppMgmt3---SSL-Certificate-add-fa/10371316

Hello there
Got here because I'm currently wrestling with this error. Does anyone have an idea how to circumvent it for the time being?

Can we get this fixed? As far as I know deployment groups are still officially supported and not deprecated, so the task IIS Web App Manage (for deployment groups) should be maintained and receive bugfixes. Or is it some kind of dead end?

Just started encountering this ourselves.
I didn't want to remove the certificate every time as makes rollbacks harder.

Can we get some feedback from developers on this please? There's still an open PR with a proposed fix for it too.
@omeshp perhaps you could shed some insight?

Updating our servers this month and just ran into this - would love to see it fixed to continue using ADO smoothly. The more custom powershell in a deployment, the more fragile it is.

I see some fixes have been merged, but devops only shows 0.* version available. If this task is supposed to be version 3, why aren't any other versions showing up? When do these changes show up in devops?