# Getting jupyterlab-prodigy to work on a google cloud platform VM

**URL:** <https://support.prodi.gy/t/getting-jupyterlab-prodigy-to-work-on-a-google-cloud-platform-vm/5877>\
**Category:** Uncategorized\
**Tags:** usage, jupyter, google-cloud\
**Created:** [August 25, 2022, 2:13pm UTC](https://support.prodi.gy/t/getting-jupyterlab-prodigy-to-work-on-a-google-cloud-platform-vm/5877 "2022-08-25T14:13:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\
**Post date:** [August 25, 2022, 6:26pm UTC](https://support.prodi.gy/t/getting-jupyterlab-prodigy-to-work-on-a-google-cloud-platform-vm/5877/4 "2022-08-25T18:26:12Z")

</div>

hi @sangersteel!

> [@sangersteel](#):
>
> I'm not using port 8080 because when I try to I get the error message:

I'm curious. Did you get this error serving Prodigy in jupyter or terminal?

Related, if you shut down jupyter, are you able to serve Prodigy on port 8080?

Ideally you should be able to run on port 8080. While in theory the port shouldn't matter if you update everything else, I think if we can figure out why the port is in use we could err on defaults.

I'm not sure what that root process is. Would it be possible to kill that process?

> <https://stackoverflow.com/questions/20691258/is-it-possible-in-python-to-kill-process-that-is-listening-on-specific-port-for>

However, others have found the problem is shutting down Prodigy in jupyter. Here's one approach:

> [@\[Errno 10048\] error while attempting to bind on address ('::1', 8081, 0, 0): only one usage of each socket address (protocol/network address/port) is normally permitted](https://support.prodi.gy/t/errno-10048-error-while-attempting-to-bind-on-address-1-8081-0-0-only-one-usage-of-each-socket-address-protocol-network-address-port-is-normally-permitted/2503/11):
>
> I think this comes down to how Jupyter / JupyterLab handles a server that's started in a cell and how it lets you terminate it. This thread has some approaches that might be more convenient than restarting the whole kernel:

Last three ideas... but I'm not confident they'll do anything:

- Any chance you're running NGINX? If so, it could be the reason:

> [@Prodigy bind error](https://support.prodi.gy/t/prodigy-bind-error/4659/3):
>
> Thanks Ines. I think I figured out the problem. I am trying to proxypass using nginx and I have prodigy installed in AZURE VM and my bind error was because nginx was running. When I stopped, nginx the prodigy ran fine but unable to proxy pass. So, what I need is how to proxy pass in a Azure VM? Thanks, Vaishnavi

> [@sangersteel](#):
>
> Tried opening it up in a separate browser tab

- You should open through the launcher (red circle), did you try this?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/2X/9/9b1ed6fffd3a5a554b0a5632fb22810599e0882c.jpeg)

- what version of jupyterlab are you running? It should be 2.0.0 +.

> [@Prodigy on AWS Sagemaker Notebooks](https://support.prodi.gy/t/prodigy-on-aws-sagemaker-notebooks/5236/3):
>
> Hi Ines, Thank you so much for that link! I think I found the issue. AWS Jupyterlabs has a version of 1.2.X. Sources state that they will be updating to 2.X.X some time later this year. Though Prodigy did install and labextension was active, when searching for "Open Prodigy" in commands, nothing was showing up.

Hopefully something above will help you but let us know if you still can't get things to work.

---

_[View the full topic](https://support.prodi.gy/t/getting-jupyterlab-prodigy-to-work-on-a-google-cloud-platform-vm/5877)._