13 Jan
2014
13 Jan
'14
8:43 p.m.
I am able to gain noNVC access by going to https://<FQDN>:6100, however, I'm trying to find a practical, permanent solution, to make it more user friendly for clients. The firewall is allowing connections to it. On 1/13/2014 3:25 PM, Joop wrote:
Neil Schulz wrote:
I see it under there as well, however, still getting server disconnect.
Seeing anything being logged/outputted by the webproxy if you run it on the commandline instead of a service?
I have recently got noVNC working and I, ehhh, had a firewall in the way :-) Make sure you can connect to engine:6100 from you client and that engine can connect to your hosts. Its highly unlikely that this is your problem but ...
Regards,
Joop