Jupyter Datascience Notebook Websocket ping timeout error

Notebook
,
1

Hello,

I have been using the Jupyter Datascience notebook deployed through ArgoCD + Kubernetes for 2 years. I never had an issue with this notebook until last Friday (31st October, 2025). Suddenly, the Kubernetes Pod started to throw this message:
Jupyter Server 2.17.0 is running at: ``http://localhost:8888/app_proxy/a219e992-a2a3-4175-8350-50b2b1e896a5/lab
The websocket_ping_timeout (90000) cannot be longer than the websocket_ping_interval (30000).

This is the first time I’ve seen this message, and when I ran some analysis, the notebook environment crashed.
Could you please tell me how to resolve this issue?
Was there a specific update that might have caused this WebSocket ping timeout error?

This is my Dockerfile heading:
FROM quay.io/jupyter/datascience-notebook
USER root
WORKDIR /home/jovyan/
USER $NB_UID

Below, I have pasted a snippet from the ArgoCD yaml file:
container-cmd: ["start-notebook.sh", "--NotebookApp.token=''", "--NotebookApp.base_url=#{proxy.getRuntimeValue('SHINYPROXY_PUBLIC_PATH')}"]
container-image: registry.XXXXX.XXX.XXX/XXX/XXX:latest
port: 8888
websocket-reconnection-mode: None
target-path: "#{proxy.getRuntimeValue('SHINYPROXY_PUBLIC_PATH')}"
heartbeat-timeout: -1
container-memory-request: "50Gi"
container-memory-limit: "200Gi"
container-cpu-request: "8"
container-cpu-limit: "24"
container-env:
USER: "#{proxy.userId}"

2 
[W 2025-11-27 20:18:00.643 ServerApp] The websocket_ping_timeout (90000) cannot be longer than the websocket_ping_interval (30000).
    Setting websocket_ping_timeout=30000

I have seen this warning on all my current installations of jupyterlab and tried to set the values manually in the config, starting with --ServerApp.websocket_ping_interval=30000 --ServerApp.websocket_ping_timeout=30000 but I could not get rid of the warning.
I did not notice any other problems though, apparently the value is set automatically to a working value.

3

But if you close the window, then the processes were running? In my case, once I closed the window, everything stopped.

4

yeah, jupyterlab is keeping everything running when i close the browser window, i am not using jupyterhub though, so it might have to do something on that part of the environment. that error message is probably a red herring.

5

Ok good to know. I will try again. Interestingly, if I use a different container like python-3.11, then all these error message and ping timeout disappears.