My package is using the “Deploy to IIS” step. This step is configured to deploy an IIS Website.
I’ve also configured this step to add 3 bindings.
HTTP with port 85
net.tcp with port 850:*
net.pipe with port *
As you can see from the screen shot attached, the appropriate fields are being set in IIS, however, the values do not reflect the configuration in Octopus.
The IIS bindings have the following values post deployment
HTTP has port 85 which is correct
net.tcp has port :850:: which is incorrect
net.pipe has port :: which is incorrect
Could you please advise if this is a bug or if I’m doing something wrong?
Thanks for reaching out, I’m sorry to hear you are having issues with the IIS bindings.
Are you using a PowerShell script on the “Deploy to IIS” step to perform the net.tcp and net.pipe bindings? If so are you able to send the script through so we can investigate the issue further. Also if you are able to send through the deployment logs, that might also help us identify the issue.
If you require any additional information or clarification please let me know.