I am working on MacBook Pro 10.12.6. I downloaded the most recent Anaconda 5.2 distribution, with the Python 3.6 version.
I can launch the Jupyter Notebook from the command line without any problem, but it does not work from the Anaconda Navigator. I have the Jupyter Notebook version 5.6.0 in the Navigator. How can I get it to work?
19 Answers
I had the same issue on my computer. The issue was that a particular file went missing while updating the notebook. Please check the following file in the folder: /Users/your-name/.anaconda/navigator/scripts/notebook.sh and the corresponding output and error files called something like *out.txt and *err.txt The script notebook.sh should look like this:
#!/usr/bin/env bash source /Users/your-name/anaconda3/bin/activate /Users/your-name/anaconda3 open /Users/your-name/anaconda3/bin/jupyter_mac.command >/Users/your-name/.anaconda/navigator/scripts/notebook-out-1.txt 2>/Users/your-name/.anaconda/navigator/scripts/notebook-err-1.txt The error message said that the file jupyter_mac.command did not exist. This was why the notebook was not getting launched.
To fix it simply create this file, jupyter_mac.command , in the /Users/your-name/anaconda3/bin/ folder. The file is the following simple script :
#!/usr/bin/env bash DIR=$(dirname $0) $DIR/jupyter-notebook After saving this file, you may need to give it executable permission using the chmod +x command.
Voila! It's done.
3Launch it from cmd / terminal in cmd type jupyter notebook.
1I faced a similar issue running Anaconda on CentOS 7. The root cause was Anaconda was running as root user. I created an OS user for installing Anaconda. Since that, I can start the Jupyter Notebook (Yes, I know this is a very basic best practice) :)
You have more than one version of python on your computer so you should set up virtual environments for each version of python. It's very easy to do using Anaconda. Instructions are here and here. Once you have created your virtual environments then open Anaconda-Navigator. Once you've opened Navigator you'll see the following pane with a pull-down menu (as highlighted on the image).
From that pull-down menu select one of your virtual environments and try running Jupyter again.
5I resolved this using the following command, although note that it rolled back my (base) environment to the original state.
conda install --revision 1
Further discoveries:
I had the same behaviour as Marc in the comments above (it would launch from Environments but not the Home Page).
Clicking on Launch did actually start a notebook, it just didn't force a browser window to open; navigating to after doing so took me to it.
There is further discussion of the issue (at least the one I had) here:
- I had previously had problems with upgrading JupyterLab to 1.02, which I had succeeded in doing but perhaps something in that process resulted in the issue.
When I installed Anaconda I faced a similar problem. Jupyter notebook was not launching from Anaconda. I google searched and tried every piece of advice but nothing worked until I figured out that Jupyter notebook runs on localhost and I already have XAMPP. I use xampp as localhost to test my web pages. I uninstalled the xampp completely. Restart the computer, run the Anaconda and launched jupyter notebook. Voila, now it's running. Now when I installed Docker, I faced a similar problem. then I did the same. Uninstalled Anaconda in order to run Docker. It'd be my pleasure if it solves anyone's problem.
I had a custom path set as the base path for my jupyter notebook start-up folder. While taking some backup I had removed that folder. This was leading to Jupyter notebook and JupyterLab failing on start up. It worked fine after I fixed that path.
You just need to find the right version of anaconda I think. For me it works well when I downloaded a previous version, I was also facing the same issue. I could then launch jupyter from navigator itself.
1Few things to try
- Run the Navigator in admin mode (Right click the shortcut -> More -> Run as Administrator)
- Downgrade Jupyterlab to another version and upgrade it again (basically reinstalling)
The first one solved my issue.
