-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Jupyter Notebook won't start due to ports being already in use #3495
Comments
That's weird. If you run |
Here's the output.
|
Nope, that doesn't show anything relevant. Is there anything odd about your network setup, or any security software you might have installed on it? |
No, there is nothing tinkered at my system. It's almost freshed install Linux Mint 18.3. |
I'm out of ideas, sorry 😕 |
Oh, that’s unfortunate. I even installed the launchpad through anaconda but when I run it, it stucks on “loading available apps” :/ |
It's possible that Anaconda launchpad (is that the same as navigator?) is doing something similar, looking for a local port to bind. I'm not familiar with that, though, so it might be something else entirely. |
Hi, my Jupyter Notebook shows it running on Port 8889 but using Here are the steps I've taken: To connect I use:
I then run
/home/cordun/anaconda2/bin/jupyter
[I 21:11:09.130 NotebookApp] Writing notebook server cookie secret to /run/user/1031/jupyter/notebook_cookie_secret Error message upon opening in Chrome:
But at It does connect and prompts me for a password. I already set my My .config:
running:
returns the following: State Recv-Q Send-Q Local Address:Port Peer Address:Port Opening up Should I uncomment a specific setting in the .config file? History: Everything ran smoothly until a few days ago when I Thank you for any guidance on how to solve this issue. Currently I'm unable to open any Jupyter Notebook. |
|
Thank you @takluyver - Jupyter opened and now works on port 8889. What I seemed to have been doing wrong was the incorrect SSH tunnel/forwarding syntax.
Was the right way. Then I called the port directly:
Thank you for your guidance. And yes, my mistake - it was a typo. I was using ':' not '/'. But thanks for pointing that out. Another question I have is how can I "kill" the other notebook running on port 8888? I had looked up commands on how to see what's running on other ports via the By the way, the notebook at port 8889 successfully accepted my new password. Thanks again. |
On the system that it's running on, |
After launching the jupyter notebook for the first time, I am continuously facing problem in launching it. Everytime I run it through my conda navigator it gives this error: [I 11:54:52.606 NotebookApp] The port 8888 is already in use, trying another port. During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
I faced exact the same problem. Using --ip=0.0.0.0 solved it: jupyter notebook --ip=0.0.0.0 --port=8888 |
I had similar issues. This might occur when you have installed some other conflicting program into your system. Such as, I installed PyLucene where many programs were installed in order to get it done. This is how I solved my problem. First check your pip version
|
I had the same issue and was able to resolve it with --ip=0.0.0.0. |
Thank you. It works! |
i had the same problem and for me it was my messed up /ets/hosts file. ive had 127.0.0.1 localhost and 0.0.0.0 localhost inside it, if providing something with --ip=x.x.x.x fixes the problem, also pay attention to /etc/hosts file. |
I'm going to close this issue based on the recent history of helpful responses and successes. Thank you to everyone. |
I'm having issue while launching jupyter notebook from anaconda navigator. |
I'm having the issuse of launching jupyter notebook from anaconda navigator it shows produced error |
I had similar issues where it tried all ports and it said none of the ports are available. This worked for me 👍 |
Thank you
…On Fri, Jun 19, 2020, 09:56 Sumanth Reddy ***@***.***> wrote:
i had the same problem and for me it was my messed up /ets/hosts file. ive
had 127.0.0.1 localhost and 0.0.0.0 localhost inside it, if providing
something with --ip=x.x.x.x fixes the problem, also pay attention to
/etc/hosts file.
This worked for me 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3495 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AORRLTOGWHQOJBWIAZRMOKLRXLSGHANCNFSM4EY3IMLQ>
.
|
Hey Github, I face the same error pls share any perfect solution for this [W 22:50:19.358 NotebookApp] Permission to listen on port 8888 denied. |
This worked but on another port 8890, the other ports 8888 and 8889 are still in use. Could access the notebook with the link |
I'm somewhat able to troubleshoot the problem... Hope, this helps... If somebody know any other solutions, please let me know..... |
Uh.. are you using the aws EC2 service? If so, restart the instance. Hope, this helps...too |
Hi, can anyone tell me how to fix the problem using this method? Thanks a lot. |
I was having this exact same issue. Running:
fixed my problem |
Tried all of the above and still can't use jupyter any more. |
This cleared it for me. it is an issue with windows/hyperv
|
Thanks, It worked for me! |
https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/default-dynamic-port-range-tcpip-chang |
Same error I was facing, One of the issues with your antivirus installed... |
It helped |
Thanks it worked for me too !!!! |
谢谢它也对我有用!!! |
我也碰到了这个问题,再使用jupyter notebook --ip 0.0.0.0或者实际ip时都可以正常启动, 但使用jupyter notebook --ip localhosts时,出现了同样的端口被占用问题, 查看hosts文件里后发现是我把0.0.0.0指向了localhost,去掉这个ip映射就好了 |
Fresh install of anaconda 3.6 on Linux Mint. After restarting my computer I tried running a notebook server using the command
which returns the following error:
Is there any suggestion on how to resolve this issue?
I even tried providing a custom port with the --port flag but still the same issue.
The text was updated successfully, but these errors were encountered: