Unable to connect to kernel

[sds-dubois]

Everytime I try starting a new notebook I get a connection error to the kernel. My browser's debugger shows the following message:

WebSocket connection failed:  wss://templ-prod-group-2hn2-templ-prod-group.juliabox.com./api/kernels/2a17717a-722d-46f7-bdd0-db2c4aef8959

I don't know if it can be useful but I'm on Windows 10.

[tanmaykm]

Could be due to one of the following:

• stale packages in ~/.julia. See The Julia 0.4.6 kernel in JuliaBox keeps dying  #424
• websocket connections not allowed from your current network. There is a link to test websocket connections on the settings page, which may give some more details.

[jin2fantasy]

I have a same problem. I clicked the reset packages button, but it didn't help. Also, the network connectivity test in the setting all passed. Different browsers all failed to connect.
FWIW, I can connect the kernel without any problem from my android phone and tablet (using Chrome). Maybe this is somehow related to Windows 10?

[nkottary]

You will need to allow third party cookies if you have disabled that in
your browser settings.

On 15 November 2016 at 19:42, jin2fantasy notifications@github.com wrote:

I have a same problem. I clicked the reset packages button, but it didn't
help. Also, the network connectivity test in the setting all passed.
Different browsers all failed to connect.
FWIW, I can connect the kernel without any problem from my android phones
and tablets. Maybe this is somehow related to Windows 10?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#483 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC3EZ81WOL-s4jQJ93IAR4c_lNnK-3dnks5q-b3GgaJpZM4Klrg2
.

Nishanth H. Kottary

[camaramm]

@nkottary:

I have done the following:

1. Network connectivity tests in settings page have all passed.
2. I have cleaned out my ~/.julia.
3. Third party cookies are allowed in my browser settings.

However, I am still experiencing WebSocket connection failed, as shown by browser's console on notebook.

Do you have any other suggestion?

[AnthonyJacob]

I have had the same problem. Accepting third party cookies and restarting the browser worked for me.

[camaramm]

So, today I've finally got it working. My Firefox browser was set to accept third-party cookies from visited sites. Changing this setting to always solved the problem. Thanks @nkottary .

[zaib4tsu]

You shouldn't need to set "accept third-party cookies" to "always" if your current setting is the more secure "from visited". This is poor practice on JuliaBox's part and the end user should NOT have to degrade their browser security to use this software.

I found the solution by checking what "other" cookies JuliaBox saves - unsurprisingly a stupid naming convention issue (JuliaBox's fault) whereby it saves cookies with at trailing dot (i.e. ".com." instead of ".com" as per convention, hence bypassing my regular "allow juliabox.com" filter (which would usually work).

So, to allow JuliaBox to work in-browser without reducing your security settings, the solution is under Preferences > Privacy > Exceptions, add the following and click "Allow" to add them to your safe list:

juliabox.com
juliabox.com.
https://juliabox.com
https://juliabox.com.

That should be the correct fix - which basically allows the stupidly named cookie that JuliaBox uses, without globally allowing ALL third-party cookies (and reducing general security).

NB: This applies to Firefox, the method may be different for Chrome/Safari/etc.
This might be useful to: @camaramm @AnthonyJacob @nkottary @tanmaykm

[tanmaykm]

Thanks @zaib4tsu
The trailing dot in the cookie name must be a bug that crept in.
It should be possible to change it at juliabox end.

[sabian2008]

I can confirm that in Chromium the problem still persists (don't know if due to the same reason). I can't find a way to make juliabox.com an exception for accepting cookies, neither manually nor hitting in "Always accept cookies from ..." in the GUI.

In Firefox however, not even zaib4tsu fix is required. It works out of the box.

Cheers,