We have received questions about the graphical console not working on networks that require a proxy. It has something to do with the way that the java application forwards traffic back through an open connection. Regardless of this, I have discovered a basic way to troubleshoot it if the console not working is a grid problem, or a network problem. Basically so long as you have direct ssh access to the controller you can create a tunnel to bypass the proxy. Say you have root access to a customers grid and you are using a basic user account in linux just do this:
Basically, follow these commands:
`ssh root@<GRID_CONTROLLER>`
`vi +88 /etc/ssh/sshd_config` (#AllowTcpForwarding yes) may not be line 88 if the customer has done a lot of customizations
Remove the hash in front of AllowTcpForwarding yes
`service sshd restart`Bypass Proxy for Graphical Console
`exit`
‘sudo ssh --I ~/.ssh/id_rsa --C --L 80:127.0.0.1:80 --L 443:127.0.0.1:443 root@<GRID_CONTROLLER>` (You must use sudo or be root to forwards privileged ports just make sure you use the right key)
Next:
Open a web browser and connect to:
http://127.0.0.1
accept certificate
Login to the customer grid
Open application and then open a graphical console. If it works you know it’s a networking problem on their end. When you are done of course:
Vi /etc/ssh/sshd_config and comment (#) out the AllowTcpForwarding
`service sshd restart`
`exit`
By tunneling your ports through the ssh connection you are bypassing any firewall, packet sniffers, l7 filters, or proxies allowing a direct “http/https” connection to the controllers web server. Don’t forget to undo this when you are done.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|