Problem when using an SSL certificate to bind the https port
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @kareemshah ,
Are you following all the steps from this tutorial? https://knowledge.alteryx.com/index/s/article/Configuring-Alteryx-Server-for-SSL-Obtaining-and-Insta...
If you are, sometimes the cert hash comes with an invisible character before/after the string. I would suggest deleting the first and last characters and re-adding them, just in case. Or check with Notepad++ for weird characters.
Best,
Fernando Vizcaino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Break the command to bind the certificate into separate parts. Follow these steps instead of typing the entire command in the command prompt window (i.e.; "netsh http add sslcert ipport=0.0.0.0:443 certhash=‎74d4ca722e2954cd225f9b4697d2fc7f6747194c appid={eea9431a-a3d4-4c9b-9f9a-b83916c11c67}").
Steps:
- Go to command prompt
- type "netsh"
- type "http add sslcert ipport=0.0.0.0:443 certhash=‎74d4ca722e2954cd225f9b4697d2fc7f6747194c appid={eea9431a-a3d4-4c9b-9f9a-b83916c11c67}"
(Replace the certhash from above with your certificate thumbprint)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The error "The Parameter is Incorrect" when binding HTTPS to port 443 usually means an issue with the SSL certificate or IIS setup. First, check if the certificate is valid, not expired, and has a private key (look for the key icon in MMC > Certificates > Personal). If the private key is missing, re-import the certificate with the full. PFX file. Also, ensure the hostname matches the certificate’s domain. If the issue persists, try removing and re-adding the binding in IIS or running netsh http show sslcert in CMD to check existing bindings. Hope this helps!
