Blank Page for Spools and Filaments

Donkie / Spoolman

Keep track of your inventory of 3D-printer filament spools.

MIT License

993 stars 93 forks source link

Blank Page for Spools and Filaments #426

Open blackadar opened 3 months ago

blackadar commented 3 months ago

Describe the bug I've noticed that Spoolman can get into a state where clicking on Spools or Filaments from the home page just displays a blank page with browser errors in console.

To Reproduce Steps to reproduce the behavior:

Open Spoolman
Click Spools
Page may be blank

Expected behavior Page should load

Screenshots

Spoolman Host (please complete the following information):

Installation type: Docker
Installed version: Version 0.18.1 (306dbe4)
OS and Distro: Ubuntu
Database type: SQLite

Desktop (please complete the following information):

OS: Windows 11
Browser: Chrome and Edge on same computer

Additional context Docker container logs show no problems

blackadar commented 3 months ago

Also notable: I have this exposed to the internet behind Cloudflare Access under a domain name. When I access the service locally through the same browser that has the blank page, the Spools and Filaments page loads just fine.

Thinking this could either be cache related, or an interaction with Argo tunnels.

haynesdavid commented 3 months ago

Same issue, wont let me add, page goes blank.

filcuk commented 3 months ago

Same, also proxied through Cloudflare.
Worked fine on desktop, am on mobile now (Android, Firefox).
Screen seems to load for a split second before going white.

Will add more info when I can test from a desktop again.

haynesdavid commented 3 months ago

does the same on desktop too, i get the screen for 2 secconds also, before going white.

mwmason commented 3 months ago

Non-proxied, local network - get a blank page on Spool>Clone. I can Create a spool, from both Spools and Filaments. Filament>Clone works.

haynesdavid commented 3 months ago

Mine has resolved itself, not sure if an update has been push out somewhere, works across all devices now.

Donkie commented 3 months ago

Very strange issue. Would be interesting to see more console errors if it appears again.

It looks like one of the javascript files failed to download fully, and then it was stored in your browser's cache causing it to keep happening. Until your browser decided to download it again whereupon it now succeeds.

Maybe it has something to do with cloudflare?

blackadar commented 2 months ago

Happened again for me today, here's the console errors:

Let me know if anything else would be helpful :)