Project

General

Profile

Support #8024

Foreman Xen VNC Console

Added by Enrico Bartz almost 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Hi,

i was setting up the connection between my foreman instance (1.6.1) and my XEN Cluster (6.2) a few days ago which went well.

The only thing which is not working is the VNC Console. I was searching for more Informations on how to set this things up but i was not able to get this fixed.

I have a working VMWare installation with the Console Feature enabled so I think it's not an issue with my browser settings as suggested in http://theforeman.org/manuals/1.6/index.html#7.1NoVNC .

What I am searching for is maybe a manual like this: http://theforeman.org/manuals/1.6/index.html#5.2.9VMwareNotes . Which explains which ports are needed and if there are maybe things i have to enable in XEN.

Could you please provide more information on how to get the console working or send me a few steps which would help me troubleshooting?

Regards,
Enrico

Associated revisions

Revision 0e749707 (diff)
Added by Michael Moll over 6 years ago

refs #8024 - remove outdated ssl information

History

#1 Updated by Operations ooVoo almost 7 years ago

Hi,
Now it only supports Non-SSL connection for VNC console.
So most probably you have your foreman redirecting your browser to the https port
to disable it, just change it in your config/settings.yaml file:

:require_ssl: false

and restart your foreman instance.

#2 Updated by Enrico Bartz almost 7 years ago

Operations ooVoo wrote:

Hi,
Now it only supports Non-SSL connection for VNC console.
So most probably you have your foreman redirecting your browser to the https port
to disable it, just change it in your config/settings.yaml file:

:require_ssl: false

and restart your foreman instance.

I changed the setting as you wrote it but I still get the "Failed to connect to server" message when i try to connect to the VNC console.

As i already mentioned i have it working with a VMWare cluster on the same foreman instance without facing any problems so i don't think it's an issue with my ssl / browser settings.

Are there any ports or settings needed for connecting to the console?

A little guide like the one i mentioned regarding VMWare would be very nice.

#3 Updated by Operations ooVoo almost 7 years ago

Did you verify you were running foreman web UI with "http" rather than "https". Because it's not an issue from your ssl/brower, it's just foreman VNC that doesn't support SSL connection now.

#4 Updated by Enrico Bartz almost 7 years ago

Operations ooVoo wrote:

Did you verify you were running foreman web UI with "http" rather than "https". Because it's not an issue from your ssl/brower, it's just foreman VNC that doesn't support SSL connection now.

Hi,

i have disabled https and restarted as i told you before.

As I also told you before I have already done everything which is described in the VNC troubleshooting guide without getting it to work.

As already mentioned, which VMWare i don't have any problems with connecting so i don't think it's browser related.

Could you say me maybe on which ports the module is trying to connect to the XEN Server, so i can maybe look for firewall issues?

#5 Updated by Pujan Shah almost 7 years ago

Hi Enrico,

I had similar issue with foreman_xen plugin but in latest version(0.4.1) it got resolved. Which version you are using? Also if it's older can you update to latest and check.

#6 Updated by Anonymous over 6 years ago

What's the status regarding this issue with Foreman 1.7.x and foreman_xen 0.0.6 or Foreman 1.8.1 and foreman_xen 0.1.0?

The README of foreman_xen still recommends to turn of ssl alltogether, which is not a good thing...

#7 Updated by Operations ooVoo over 6 years ago

  • Status changed from New to Resolved

Please use latest version of Foreman + foreman xen plugin 0.1.1.

In case you use foreman via SSL it will requires secure web socket connectivity, so make sure that foreman user has an access to your certificate for proper running websockify.py process.

/usr/bin/python /usr/share/foreman/extras/noVNC/websockify.py --daemon --idle-timeout=120 --timeout=120 5910 localhost:46157 --cert /var/lib/puppet/ssl/certs/YOUR_CERT.pem --key /var/lib/puppet/ssl/private_keys/YOUR_CERT.pem

you may change permission to allow foreman user to access your private/public keys

chmod -R 775 /var/lib/puppet/ssl/

Also available in: Atom PDF