fonsp / Pluto.jl

🎈 Simple reactive notebooks for Julia
https://plutojl.org/
MIT License
4.91k stars 284 forks source link

Blank screen issues #2714

Open tamasgal opened 7 months ago

tamasgal commented 7 months ago

This might be partly related to https://github.com/fonsp/Pluto.jl/issues/1583

I started to use Pluto again and created a few notebooks for teaching. Today, when accessing the Pluto web UI, I only get a blank screen and the page is stuck at loading. Chrome displays sometimes "localhost took too long to respond" or simply hangs with a blank page.

I am using

  [c3e4b0f8] Pluto v0.19.32
  [7f904dfe] PlutoUI v0.7.53

with Julia 1.9.3 on macOS M1.

I tried the following:

I don't see any errors in the Julia session and I also don't see any errors in the web developer console (nothing is loaded).

In my Notebooks I was using CairioMakie and Javis / JavisNB.

Safari on macOS does not work at all.

How should this be debugged?

Screenshot 2023-11-15 at 10 14 26 Screenshot 2023-11-15 at 10 14 35
tamasgal commented 7 months ago

I tried all kinds of stuff, no way to get Pluto running. Is there any way to turn on verbose mode or something?

I even updated macOS to the latest Ventura version (13.6.1) and also deleted the whole ~/.julia directory and reinstalled everything. This issue is very likely OS related and I cannot believe I am the only one who faces this.

I don't have any VPN or weird network setup, also no firewall or proxy. Jupyter works flawlessly btw. and many other server-based apps either.

Screenshot 2023-11-15 at 21 23 30

tamasgal commented 7 months ago

OK got it finally!

It was an HSTS policy which probably got its way to the localhost local storage in several browsers, probably from another web application which I ran through localhost. Phew...

For Safari, delete the local data under Settings/Privacy

Screenshot 2023-11-15 at 21 43 02

tamasgal commented 1 week ago

I again hit this issue (twice today). The only way to solve it was again deleting the full local cache (which also deletes the notebook history). I think we need a solution for this. I still don't know how this happens...