So this is some http server running somewhere, maybe lightpd not sure, and I would like to put my SSL cert on that too. Overkill for sure, but if it can be done I would like to do it :0)
This is unnecessary, in my opinion, as there is no reason to authenticate or protect the data on the display page.
If you are running ROON on linux, you could firewall port 9100, and install Nginx to reverse proxy to it with TLS, but it is such a chore to maintain TLS certificates I don’t think it is worth it.
TLS is normally deployed based on risk, and since there is none to the end user in this scenario, it wouldn’t make sense for ROON to include the ability to install certificates as part of the ROON interface and complicate the user experience.
Totally aware it offers no risk reduction to what is being presented, as I said before I know this is over kill. I run a wildcard cert in one location and a bunch of services being nginx already so adding 1 more config to this setup should be easy…
I did try with nginx, using a standard setup template, however this did not display content as it would only allow a connection back to a secure web socket, which I don’t think Roon is running. I don’t fancy hacking about in display_ui.js to get this working. Not to worry.