Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to launch notebook on Windows 10 Python 3.6 #3221

Closed
rahulptel opened this issue Jan 16, 2018 · 15 comments
Closed

Unable to launch notebook on Windows 10 Python 3.6 #3221

rahulptel opened this issue Jan 16, 2018 · 15 comments

Comments

@rahulptel
Copy link

I am working on Windows 10 machine and trying to run Jupyter Notebook over Python 3.6. However, I get stuck when starting Notebook. Below are the screenshot of cmd and chrome.

image

image

After a while, I start seeing 302 GET calls on cmd as below.

image

I have used Notebook with Python 3.5 and never faced such issues on the same machine. I have no clue why this is happening or how to solve the same. Any help would be much appreciated.

@dsblank
Copy link
Member

dsblank commented Jan 16, 2018

I notice that the security token doesn't match the token once it gets to the browser. You might copy and pasting the URL exactly into the browser directly.

@rahulptel
Copy link
Author

rahulptel commented Jan 16, 2018

Even when I copy paste the URL mentioned after the line Copy/paste this URL ... , I get 302 GET /?token=<token_mentioned_in_copy_paste_link> and nothing gets loaded eventually into the browser.

@OrangeBot
Copy link

OrangeBot commented Jan 17, 2018

Might I suggest a workaround? You can install linux subsystem for windows and run everything from there (https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/)
Also, I believe there were some issues with launch folder being hidden/starting with '.' - might that be the case?
Other option is that the problem is in your antivirus/firewall (even though it's localhost).. maybe add jupyter to exceptions?
Oh, and one standart windows advice that seem to work waay too often - reboot maybe? :)

@takluyver
Copy link
Member

We have seen some problems like this with security software, so if you've got any, try disabling it. Other things to try:

  • Change localhost in the URL to 127.0.0.1
  • If you've got a proxy set up, ensure that localhost and 127.0.0.1 don't go through the proxy.
  • Try copying the URL into a different browser.

I'm puzzled as to why the 302 codes start showing up if the browser can't connect.

@rahulptel
Copy link
Author

@takluyver

  1. I pinged at 127.0.0.1 instead of localhost which helped me render the notebook. However, I had the following issues.
  • The notebook always kept loading
  • The notebook behaved abnormally, not allowing to write.
  • 404 in cmd

image

image

  1. There are no proxies set up on my machine

  2. I turned off firewall and checked. The issue still persisted.

@OrangeBot
The launch folder is not hidden.

@takluyver
Copy link
Member

That's weird. I've got no idea what proptyt-compat is - I don't seem to have a file called that anywhere on my machine. How did you install Jupyter?

@rahulptel
Copy link
Author

I installed ipython and jupyter using pip.

@takluyver
Copy link
Member

Maybe try removing them and installing again? Sorry, I'm out of good ideas to try.

@rahulptel
Copy link
Author

Already tried the same natively and also in Anaconda environment. The problem still persists.

@DeltaCharlieAlpha
Copy link

The same thing was happening to me. Ended up being that nodejs didn't get installed. When I pip installed nodejs, it all worked.

@takluyver
Copy link
Member

Thats interesting. The notebook doesn't require nodejs if you install a prebuilt package (you need it to install from Github), and I'm pretty sure you can't install nodejs with pip. So I'm not sure what happened. But I'm glad you got it working!

@DeltaCharlieAlpha
Copy link

I definitely did some sort of nodejs install:

>pip install nodejs
Collecting nodejs
  Downloading nodejs-0.1.1.tar.gz
Collecting optional-django==0.1.0 (from nodejs)
  Downloading optional-django-0.1.0.tar.gz
Building wheels for collected packages: nodejs, optional-django
  Running setup.py bdist_wheel for nodejs ... done
  Stored in directory: C:\Users\david\AppData\Local\pip\Cache\wheels\5d\3e\10\4c849e533db93962941d161b7cf06f8990f39ad63dfcbb7012
  Running setup.py bdist_wheel for optional-django ... done
  Stored in directory: C:\Users\david\AppData\Local\pip\Cache\wheels\80\b6\20\3aeee7b395637ff94b2ca0cfbd0d9654136fc31b96748fc1d2
Successfully built nodejs optional-django
Installing collected packages: optional-django, nodejs
Successfully installed nodejs-0.1.1 optional-django-0.1.0

After that, it started working. I was also installing on a clean Windows 10 machine. I suspect there is something about installing into a very fresh Anaconda environment where Jupyter is one of the only things installed. I am also wondering based on some of the path names I see in if there is something specific about 64-bit Anaconda Windows 10 install that is making something not right.

@takluyver
Copy link
Member

There's a Python package called nodejs, but it's a binding for nodejs, not nodejs itself. It looks like it's unmaintained, and as far as I know we've never used it, so I don't know why it would make a difference. 😕

@DeltaCharlieAlpha
Copy link

The more I am looking into this, the more I think something is definitely subtly wrong on this clean install. I think the bogus nodejs install sucked in a dependency that didn't get installed correctly before. I suspect that I may have used a pip install where i should have used a conda install or vice versa.

If I can get a clean repro, I'll open a separate issue if it is actually an issue. Basically, I did a clean Anaconda install, then created one environment, then installed some basic libraries like Pandas, Numpy, Scikit Learn, etc, and Jupyter. I will see if I can get it down to a simple repro with Anaconda, 1 env, and Jupyter on a clean install.

@JasonWeill
Copy link
Collaborator

Closing this because Python 3.6 is now end of life (EOL) and Windows 10 reaches EOL in October 2025. Please open if you see this with a supported Python version.

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

No branches or pull requests

6 participants