Open dburkhardt opened 6 years ago
Did you ever get this figured out? I'm having the same problem with Firefox. Running jupyter server on my workstation on Windows 10, connecting from laptop on local net. I'll be cruising along all day with no problems, and all of a sudden, my jupyter windows in Firefox will get flaky/slow, and then start refusing to connect at all. Chrome works fine on those same documents. Clearing the Firefox cache doesn't fix it. Restarting the kernel doesn't fix it. Restarting jupyter server doesn't fix it. Disabling all firewalls on all machines doesn't fix it. Disabling all Firefox add-ons doesn't fix it.
did this got fixed. i am struggling from months on this
I'm on Arch and still facing this issue, i had never faced this issue while on Windows. resetting cache doesn't fix the problem either, although opening incognito fixes, could it be because of a specific plugin ?
I recently updated two workstations (Arch) including jupyter-notebook 5.3.0-3 -> 5.3.0-4. Since then, I've been having a strange issue with using Jupyter via SSH port forwarding. If I try to open a notebook on Firefox (61.0.2) by connecting to localhost:8888, I get the standard "Connection Failed" error. Looking at the web console in Firefox I get the following output which makes me think it's a websocket error.
On the server side, I see this:
When I try to refresh the browser, I see no activity on the jupyter server. However, if I clear the cache in Firefox or if I open the same url in Safari or Chrome, it works. However, after a while (in Firefox at least) the same error comes up again, necessitating another cache refresh. I haven’t used Safari or Chrome for very long so I don’t know if the error pops up there as well for me.
What’s also interesting is this is reproducible on multiple machines in the building running Arch, but my colleague who uses Safari has not seen the error. Any idea where to look? I would usually expect a websocket issue to be a problem with the network, but the fact that a cache refresh fixes the problem sounds like something “bad” is getting cached.
Update 8/23: Today this happened again and I had to both refresh the cache on Firefox and restart the jupyter server. All the while jupyter is working fine through safari.