# Getting jupyterlab-prodigy to work on a google cloud platform VM **URL:** \ **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:** 6
**Author:** ![ljvmiranda921](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ljvmiranda921/32/3197_2.png) [@ljvmiranda921](https://support.prodi.gy/u/ljvmiranda921)\ **Post date:** [August 26, 2022, 12:00am UTC](https://support.prodi.gy/t/getting-jupyterlab-prodigy-to-work-on-a-google-cloud-platform-vm/5877/6 "2022-08-26T00:00:29Z")
Hi @sangersteel , my hunch is that in Vertex AI, the `8080` port is reserved by the `haveged` process as seen in your `ps aux` output. I am not sure what its purpose is exactly, but treat the `8080` port to be "reserved" for now. That's why you cannot start Prodigy because that address is already being used. So you might want to: - Change the `PRODIGY_PORT` when running Prodigy from `8080` into something not reserved (try `8888` or `8889`). Something like (or you can do so [via the `prodigy.json` file](https://prodi.gy/docs/install#config)): ```python PRODIGY_PORT=8888 prodigy ... ``` - Then configure the Jupyter lab extension so that it sees that port where Prodigy is running as mentioned here: > [@Localhost refused to connect](https://support.prodi.gy/t/localhost-refused-to-connect/5134/5): > > Hi @Joshmantova , to configure the Jupyterlab Prodigy extension, (in Jupyterlab) head to "Settings" \> "Advanced Settings Editor" \> "Prodigy Jupyter Extension" then update the prodigyConfig with the URL you're checking. It might also be better if you enable HTTP (or HTTPS) traffic in your Google Cloud VM (or the VM where the Vertex AI notebook runs). Not sure what you meant by this. Where do you see that "0.0.0.0":80 is being run? For reference, my prodigy.json config shows this: { "port": 8… To be sure, you might want to try this in a new VM in case you've shutdown some reserved processes. Just for a cleaner slate. Hope that helps! --- _[View the full topic](https://support.prodi.gy/t/getting-jupyterlab-prodigy-to-work-on-a-google-cloud-platform-vm/5877)._