# Clicking on New -\>Python3 in Jupyter notedbook (interactive app) gives Proxy Error message

**URL:** <https://discourse.openondemand.org/t/clicking-on-new-python3-in-jupyter-notedbook-interactive-app-gives-proxy-error-message/1612>\
**Category:** Get Help\
**Tags:** question\
**Created:** [August 2, 2021, 1:07pm UTC](https://discourse.openondemand.org/t/clicking-on-new-python3-in-jupyter-notedbook-interactive-app-gives-proxy-error-message/1612 "2021-08-02T13:07:40Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![travert](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/travert/32/3074_2.png) [@travert](https://discourse.openondemand.org/u/travert)\
**Post date:** [August 4, 2021, 4:29pm UTC](https://discourse.openondemand.org/t/clicking-on-new-python3-in-jupyter-notedbook-interactive-app-gives-proxy-error-message/1612/21 "2021-08-04T16:29:09Z")

</div>

So, as a test to see if another kernel of python3 with a different name will work, could you follow the instructions here:

> **[HOWTO: Use a Conda/Virtual Environment With Jupyter](https://www.osc.edu/resources/getting_started/howto/howto_use_a_condavirtual_environment_with_jupyter)**
>
> Conda/Virtual environments must be installed on JupyterLab or Jupyter Notebook prior to use. Whereas older versions of Conda automatically installed a Jupyter kernel, users must now manually perform the installation process. To perform the...

To setup another `python3` kernel with a different name, the `useful-project-name` in the example, and see what happens when you try to run a notebook with that new kernel.

Because if that runs fine, there is something wrong with the particular `python 3` kernel that the notebook is trying to use. In which case you should remove it and replace with a fresh `python3`.

---

<div class="post-metadata">

**Author:** ![skelting1](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/skelting1/32/940_2.png) [@skelting1](https://discourse.openondemand.org/u/skelting1)\
**Post date:** [September 15, 2021, 1:41pm UTC](https://discourse.openondemand.org/t/clicking-on-new-python3-in-jupyter-notedbook-interactive-app-gives-proxy-error-message/1612/22 "2021-09-15T13:41:32Z")

</div>

We went through this exact error for our system as well.

Upon testing JupyterLab by it itself, we found it was just outright crashing when we made a new notebook. A fresh install of the newest version did not resolve the issue.

In our case, we recently updated our storage from CentOS6 to CentOS7. We did not change any of the mount option on our headnode or compute nodes. For some odd reason, using an NSFv3 mount was the root cause of the issue. We removed the NSFv3 option from the fstab, and let our system default to NSFv4. Afterwards, JupyterLab began working like a charm!

As a word of warning if this is indeed your problem, ACLs changed in NSFv4. It’s no longer exported by rpc and requires a special utility to manage. There is some translation available to help migrate, and a chunk of documentation on the utilities.

---

<div class="post-metadata">

**Author:** ![westburg.2](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@westburg.2](https://discourse.openondemand.org/u/westburg.2)\
**Post date:** [May 26, 2022, 3:42pm UTC](https://discourse.openondemand.org/t/clicking-on-new-python3-in-jupyter-notedbook-interactive-app-gives-proxy-error-message/1612/23 "2022-05-26T15:42:45Z")

</div>



[Previous page](https://discourse.openondemand.org/t/clicking-on-new-python3-in-jupyter-notedbook-interactive-app-gives-proxy-error-message/1612.md?page=1)