Restart Kernel Keep looping on reconnecting
- Dominant language
- Jupyter Notebook
- Stars
- 13.3k
- Forks
- 5.8k
- Avg merge
- 6d 11h
- Merged PRs (30d)
- 7
Description
Hello,
I have some issue when Open notebook then click Restart kernel. Its can't connect to kernel and keep looping. This is only happened on Google Chrome. Tried on Firefox its working fine.
I used apache proxy configurations using the know-well-working config from [https://jupyterhub.readthedocs.io/en/stable/reference/config-proxy.html](https://jupyterhub.readthedocs.io/en/stable/reference/config-proxy.html)
Here the my config:
```
Listen 443
ServerName example.com
# configure SSL
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/example.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem
SSLProtocol All -SSLv2 -SSLv3
SSLOpenSSLConfCmd DHParameters /etc/ssl/certs/dhparam.pem
SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
# Use RewriteEngine to handle websocket connection upgrades
RewriteEngine On
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /jupyter/(.*) ws://192.168.1.13:4436/jupyter/$1 [P,L]
# preserve Host header to avoid cross-origin problems
ProxyPreserveHost on
# proxy to JupyterHub
ProxyPass http://192.168.1.13:4436/jupyter/
ProxyPassReverse http://192.168.1.13:4436/jupyter/
```
When i inspect elements and see the console on Google Chrome, i got this error message:
```
WebSocket connection to 'wss://www.example.com/jupyter/user/testuser/api/kernels/1a1409fb-2697-4005-bb4b-afc1f2507e60/channels?session_id=fe9bd559dd7c465f8f49af49571fa3b3' failed: One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 1
```
Kindly help about this issue.
Thank you
Contributor guide
Research direction
No repository file or test is named. Start with the Chrome console WebSocket error and the supplied Apache proxy configuration, then compare the reconnect behavior with Firefox. Done means identifying why Chrome rejects the kernel connection and documenting or implementing a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, jupyter-notebook
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100