When your setup is like: subdomain.customerdomain.com -> fallback.domain.com, Worker Routes sees th
When your setup is like:
subdomain.customerdomain.com -> fallback.domain.com, Worker Routes sees the incoming request as "subdomain.custerdomain.com/" and thus fallback.domain.com/* wouldn't match. You need a wildcard as per this guide: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/ just be careful to exclude your own subdomains first or use a dedicated domain/zone for cf for saas
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.
15 Replies
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
I am trying to troubleshoot an issue with my webpage and I am tryong to check the server logs but they logs won't display?
just says "waiting for logs..." but never populates
Are you using the new persistent logs (you'll have an [observability] section in your wrangler.toml if you do) or real-time logs?
And where are you running your Worker?
There’s no observability section in my toml file so I don’t think so
I have it currently in a folder on my desktop with the files for the web app I’m building
regarding your first item: adding check runs in github for Workers Builds is on our radar! we are working on it.
Are you running it locally when you are trying to see logs (hitting localhost), or are you accessing a URL like something.workers.dev?
locally
Anyone able to create an app with the new Remix worker template? I tried following https://developers.cloudflare.com/workers/frameworks/framework-guides/remix/ but the app it made seems to still be using pages. eg, the deploy command it gives is
wrangler pages deploy and I don't see an assets binding anywhere and it's still using @remix-run/cloudflare-pages...Cloudflare Docs
Remix | Cloudflare Workers docs
Create a Remix application and deploy it to Cloudflare Workers with Workers Assets.
I need myblogexample.pages.dev to be accessed by myblogexample.org but when I add the domain in the Pages settings, the message below appears
"After the update, visitors will no longer be able to access your site when visiting https://myblogexample.org."
I didn't understand
I want it to be accessed by myblogexample.org without displaying myblogexample.pages.dev
It sounds like you might already have a DNS Record for that domain? I think it is warning you that it would remove that DNS record
Yes
4 types:
R2 ( bucket )
CNAME ( www to myblogexample.org )
Worker ( subdomain.myblogexample.org )
Worker ( subdomainb.myblogexample.org )
Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
Yes, I'm saying the command in that doc
npm create cloudflare@latest my-remix-app -- --framework=remix --experimental generates that but it shouldn't.Unknown User•3w ago
Message Not Public
Sign In & Join Server To View
seems like still no mongo support?