# Lack of Docs on Debugging Websocket Proxy

**URL:** <https://forums.suse.com/t/lack-of-docs-on-debugging-websocket-proxy/2157>\
**Category:** Rancher 1.x\
**Created:** [March 24, 2016, 7:43pm UTC](https://forums.suse.com/t/lack-of-docs-on-debugging-websocket-proxy/2157 "2016-03-24T19:43:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JJediny](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JJediny](https://forums.suse.com/u/JJediny)\
**Post date:** [March 24, 2016, 7:43pm UTC](https://forums.suse.com/t/lack-of-docs-on-debugging-websocket-proxy/2157/1 "2016-03-24T19:43:31Z")

</div>

We’ve recently deployed Rancher on AWS, however we’re encountering alot of timeouts and failure to connect to container’s exec/stats… I’m figuring are being caused by a websocket issue, we had to watch the meetup recording to know that AWS ElasticLoadBalencer needs to be manually configured…

But now that we have re-instantiated the environment with enabling ELB rules to enable websocket over TCP, we’re still encounter websocket errors connecting to the containers. I know that this is probaley caused by an issue with websocket proxy but there are no docs on troubleshooting… Are there a simple set of steps to ensuring all the websocket needs are configured/implemented correctly?

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [March 24, 2016, 7:57pm UTC](https://forums.suse.com/t/lack-of-docs-on-debugging-websocket-proxy/2157/2 "2016-03-24T19:57:49Z")

</div>

Did you see these installation notes?

[http://docs.rancher.com/rancher/installing-rancher/installing-server/basic-ssl-config/#running-rancher-server-behind-an-elb-in-aws-with-ssl](http://docs.rancher.com/rancher/installing-rancher/installing-server/basic-ssl-config/#running-rancher-server-behind-an-elb-in-aws-with-ssl)