Project

General

Profile

Actions

Bug #3916

closed

ws_proxy port issues

Added by Markus Nussdorfer over 10 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Was just trying to set up console access to our VMWare Servers and discovered, that the host_port variable is never assigned from the defined PORTS Range
set in lib/ws_proxy.rb

Setting the VNC settings according to the manual has no effect, as the connections get opend on some random ports outside of that range
http://theforeman.org/manuals/1.3/index.html#5.2.8VMwareNotes

/usr/bin/python /usr/share/foreman/extras/noVNC/websockify.py --daemon --idle-timeout=120 --timeout=120 5910 esxhost:5902
/usr/bin/python /usr/share/foreman/extras/noVNC/websockify.py --daemon --idle-timeout=120 --timeout=120 5910 esxhost:5908

Actions

Also available in: Atom PDF