>
> > How to diagnose "Failed to connect to server" error when attempting to
open
> > noVNC console in foreman web UI? I could not find anything helpful in
the
> > logs[1]. {grep for AVC [4]}
>
> The first thing to check is after you open the screen, immediately list
> processes on your Foreman server, you should find process websockify.py.
> If you list with all parameters (ps auxwww) then you will see exactly
> what certificates it was launched with.
>
> It must match with Foreman web application server certificate, which was
> loaded by the browser.
>
> Then check connections Browser <-> websockify.py <-> libvirt VM.
>
> Also check if the VM was launched with VNC or Spice console. The port is
> usually random, something like 5900 + N. You can easily misconfigure the
> VM and launch it without remote console.
>
> –
> Later,
> Lukas #lzap Zapletal
>
> –
> You received this message because you are subscribed to the Google Groups
"Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
I've also seen recently that browsers now reject sha1 based certificates,
YMMV.
Ohad