Skip to content
This repository has been archived by the owner on Nov 14, 2018. It is now read-only.

Websocket connection error #14

Closed
ViralBShah opened this issue Jul 24, 2014 · 10 comments
Closed

Websocket connection error #14

ViralBShah opened this issue Jul 24, 2014 · 10 comments

Comments

@ViralBShah
Copy link
Contributor

I am behind a firewall, and get this. I wonder if we can have a more seamless experience for folks behind firewalls - of course, each one has its own quirk.

screen shot 2014-07-24 at 1 59 12 pm

@ihnorton
Copy link

ihnorton commented Sep 5, 2014

Some comments from #59:

There is an IPython issue with some relevant discussion: ipython/ipython#2321

Some possible options:

@ViralBShah
Copy link
Contributor Author

The switch to SSL has fixed this. Now the firewall does not know it is a websocket connection!

@mturok
Copy link

mturok commented Oct 23, 2015

Sorry to revive this - I'm actually having this problem in a fresh install, and not sure which switch to SSL you are referencing.....

@tanmaykm
Copy link
Member

@mturok for a local install, you may be need to do the same as #307 if you see websocket errors.

@mturok
Copy link

mturok commented Oct 23, 2015

Thank you. I actually tried that....was starting juliabox with
http://localhost, where localhost is my Ubuntu 14.04 running under
virtualbox on a Windows host.

Do I need to start juliabox with a fqdn name and use the fix below?

On Fri, Oct 23, 2015 at 12:30 AM Tanmay Mohapatra [email protected]
wrote:

@mturok https://github.com/mturok for a local install, you may be need
to do the same as #307 #307
if you see websocket errors.


Reply to this email directly or view it on GitHub
#14 (comment).

@tanmaykm
Copy link
Member

Yes. That should most likely fix it.

If that doesn't. the other thing to check is whether your proxy/firewall configuration allow websockets in general.

@mturok
Copy link

mturok commented Oct 23, 2015

Thank you again! Will try in NYC am. Great and simple design here for
something fairly sophisticated.

On Fri, Oct 23, 2015, 1:23 AM Tanmay Mohapatra [email protected]
wrote:

Yes. That should most likely fix it.

If that doesn't. the other thing to check is whether your proxy/firewall
configuration allow websockets in general.


Reply to this email directly or view it on GitHub
#14 (comment).

@ViralBShah
Copy link
Contributor Author

Let's move the discussion to a new issue if we need to continue debugging.

@mturok
Copy link

mturok commented Oct 25, 2015

Just an fyi that the issue was elated to the proxy server we have combined
with the need for a fqdn. Not much more to debug but maybe something for
the README?

On Fri, Oct 23, 2015, 2:34 AM Viral B. Shah [email protected]
wrote:

Let's move the discussion to a new issue if we need to continue debugging.


Reply to this email directly or view it on GitHub
#14 (comment).

@tanmaykm
Copy link
Member

Thanks. Yes, I think it should be mentioned in the setup steps.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants