-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank page if local_names
are non trivial
#7221
Comments
Thank you for opening this issue @daskol. I was not able to reproduce this issue myself. Can you share the output of |
It's ArchLinux.
UPD I can access to |
Same issue here. Same versions. I downgraded the edited: in my case, if I open with |
I have a similar problem. The page won't load on chrome (it does on firefox and safari) and the server warns |
I have the same problem, but I did not modify anything regarding hostnames (I use On Chrome, page is blank with these errors in the console :
On Firefox, page loads but there are some errors in the console as well.
I am on MacOS (Ventura).
Hope this helps. |
facing the same issue, switching to 127.0.0.1 resolved the issue for me locally. |
This is almost surely a cache problem, which is very common with the jupyter server. (See this SO page for example.) Changing the host name from localhost to 127.0.0.1, or vice-versa , or using Firefox instead of Chrome, or vice-versa, works around the stale cache by using a different cache which may not be so stale. When a page is entirely constructed with javascript any error causes a blank page. Using a stale cached javascript file in place of the expected version of the file is almost certain to produce an undefined result somewhere in the jupyter javascript code base. The bug here, if there is one, is probably that jupyter re-uses its obfuscated javascript file names. Given that the file names are just numbers, one would think that when a file is changed its name could also be changed. Why not use uuids for filenames, instead of relatively small numbers? |
I also had the same issue (blank page, browser console reveals 404 with 6853.bundle.js) and it cost me a lot of time to find this issue and explanation. AFAICS, the issue here may be that the main page referencing the bundle is stale – after a shift-reload in Safari, the page suddenly worked, and the numbers of the loaded bundle files have changed. So changing the filename to UUIDs would not solve this problem, I am afraid. BTW: I am also on MacOS, but I think the exact environment may not be very relevant – I did reinstall my Jupyterlab installation via MacPorts and also tried switching from a python 3.11 environment to a python 3.12 one, but that did not change anything w.r.t. the browser frontend. In fact, I noticed that I could open the notebook via Jupyterlab and have it appear and work perfectly, but "detaching" the notebook again led me to the non-functioning notebook URL with the blank page. |
For future travellers, I also hit this because of a cached page after a notebook upgrade. |
Facing a similar issue, though my symptom is a syntax error in bundle.js (extraneous '}'). Using 127.0.0.1 instead of localhost resolved it. Perhaps related to ipv6 entries in /etc/hosts? |
As far as I know, the only way that using 127.0.0.1 instead of localhost could possibly resolve a syntax error in a javascript file is by causing the browser to switch to a different cache. Flushing the current cache without changing the host name should have the same effect. |
It does not work is
c.ServerApp.local_hostnames = ['localhost', 'jupyter']
in config. In brower console one can find this.The text was updated successfully, but these errors were encountered: