Comment 4 for bug 1788660

Looking at the original bug description closer, we can see that in fact the original web page (the SPICE client) was loaded as https, but the websocket was definitely insecure.

That is different to the multiple other related issues I ran into. In the novnc code base it inherits the domain/port/protocol from the page it was loaded on - it's never explicitly set. We should check the code for the spice client to see if it's doing the same or not. (in xenial-queens which the original environment was)

Side note: This is working fine for me on bionic-rocky