Hi, does anyone have an input on my issue? I am running Jupyter from Anaconda and updated everything to the latest. When I enter the notebook on port 8888 it never connects to the kernel and I cannot run the cells.
I followed every single guide I could read and tried changing ports, deleting adblocks, and downgrading tornado to 5.1.1 but still no luck.
Thanks!
Can you try upgrading to notebook 5.7.5, just to make sure it's not the tornado incompatibility?
See https://github.com/jupyter/notebook/issues/4439 and https://github.com/jupyter/notebook/pull/4449.
Thanks! Figured out my issue was that I didn't have notebook installed.
Oops, false alarm wasn't notebook, still doesn't work
Upgraded notebook to 5.7.5, still issue.
Combinations I've tried:
I got the same issue after downgrading jupyter notebook from 5.7.6 to 5.7.4 due to https://github.com/jupyter/notebook/issues/4467.
Indeed downgrading tornado down to 4.2.0 solved the issue.
downgrading to tornado 5.1.1 worked for me.
Simply downgrading tornado to 4.2.0 worked for me.
Upgrading tornado to the current version 6.0.4 fixed the issue for me.
upgraded notebook to 6.0.3 ,issue resolved
downgrading to tornado 5.1.1 worked for me.
This also worked for me - I had the latest tornado version 6.0.4 and the downgrade fixed the pblm
I had the same problem when opening bash notebooks (not with python notebooks). Downgrading to different versions of tornado didn't help. Could this problem be related to port access?
Thanks everyone, I downgraded tornado==5.1.1 to replaced 6.0.3 version, then jupyter (jupyter-notebook==5.6.0, jupyter core==4.6.1) works properly.
Likewise, I was unable to start a new Jupyterlab session because of the "replacing stale connection" error message, but then I fixed the problem by running "pip install tornado==5.1.1" to downgrade from the latest available version. This thread was helpful for solving that error, thank you.
Most helpful comment
I got the same issue after downgrading jupyter notebook from 5.7.6 to 5.7.4 due to https://github.com/jupyter/notebook/issues/4467.
Indeed downgrading tornado down to 4.2.0 solved the issue.