uh, hi everyone i’m really not
uh, hi everyone i’m really not knowledgeable on this stuff but i got the advanced certificate and a bunch of subdomains, but one of my workers, that i deployed with my Debian Raspberrypi with Vue3 and Vite is now pointing all of my subdomains to “fallback domain” which stupidly enough, is - by my own admission- my root domain.
now i’ve changed the fallback but cloudflare hasn’t validated the root cert in 48h, while all subdomains are instantly ready.
so i guess my question is, if my worker is removed, does it delete all subs?
i’m ashamed of it but that’s the worker and i’m able to configure it but idk why and when i made it
40 Replies
Can you clarify what you mean more? Fallback domain is a CF for SaaS term, are you using that? You have a root certificate -- your universal, not validating?
wait a sec
im totally new, rushed into this without looking at docs
damn that took long sorry
So the point of CF for SaaS is so you can point external domains into your own config. If you want to use Workers with CF for SaaS, you need a specific setup: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/
As Workers Routes see the request url as from the external hostname/domain, and not to your fallback.
Cloudflare Docs
Workers as your fallback origin · Cloudflare for Platforms docs
Learn how to use a Worker as the fallback origin for your SaaS zone.
uh
no im totally rivale
private*
If you just wanted to add your own websites to your worker, you can just use Worker Custom Domains under the Worker Settings -> Triggers tab
just wanted subdomains, gonna guess that’s not how its meant to be done
i am
Yea, you can just add them as Custom Domains to your Workers. CF For SaaS (Custom Hostnames) is a whole different use case lol
but its catching all of them
sounds like you made a worker route?
lemme see
Inside of the dashboard if you go to your website, it'd be under the "Worker Routes" tab
yes
that’s the one i posted
wydm? The one picture of the dashboard you posted as Custom Hostnames tab
no the hello world thing
sorry - that’s the worker:
// src/index.ts
var src_default = {
async fetch(request, env, ctx) {
return new Response("Hello World!");
}
};
export {
src_default as default
};
//# sourceMappingURL=index.js.map
is it the src_default
?
The thing you are trying to debug right now is why all your subdomains are pointing to your worker?
yea
that has nothing to do with the code itself
Check under "Worker Routes" tab in your website in Cloudflare
there’s one
what's the route?
but it points to the actual vue3vite site
like the default „you did it“
can you send a screenshot of the worker routes page, censoring anything if needed?
its inactive appearently
That's not your workers routes page
i dm´d u
you dm'd a screenshot of your pages custom domain. Pages Custom Domains cannot be wildcard and do not have the ability to capture requests to all subdomains, espec ones inactive
it was working when i started typing this though 😦
yea ok this is just wasting your time now sorry, but if you’re free i`d take any advice, the docs are gibberish to me
idk how to do this
You described a specific issue of a worker overmatching traffic, I told you what you could check. Worker Routes are the only way Workers could match all subdomains. I can't help you if you're unwilling to help yourself
im sorry man
youre right tho
shoulda asked youtube first
you're fine, I just can't help you without more info. If you're asking for generic advice, remove all your custom hostnames and ignore that section it's not going to help you. Remove any Worker Routes. You want Worker Custom Domains for Workers (under settings -> Triggers) and Pages Custom Domains for Pages. If your Pages Custom Domain is broken, remove it and readd it -- chances are you messed up the auto created dns record at some point. Pages is a project for serving full stack apps, Workers are serverless code, they both can sort of do the same tasks but slightly different.
You're making it harder for yourself then it needs to be lol
i sent you triggers
i don’t understand half that but ill try that thanks
i know i installed wrangler on a pi for this
im sure i could’ve just created a page
but i wouldn’t know how to configure that
there's no wildcard on that worker at least
what are you trying to do, exactly? Your end goal is to not have that subdomain use the worker?
nah i don’t even know how to use a worker
i thought it was for subdomains
:((
can i just delete this without harm?
Well what do you want on the
landing subdomain?
the worker? Yea, just remove all the custom domains and routes, you can always recreate, it's just a simple hello worldoriginally a homepage but then, my autism kicked in 12th gear and i went down some high level server document rabbithole
I'll be afk for a bit but if you could describe your end goal that would be easier. Workers are for serverless code, not just subdomains. You can do a lot with them though
so i forgot about that and added home and homepage
end goal: multiple subdomains for root
which i can manually configure as a noob
can’t find normal subdomains tab- if there’s one
like, serving what you have on your root, on various subdomains?