add SSL encryption to the RPC port

[cipig]

it would be helpful to have the RPC port SSL encrypted, so that mm2 instances can be managed over the network through the RPC port, eg for marketmaking bots dealing with more then one node
saw that we now have the option wss_certs... could that be simply applied to RPC too, like rpc_certs and if defined the RPC port will be encrypted with the cert?

[artemii235]

It's possible, but you can also put a MM2 RPC behind the reverse proxy to reach the same goal. So it's unlikely to be implemented from the API side in near future.

[shamardy]

@cipig https was added in this PR #1861 which was merged to dev. You can close this issue once you test https and everything is working fine.

[cipig]

thanks, works fine
with \"https\":true, the RPC port is encrypted
if using self signed certs curl needs to be called with curl --insecure --url "https://127.0.0.1:7783"

works from remote too, with mm2 params \"https\":true,\"rpcip\":\"0.0.0.0\",\"rpc_local_only\":false and the remote IP in curl