After upgrading to 3.2.3 i get the following error when deploying an IIS site with a SSL certificate. Dowgrading to 3.2.2 it works again - so a bug has been introduced in 3.2.2
Finding SSL certificate with thumbprint XXXX
09:46:28Info
Found certificate: CN=*.blah.com, OU=x, OU=x, OU=Domain Control Validated in: WebHosting
09:46:29Info
Adding a new SSL certificate binding…
09:46:29Info
The parameter is incorrect.
09:46:29Info
Attempt 1 of 5 failed: ScriptHalted
09:46:29Info
Waiting for 3 seconds before retrying…
09:46:32Info
Retrying…
09:46:32Info
Adding a new SSL certificate binding…
09:46:32Info
The parameter is incorrect.
09:46:32Info
Attempt 2 of 5 failed: ScriptHalted
09:46:32Info
Waiting for 3 seconds before retrying…
09:46:35Info
Retrying…
09:46:35Info
Adding a new SSL certificate binding…
09:46:35Info
The parameter is incorrect.
09:46:35Info
Attempt 3 of 5 failed: ScriptHalted
09:46:35Info
Waiting for 3 seconds before retrying…
09:46:38Info
Retrying…
09:46:38Info
Adding a new SSL certificate binding…
09:46:38Info
The parameter is incorrect.
09:46:38Info
Attempt 4 of 5 failed: ScriptHalted
09:46:38Info
Waiting for 3 seconds before retrying…
09:46:43Info
Retrying…
09:46:43Info
Adding a new SSL certificate binding…
09:46:43Info
The parameter is incorrect.
09:46:43Error
ScriptHalted
09:46:43Error
At E:\Octopus\Applications\Extern_Services_Production\X\2015.11
09:46:43Error
.33.0_4\Octopus.Features.IISWebSite_BeforePostDeploy.ps1:248 char:6
09:46:43Error
Thanks for bringing this issue to our attention guys. Looks like one of the code flows through the IIS setup wasn’t fully tested for backwards compatibility.
Our sincere apologies for the inconvenience and we are looking into a fix we we speak. In the meantime the workaround as suggested by Matt & Kaylee should do the trick.
Thanks for your patience,
Rob
The workaround isn’t working for me. What kind of changes did you make to the binding settings? Did you just save the binding, or the whole process step, too?
Jake,
To change and save the binding you have to save the step itself. Perhaps there is a bit of a naming problem with the Save button on the bindings modal, you you then need to save the step itself.
Cheers,
Rob
That’s still not working. I even tried removing the ssl binding altogether. If I do that, I can get it to deploy. But when I add it back in and create another release I get the same error.
I got it to work. This time I edited the ssl binding, toggled the checkboxes for Require SNI and Enabled. Saved. Saved the process step. Then edited it again, toggled both checkboxes back. Then it worked.
In case it helps…
The deploy log during the failures included this at the top of the deploy IIS site step (thumbprint, site, and server name removed):
http/:80:sales.phidev.com//True/false|https/:443://True/False
Finding SSL certificate with thumbprint
Found certificate: CN=WMSvc- in: Root
When it started working, it looks like this:
[{“protocol”:“http”,“ipAddress”:"",“port”:“80”,“host”:".com",“thumbprint”:"",“requireSni”:false,“enabled”:true},{“protocol”:“https”,“ipAddress”:"",“port”:“443”,“host”:"",“thumbprint”:"",“requireSni”:false,“enabled”:true}]
Finding SSL certificate with thumbprint
Found certificate: CN=WMSvc- in: Root