JupyterLab Studio session keeps throwing "Server Connection Error" popup

Every time I enter a JupyterLab data studio session, after a while I keep getting these server connection error popups. These are a huge annoyance, especially since I don’t actually experience a drop out in my session - the terminal keeps running perfectly fine even if the popup is displayed.

I would love it if someone could point me towards some way to hide the popup!

Hi Michael,

Thanks for your message and welcome to the Seqera Community Forums! I’m sorry you’re experiencing these problems with Studios, and hopefully I can help you out.

Can you please let me know if this is the Cloud multi-tenant version of Studios, or if this is an Enterprise (self-installed) version of Studios? Could you also provide me with the container template image you are using (it will have a name like public.cr.seqera.io/platform/data-studio-jupyter:4.2.5-0.7. It’s important to provide the whole name because it contains both the version of Jupyter and also our Connect webserver.

Finally, can you provide details about your network environment? Are you inside a DMZ/firewalled space or do you have access to the public internet?

Thanks so much,
Rob N

Hi Rob, I suppose it’s the cloud version? I’m accessing it through my organisation’s seqera platform:
https://cloud.seqera.io/orgs/origin_sciences/workspaces/aws-prod/studios

the container template image I’m using is public.cr.seqera.io/platform/data-studio-jupyter:4.2.5-0.7

I’m not sure whether your last question is regarding my internet connection, or the internet connection on the instance. I have access to the public internet, yes. The same issue happens on my home wifi network.

The aws configuration however uses a whitelist of allowed URLs, and everything else is blocked.

Hi Michael - thanks for the added information - I just wanted to check you weren’t using an Enterprise deployment in your own (private) VPC. Looking now.

1 Like

Hi @mbeavitt,

Unfortunately we haven’t been able to reproduce this in our environments. We are about to roll out an update to the networking/proxying used in connecting to the Studio sessions running in the CE from the platform, which may resolve your problem. I’ll let you know once the platform update has been deployed and perhaps you can test again afterwards to see if your issue remains?

Warm regards,
Rob N

1 Like

Sure, sounds good!

It’s not the most reproducible problem in the world, and only seems to start happening 30-60 minutes after the studio starts up. Side note, there wouldn’t be a way of using SSH to access the studio in JupyterLab/Code/RStudio, or some other custom container template, would there?

Hi @mbeavitt,

This is a known feature request that is in our backlog. Please upvote if you would like to see this developed!

Warm regards,
Rob N

1 Like

Note, I found a solution to my annoying popup problem (in case anyone else finds this thread).

it crops up after around 30-60 minutes of use, but can be fixed by simply closing the browser tab/window, and clicking ‘connect’ from the data studios launch page to re-enter the session.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.