Docs: The netsh http add sslcert seems to be wrong?

Created on 4 May 2018  Â·  2Comments  Â·  Source: dotnet/docs

A lot of folks seem to have problems w/ this command. See: https://stackoverflow.com/questions/779228/the-parameter-is-incorrect-error-using-netsh-http-add-sslcert

This worked for me:

netsh http add sslcert ipport=0.0.0.0:8085 appid="{7BBE87B9-D98F-41D7-B726-FC5E1300ED28}" certhash=4da5af739d6745de4e38fea9574cdaa79032ea14

This failed with message "The parameter is incorrect.":

netsh http add sslcert ipport=0.0.0.0:8085 certhash=4da5af739d6745de4e38fea9574cdaa79032ea14 appid={7BBE87B9-D98F-41D7-B726-FC5E1300ED28}


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Technology - WCF P1 Pri2 doc-enhancement unspecifiesvc

Most helpful comment

This is actually a syntax problem of cmd vs Powershell. Changing the command to
netsh http add sslcert ipport=0.0.0.0:8085 certhash=4da5af739d6745de4e38fea9574cdaa79032ea14 appid="{7BBE87B9-D98F-41D7-B726-FC5E1300ED28}" will work in both terminals.

All 2 comments

@zhenlan @glennc can you look at this feedback for a WCF topic?

This is actually a syntax problem of cmd vs Powershell. Changing the command to
netsh http add sslcert ipport=0.0.0.0:8085 certhash=4da5af739d6745de4e38fea9574cdaa79032ea14 appid="{7BBE87B9-D98F-41D7-B726-FC5E1300ED28}" will work in both terminals.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

svick picture svick  Â·  3Comments

skylerberg picture skylerberg  Â·  3Comments

stanuku picture stanuku  Â·  3Comments

gmatv picture gmatv  Â·  3Comments

tswett picture tswett  Â·  3Comments