I installed a trusted cert and key for our foreman server, and webUI
trusted SSL works flawlessly. However, when I attempt to connect to the
NoVNC console, I get timed out, indicative of the connection using an
untrusted connection.
I know of the workaround to visit the https://foreman.fqdn:5911 page to
trust the self-signed certificate, however I would much rather have
websockify use the trusted cert and key that I'm using for the WebUI.
I notice the websockify.py connection has –cert and* --key* arguments
being fed to it… is there a config file somewhere that I can use to
change these values to my trusted cert and key?
change the following settings to your new key and cert:
in /etc/foreman/setting.yml
:websockets_ssl_key:
websockets_ssl_cert:
···
On Monday, June 29, 2015 at 1:38:17 PM UTC-5, lawre wrote:
>
> I installed a trusted cert and key for our foreman server, and webUI
> trusted SSL works flawlessly. However, when I attempt to connect to the
> NoVNC console, I get timed out, indicative of the connection using an
> untrusted connection.
>
> I know of the workaround to visit the https://foreman.fqdn:5911 page to
> trust the self-signed certificate, however I would much rather have
> websockify use the trusted cert and key that I'm using for the WebUI.
>
> I notice the websockify.py connection has *--cert* and* --key* arguments
> being fed to it... *is there a config file somewhere that I can use to
> change these values* to my trusted cert and key?
>
> sample output:
> /usr/share/foreman/extras/noVNC/websockify.py --daemon --idle-timeout=120
> --timeout=120 5911 esxi.fqdn:5906 --cert /var/lib/puppet/ssl/certs/foreman
> .fqdn.pem --key /var/lib/puppet/ssl/private_keys/foreman.fqdn.pem
>
>
>
