*** Turns out we have to specify websocket traffic uniquely from port 80 in our Palo Alto FW’s ***
Rancher v1.2.0 fresh install on vmware nodes on-prem. I cannot get any graphs to come up, nor can I exec to a shell or view logs, or anything else that uses websockets (interactive status updates like “Starting… --> Running”)
RHEL7.2/Docker 1.12.3
WebSocket connection to 'ws://abcd.rjf.com/v2-beta/projects/1a5/subscribe?eventNames=resource.change&eventNames=service.kubernetes.change&limit=-1&include=instanceLinks&sockId=1' failed: WebSocket opening handshake timed out
WebSocket connection to 'ws://abcd.rjf.com/v1/hoststats?token=eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJjYXR0bGUiLCJyZXNvdXJjZUlkIjoiMWgxIiwiaG9zdFV1aWQiOiI3NzFlYWE3Yi02ZmFkLTRkZjAtNjI5NS0wZTQwMTFhN2M5MzgiLCJraWQiOiJkZWZhdWx0IiwiaXNzIjoiaHR0cDpcL1wvY2F0dGxlLmlvIiwiZXhwIjoxNDgxMDYwMDc3LCJpYXQiOjE0ODEwNTk3Nzd9.i9Q-MgCpJFyT-26ww6K6Cbn4awGQQse7bwmaFtj9VhCuA57qVOajGAEqiqWlvobyrqc6nFkxAwMO_X2vK6xCt2-slQRojS9CMT9Ob3iybWs2BQFSRT5PI8EqKVG9zKmXY67uccTo21r_jF6hq4uzuvrXNKjZE4W9o__obkMr4w0jyvhuOtcOY99sPZw6dnokyBu3DWI6chDOWZLX-FnCOkJQXcUyYT5CnjcKUrLqwhDZgeeXEqYOpXiIZCeIaRgcvhK5mKFWqvztN3JyxZcGfYgrMfFg7wqkBMBmmUgWuabSXCxIG6NGXHA7YqUUkRZrj_yKM-CP9nKftSh4vWvumA&sockId=3' failed: WebSocket opening handshake timed out
Socket error (state=connecting, id=3)
socket.js:169 Socket 3 closed
socket.js:48 Socket connecting (id=4, url=ws://abcd.rjf.com/v2-beta/projects/1a5/subscribe…)
socket.js:48 Socket connecting (id=5, url=ws://abcd.rjf.com/v1/containerstats…)
socket.js:48 Socket connecting (id=6, url=ws://abcd.rjf.com/v1/hoststats…)