In answer to your question you can use any port in fact you can even set it up for multiple instances like test, staging and production even on the same machine to specify the port you use :[portnumber] just like under http.
Instruction on largely what you need to do can be found here
https://blog.boxofbolts.com/ssl/windows ... d-windows/ which is about binding the certificate to a port, the same steps would apply to a self signed or bought certificate, you could actually avoid these steps by running the service as administrator but I would not recommend that from a security perspective.
The only trick that seem to be at issue that I've set is wild cards don't seem to work in namely you can't simply change
- Code: Select all
<add key="URLBase" value="http://*:81/" />
to
- Code: Select all
<add key="URLBase" value="https://*:81/" />
you actually need a proper URL for a domain or an ip address at least that's what I had to do to make it work.
Mike in an email had been discussing WinAcme & Lets Encrypt and was going to do up a set of instructions but I don't know how far he got, using it gets you out of the cost of the certificate by using Lets Encrypt but you have to set it up to renew when the certificate expires, I'll forward you the email which also covers most of the steps mentioned in the link above.