Hello everyone,
I started glitch a couple of days ago, and I am struggling so much right now because the preview won’t show the result of the codes I put in. Can someone please tell me what has gone wrong? 
Thank you all!
The asset URLs seem to be CORBing but I don’t know if that’s just me!
Update: None of the asset URLs, even cdn.glitch.global, seem to not exist, this might be an issue on my end.
mine’s at least showing something. viewing on firefox. do y’all not resolve cdn.glitch.global? resolves to 151.101.66.132 here
1 Like
Had to manually resolve it, works for now. Which is a bit weird, I’m using my local DNS but switching to an alternate like 1.1.1.1 might fix this.
Hi @Yuna_Cho, just realized my reply might not have been that helpful!
The temporary fix I did for this was to point cdn.glitch.global in the hosts file in my OS to 151.101.66.132 (it’s like your computer doesn’t know where cdn.glitch.global is so we’re manually telling it where to look for!). On Windows, you can do that by editing the file called hosts in C:\Windows\System32\Drivers\etc\hosts by adding the following to the bottom of the file:
151.101.66.132 cdn.glitch.global
(On MacOS, the hosts file is located at /etc/hosts, and you might have to edit it via the terminal - sudo nano /etc/hosts).
Again, this is a temporary fix as you shouldn’t be doing this in the first place, but its a quick way to get your assets loading and continue working on your project. However, you’ll eventually want to look at why your DNS doesn’t resolve that domain — it could be your ISP censoring cdn.glitch.global or you might have to switch to an alternate DNS like 1.1.1.1.
1 Like
Thank you so much!! 
I will try that right now!
1 Like
Security note:
It is generally extremely dangerous to follow people’s advice when they tell you to update your hosts file, unless you can unambiguously confirm that the IP address they’re giving you is the actual IP address you should be using.
Your hosts file bypasses your DNS, and copying a rule could just as easily make your computer talk to a malicious server that’s pretending to be the service you think it is. Unless you know your way around networking, it is a fantastic way to get hacked.
And on a note for advising people to add rules to their hosts file: don’t tell people which IP to use, tell them to use a reputable tool to look up the IP for a service that doesn’t rely on their own DNS (or even better, tell them to use several to make sure they all agree on the IP). That way they can still bypass their DNS (in case a domain is blacklisted by their ISP/DNS) without having to blindly trust that the person giving them advice isn’t trying to trick them into accessing a malicious server.
3 Likes
to put this into perspective, it’s extremely dangerous, being up there with such antics as connecting to someone else’s wifi. they get to choose where your communications meant for some domain will go. possibly to themselves
glitch’s cdn uses HTTPS, which in ideal conditions prevents this from being catastrophic, whether you’re using wrong IP addresses or evil wifi. they can’t see what you were going to ask for from the cdn, they can’t see what the cdn sends back, and they can’t convince your computer that the cdn is giving you something else
I’m all for calling things extremely dangerous though
1 Like
my bad 
Noted - don’t listen to strangers telling you about IP addresses.
Here’s a WHOIS lookup that proves the IP is from Fastly, and not my remote server meant to return cat pictures for every request: Whois IP 151.101.66.132
1 Like
even if that was the ip for your remote server that returns cat pics of every request, it wouldn’t really work. modern browsers always enforce HTTPS, and will show a big huge red warning if a website doesn’t use it.
but still beware that cdn.glitch.global does NOT use HSTS (source: HSTS Preload List Submission and HSTS Preload List Submission), meaning it’s still possible that if someone’s using outdated software or disabled those warnings someone could (theoretically) force cdn.glitch.global to use http.