Any page under glitch.com (without subdomain) stuck on white screen

Glitch not loading on any browser?

A fetch to Google Analytics was the latest fetch request, responding with a 204 and Glitch is stuck loading nothing, whether an adblocker is on or not.

I’ve flushed my DNS, many times (most likely wouldn’t have worked) and restarted my router (unsure if that would have broken it)

I have also cleared cookies, but either way it doesn’t work on any browser (even on mobile)

But on other networks Glitch works completely fine.

It could just be my network, but just wanted to know, especially when glitch has worked before.
Sorry if this isn’t very clear, first forum post.

Are you running script blockers? If so, make sure to unblock glitch.com because it relies on scripts to even load the main page.

I’ve got no script blocker loaded, and everything seems to be loading except the Google Analytics part and when I try :

  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'G-VB0TBS64TF');

In the console, (I could be dumb, I really don’t know what I’m doing) it returns with undefined.

if this also happens on other browsers, I’m afraid it might be your network… does your network tab in the dev tools show it actually gets a page response (e.g. the glitch.com response is not an empty document - it shouldn’t, if you’re seeing gtag activity) and if you look at the JS requests, is there a _default.page.client.jsx.somehash.js? (because that should get loaded as part of page load, which in turn should then import 9 script sections for rendering the website)

Yes, it seems I have some script named default.page_client.jsx.hash.js getting requested, it’s giving a 200 OK code, but isn’t giving any JS back, but when I visit it in a normal page (like on a new tab in the browser) it responds, but the browser also seems to be indicating that it hasn’t finished loading. And I’m not getting a blank page, but only the document with its meta tags and default scripts to render. It might be my network, but otherwise is there any other way that it would have done this?

Never mind, this issue has been reoccurring on other sites, but by some random miracle, the router fixed itself.

could be its own internal DNS/cache invalidation - probably worth looking into whether its admin options include a flush command.

This issue has happened again, but in reality, it seems to be more of a router issue than it is a DNS issue (as I have switched from Wireline to Google to Cloudflare). From what I am seeing it is the router either overloaded (it is a relatively old router with a family of 4 always watching videos at least HD) or some sort of DNS/cache invalidation even though I swapped. Just wanted to put this in the post just in case somebody has the same problem.

1 Like