Problem:
Trying to start a console for vm in Foreman but only get a black stripe on screen saying loading. I do noticed when i look at log that the Starting VNC Proxy websockify.py is using ip:port when I think it should be fqdn:ip. Where and what file would I need to change so that the fqdn of VM is used instead of its IP address? Expected outcome:
VM Console Foreman and Proxy versions:
3.0 with Katello Foreman and Proxy plugin versions:
Distribution and version:
CentOS 8.4 Other relevant data:
No cannot get this to work. Reinstall a few times and now even installed just Foreman (no katello) and still this console will not display anything more than that little black line on the screen. Do you have this issue also? It seem this has been an issue for a while now and I can’t seem to find anyone with the fix
Can’t believe no one on this forum have seen this issue. I reinstall etc but issue still continue. I noticed out on google etc that a lot of people have issues with the noVNC console so there seem to be some sort of issue not being addressed. I have oVirt as provider and i can go over to oVirt and console works without any issues. What’s going on with Foreman. Anyone care to explain?
Do you have a valid HTTPS connection to Foreman UI? Green lock in the browser. Note “Confirm security exception” or self-signed cert will NOT work (Javascript will be prohibited from making secure connections).
Compute resource type you are trying to connect to? Version?
What is your foreman FQDN and IP? (Feel free to anonymize the data but do not make any mistakes.)
What is your hypervisor (compute resource) FQDN and IP? (Feel free to anonymize the data but do not make any mistakes.)
Shortly after you make an attempt, paste the process named “websockify.py” with all its arguments, feel free to anynomize IP/FQDN correctly.
Do you have a valid HTTPS connection to Foreman UI? Green lock in the browser. Note “Confirm security exception” or self-signed cert will NOT work (Javascript will be prohibited from making secure connections).
I don’t have the “Green lock in the browser” Mine have a warning bang on it - what steps need to be taken to get this green?
Compute resource type you are trying to connect to? Version?
What is your foreman FQDN and IP? (Feel free to anonymize the data but do not make any mistakes.)
I have RHV -M 4.4.7.7-0.1.el8ev managing oVirt Node 4.4.8. I used Foreman 3.0 with Katello 4.2 to create VM which works but when trying to use the console in Foreman UI to connect to the VM. Everything works except connecting to the VM console in Foreman UI. When the VM shows up in oVirt I can open a console in the oVirt Web UI without any issues.
labmgt.“mydomain”.net ip 192.168.33.2
192.168.33.4 and 5 are oVirt hypervisors in HA mode so when creating VM it can land on either
What is your hypervisor (compute resource) FQDN and IP? (Feel free to anonymize the data but do not make any mistakes.)
See above
Shortly after you make an attempt, paste the process named “websockify.py” with all its arguments, feel free to anynomize IP/FQDN correctly.
The important parts can be seen without an account.
From what I see (and from what has been posted here before), you cannot do “accept risk” when your browser tells you it does not trust the Foreman WebUI Certificate but you have to instead download the certificate from your Foreman server and properly import it to your browsers CA Trust store. You will most likely need to revoke the trust exception first, too. You should be able to find how to do most of that in your browser’s documentation.
Correct and it is actually not a paywall, more of a registrationwall. You can simply register and even get than RHEL for free for personal use. Just search for “Red Hat Developer Subscription for Individuals” (as I am not sure which post is the newest).
