Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Make deep learning VM JupyterLab publicly available?

I was able to create a deep learning VM from the marketplace and when I open up the VM instance in the Console I see a metadata tag called `proxy-url` which has a format like `https://[alphanumeric string]-dot-us-central1.notebooks.googleusercontent.com/lab`

Clicking on that link takes me to a JupyterLab UI that is running on my VM. Amazing! Unfortunately, when I try opening that link on an incognito window, I'm asked to sign in. If I sign in, I get a 403 forbidden.

My question now is, how can I make that link available to someone else?

Solved Solved
0 2 417
2 ACCEPTED SOLUTIONS

Hi gopalv

As far as I understand, it sounds like your Jupyter Notebook isn't configured for remote access. since it doesn't work when trying to access it from the incognito window with a 403 error.

You can try looking here and here for details on how to set up a publicly accessible/remote access notebook. There are additional troubleshooting steps in our documentation here as well.

Hope this helps!

View solution in original post

I think the problem was that I had selected the option to enable access via URL and this only grants access to users who are Editors or Owners in the workspace (step 9 here) 

 

 


When I created a new VM and left this option unchecked, I was able to use my public SSH cert to get access.

View solution in original post

2 REPLIES 2

Hi gopalv

As far as I understand, it sounds like your Jupyter Notebook isn't configured for remote access. since it doesn't work when trying to access it from the incognito window with a 403 error.

You can try looking here and here for details on how to set up a publicly accessible/remote access notebook. There are additional troubleshooting steps in our documentation here as well.

Hope this helps!

I think the problem was that I had selected the option to enable access via URL and this only grants access to users who are Editors or Owners in the workspace (step 9 here) 

 

 


When I created a new VM and left this option unchecked, I was able to use my public SSH cert to get access.