Resurrecting the thread, sorry for the delay.
> I have tested using vncviwer, the VNC proto is working, I can view the
> target VMs desktop on port 5902.
Ok, good test.
> Found logs, this is extract:
>
> var/log/foreman/production.log:2016-03-11 18:01:35 [app] [D] VNCProxy Error:
> WebSocket server settings:
> /var/log/foreman/production.log:2016-03-11 18:01:35 [app] [D] VNCProxy
> Error: - Listen on :5928
> /var/log/foreman/production.log:2016-03-11 18:01:35 [app] [D] VNCProxy
> Error: - Flash security policy server
> /var/log/foreman/production.log:2016-03-11 18:01:35 [app] [D] VNCProxy
> Error: - No SSL/TLS support (no cert file)
> /var/log/foreman/production.log:2016-03-11 18:01:35 [app] [D] VNCProxy
> Error: - Backgrounding (daemon)
>
> Why is "No SSL/TLS support (no cert file)" listed as an error now that I
> have "websockets_encrypt: false"?
This is actually not an error, but standard output of the websockify.py
program but we mis-print it the output with error level. Everything
should be operating correctly, it simply informs you that no certificate
file was provided on the command line (which matches your ps output):
Now, if you restarted httpd you the NoVNC console should attempt to
communicate with websockify over non-SSL connection. Now, it depends on
the browser policy if it allows this or not (Foreman WebUI is always
HTTPS unless you turn this off).
I doubt todays browsers allows this, and this is a good thing. The key
is to enable SSL again to get this working.
What setup are you trying? Is this upstream Katello? Which version?