Closed ptoman closed 7 years ago
I have followed through the same as mentioned by @ptoman , and I also cannot connect to the kernel.
I tried cleaning up my home directory to reproduce this error but I was still able to connect to the kernel. Apart from the 2 measures mentioned in #483 I don't have any other suggestions to fix this issue. Looks like there may be something in your network that is blocking websockets.
My problem was browser's third-party cookies setting. It is working now.
JuliaBox starts Jupyter but cannot connect to the kernel. It looks like a websocket problem (perhaps a kernel is being created with one identifier and the page is trying to talk to another identifier?)
Some variables that come to mind that have no effect: browser, incognito mode, login method (Github vs. LinkedIn), internet connection (VPNness), version of Julia/Python, whether notebook is existing or new.
As per #483 and #424, I tried moving ~/.julia to another name -- the problem persists. I also tried the pretty yellow button "Reset my packages" within my Account, and I was told I'm already using system packages.
I am able to start julia and python in the Console.
In very weakly potentially relevant news, Juliabox worked fine for me until around the time I rm -rf'ed a lot of files from a completed project to clean up space on your graciously provided servers (I'd been checkpointing a ton for Mykel Kochenderfer's class, which is why I'm exploring JuliaBox).