# Jupyter Datascience Notebook Websocket ping timeout error
**URL:** https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090
**Category:** Notebook
**Tags:** jupyterlab, help-wanted
**Created:** [November 4, 2025, 3:03pm UTC](https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090 "2025-11-04T15:03:16Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Anik\_Du](https://discourse.jupyter.org/u/Anik_Du)
#### Post date: [November 4, 2025, 3:03pm UTC](https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090/1 "2025-11-04T15:03:16Z")
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}"`
---
### Author:  [@spookster](https://discourse.jupyter.org/u/spookster)
#### Post date: [November 27, 2025, 8:22pm UTC](https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090/2 "2025-11-27T20:22:51Z")
```auto
[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.
---
### Author:  [@Anik\_Du](https://discourse.jupyter.org/u/Anik_Du)
#### Post date: [December 9, 2025, 9:33am UTC](https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090/3 "2025-12-09T09:33:16Z")
But if you close the window, then the processes were running? In my case, once I closed the window, everything stopped.
---
### Author:  [@spookster](https://discourse.jupyter.org/u/spookster)
#### Post date: [December 9, 2025, 6:17pm UTC](https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090/4 "2025-12-09T18:17:00Z")
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.
---
### Author:  [@Anik\_Du](https://discourse.jupyter.org/u/Anik_Du)
#### Post date: [December 10, 2025, 9:33am UTC](https://discourse.jupyter.org/t/jupyter-datascience-notebook-websocket-ping-timeout-error/38090/5 "2025-12-10T09:33:15Z")
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.