IIS - Add CCS HTTPS bindings based on HTTP bindings - Error

[Rasmita_Polleyi]

Hi ,

We are using IIS - Add CCS HTTPS bindings based on HTTP bindings template to add https binding to our sites but we see failures more often when we push multiple deployments pointing to the same deployment target…
httpsBinding.ps1 (2.1 KB)

Attached is the PowerShell template we use and below is the error we see one during adding a new binding and the 2nd during updating the binding

Let us know how we can modify the template.

Thanks,
Rasmita

[Kenneth_Bates]

Hi Rasmita,

Thanks for getting in touch! You can modify an installed community-written step template in your web portal under Library > Step Templates, and when selecting this step template you can modify anything in it including the source code. Note this will require you to save the modified step template as a copy, so you’ll need to remove the original from your project’s deployment process, and add the new copy.

More details on updating step templates can be found in the following doc page.

Update step templates - Octopus Deploy

I hope this helps, and please don’t hesitate to reach out if you have any further questions going forward.

Best regards,

Kenny

[Rasmita_Polleyi]

Hi,

I am aware of how to modify the template and corresponding steps associated with the template. My question was how i can fix the errors associated with the binding and applicationHost.config file change for multiple deployments. If there is any suggestion.

Thanks,
Rasmita

[Kenneth_Bates]

Hi Rasmita,

My bad, sorry about my misunderstanding! Thanks for the clarification. I think the error message is indicating some issue around the value defined on a parameter in the mentioned lines (New-WebBinding -Name $WebSiteName -Protocol https -IPAddress $IPAddress -Port $Port -HostHeader $HostHeader -SslFlags $SslFlags;).

This is certainly a guess on my part, but maybe you’re specifying in the Website Name parameter the output variable as mentioned in the help text? e.g. #{Octopus.Action[*].IISWebSite.WebSiteName}? If you’re using this output variable in this field, are you targeting your IIS step name (i.e. Action[StepName])? Is the IIS step running before this step template runs in your process? If not the output variable won’t be populated yet when this step is running.

The easiest way to troubleshoot this further I’d like to have a look at the verbose logs taken from a deployment that’s exhibiting this behavior. Could you create two project variables (OctopusPrintVariables and OctopusPrintEvaluatedVariables, both with a value of True), create and deploy a new release and send me the resulting task log?

I look forward to figuring this one out!

Best regards,

Kenny