55 Replies
Works for me on your domain
It loads fine for me, but in general there are a few differences between pages.dev and Custom Domains which can cause issues:
Auto-Minify Html can break frameworks like Nuxt.js, disable under Speed -> Optimization -> Content Optimizations -> Auto Minify. Rocket Loader can cause issues as well (and isn't going to help most modern websites), you can disable there as well.
If you are forcing cache with a Page Rule or Cache Rule, it can also break things
take a photo
not works for me in inconget browser
Chrome or Firefox?
Works fine in Firefox
is there diffrenece ?
Sometimes there can be browser specific issues, they both implement the specs in different ways. I tested Chrome now as well and it loads fine
try on chrome
I tested Chrome now as well and it loads fine
ok thanks
idk why but it works for me
Do you have a Page Rule or a Cache Rule setup to force caching on your custom domain? Those can break stuff
wdym ?
eh nvm I don't see any caching like that. I would guess cache of some level is related if it just suddenly started working
If it fails to load in the future, I would check your browser console for errors
how can i do that >
hmm, do what?
cache of some level is related
oh, you were saying it suddenly started working, right?
idk why but it works for me
only on another window
It works in Chrome, but not Brave?
works on brave but i have to cache my data first
i dont to do that everytime i change something
You mean whenever you make a change to the site, you have to clear your browser cache?
Do you see any errors in Console when it fails to load?
You mean whenever you make a change to the site, you have to clear your browser cache?yeah I have to I disabled dev-tools
oh you're talking about how you blocked them on the site?
a bit silly if you do something you don't even know how to get around lol
but you can just install https://chromewebstore.google.com/detail/mnmnmcmdkigakhlfkcdimghndnmomfeo
Anti Anti Debug
Be able to use developer tools again
yeah
you're using static js/css names, which is probably causing the issue here. They're being cached and preventing you from getting the updated versions
You can create a cache rule (Cf Dashboard -> go to your domain -> Caching -> Cache Rules -> New, or Magic Link: https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules/new), with Hostname eq pain.lol, disable cache, ex:
Pages already has cache under the hood, it's just the default cache settings that sometimes get in the way. If you were using a framework that auto-generated js/css files using file hashes in the name no issue, but since you're using static file names for your css/js, they get cached and keep the old version on updates
Probably didn't break for us since Cache is per browser and per Cloudflare location, and we had never visited the site before
did not understand anything but thanks for help
Pages.dev has no cache, pulls directly from Pages data store everytime
Your Custom Domain has default cache, not for html, but for specific assets like css/js
oh
i did that
but still
That looks better, no new caching now at least. If you purge browser cache now, do another update, do you still get stuck in the same issue? (Old browser cache would still stick around even after you apply that, it's not a magical retroactive change, Maybe do an update to remove the anti-dev tools blocking so you can actually see whats erroring in console lol)
on the same browser
it opens if inconget or another browser
lol that's a very different issue
i did not do anything
wonder if it's because you have Under Attack Mode enabled (btw why? You get unlimited static requests), and you hit f5 to resend the POST Request which actually hits your origin/pages this time
i just read ur msg then refresh the page
yea unlikely to be related to your other issues
I would disable Under Attack Mode/stop challenging every visitor and see if you don't hit it again. I think you just got hit by what I said, you hit F5 (it should warn you unless you bypassed it) and it resent the POST Request but it hit your origin this time (Pages) and not CF Challenge which caused that
i stopped that and still 405
nothing is instant when it comes to web browser and changes
give it at least a minute to propagate lol, and you'd need to close that tab at least and retry otherwise your browser would keep trying to resend
hmm yea that's what I'm talking about
Part of solving the challenge is a POST Request with the solve
it shows every time i do refresh
it opens now
but no moving text
Yea, it's because when you solve the challenge it sends a POST Request with the solve details. If you Refresh/F5 your browser is telling you "Hey, you POST Requested to get this page in the first place, refreshing could repeat the same action to get the same page", but the problem is Pages rejects POST Requests with a 405, and you're not hitting the challenge solve path since you already solved it.
Anyway, you fixed it by disabling challenging everyone, just needed to give it a sec to propagate & new tab
Anything errors/etc in Console?
i cant install extensions on brave
>
chrome as well
but new chrome profile can
Using a School PC or something?
mine
school pc has core duo and 1gb ram
then there's no reason why you shouldn't be able to install extensions, unless you purposefully blocked yourself
anyway I see this error in console
Uncaught SyntaxError: Identifier 'buttons' has already been declared (at buttoneventer71.js:1:1)It still loads the text but could be something to look at
i always do somethings i never know or understand what would it to
buttoneventer71.js is the buttons
check movelook.js
there's no errors from that js, and it looks ok
If your browser already has weird issues you don't understand, trying to fix something around it sounds like a bad starting point lol
It really could be just some weird edge-case JS Error or something along that track. Looking at the browser console is just by far the easiest way to find anything like that, disable the silly anti-dev tools stuff and then see. Otherwise it's just guessing as I can't repro it on my side even when I was testing with Brave
Ok thanks
