Found a solution and posting it hear for anyone who wants to do this in the
future...
Seems that the problem was websockets not macking it through the ELB load
balancer. See this post for detaisl...
http://blog.flux7.com/web-apps-websockets-with-aws-elastic-load-balancing
Fundamentally the fix is to change the load balancer (classic version) to
using secure TCP as the protocol instead of https, so that the websockets
connections are also forwarded.
Case closed (for now)
On Monday, November 7, 2016 at 3:09:51 PM UTC-8, Ted Liefeld wrote:
>
> Still hoping someone out there has an idea...
>
> I installed net-tools into the container and found the following using
> netstat -tnlp
>
> sudo netstat -tnlp
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State PID/Program name
> tcp 0 0 127.0.0.1:33391 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:52271 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:36081 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:49909 0.0.0.0:*
> LISTEN -
> tcp 0 0 0.0.0.0:8888 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:39195 0.0.0.0:*
> LISTEN -
> tcp 0 0 127.0.0.1:51195 0.0.0.0:*
> LISTEN -
>
> I am wondering if the problem is that the kernel is listening on 127.0.0.1
> instead of 0.0.0.0? Still not sure how to control that in the
> jupyterhub_config.py though since I set the ips either explicitly to that
> of the hub or to 0.0.0.0.
>
> Anyone? Bueller?
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jupyter/27ff8fc2-43e0-4003-924a-967646cc01c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
