is it possible to see the log of a deployed pages app?
is it possible to see the log of a deployed pages app?
Ei keep getting a 500 error and I don't know why 
Rmy understanding of the
I'm, personally, still unclear on what you need done that can't be done with a well-placed
--yarn devwrangler pages devI'm, personally, still unclear on what you need done that can't be done with a well-placed
watchCloudflare Docs
Create, develop, and deploy your Cloudflare Workers with Wrangler commands.
HIIRC they removed it because it had bad UX. It still couldn't run Workers, so all you would have is what
yarn devThe new recommendation once it lands in more frameworks is to use the new Vite Environments API, which means that frameworks can now run their dev server in
workerd
Wwrangler pages deployment tail
Si could see d1 replication next month on dev week. containers? maybe not
RWeird question... when making a new Workers project from a github repository, what if I don't want to deploy to workers.dev?
Reason being, it seems that tons of bots just watch for deployments to workers.dev and jump at the opportunity to ping your Worker. :/
Reason being, it seems that tons of bots just watch for deployments to workers.dev and jump at the opportunity to ping your Worker. :/
ZYou can disable your workers.dev domain before you deploy in your
wrangler.toml/jsonc
CBots should only be from the cert. issuance for *.workername.subdomain.workers.dev anyway, if you deploy and snipe off the workers.dev quick off, should avoid it
Cfor functions?
Cthere's frameworks which can emulate that
Cyea, eh, I imagine it's one of those things where the vast majority of people use frameworks anyway
I wonder how they're going to try to make that migrate to workers assets
I wonder how they're going to try to make that migrate to workers assets
Cthey said in the blog post:
We plan to bridge the gaps between Workers and Pages and provide ways to migrate your Pages projects to Workers.
Cidk how you'd migrate file path routing without having something to deal with it
Cmaybe just a compat framework or something lol
pages-legacy-routing
HYou know what would be a real cool and dumb feature for custom domains? Pre-warming. I.e., you activate the domain, issue the cert, but block every request for the first n-minutes
Clol I think you can already do that yourself
CI just delete every cert Workers Custom Domains issue before they get a chance to be issued, and either place them on 1st level or use a *.workers.domain.com wildcard acm cert
AHey like i have hosted my vite react app in cloudflare pages and honobackend in the cf workers and there is an issue like when i login the cookie is not present i chrome cookies but in request header it is availabe and also like when i try to logout the cookie is still on the request header and unable to logout on dev no issues. after some reserch i have found like if the front end and backend have different domains like "pages.dev" and "worker.dev" as browser will not save cookie . so is there is a fix for it like without custom domain on dev side the vite proxy works but on production it will not any fix for it
HI mean the opposite, like in cases where you do want the cert, but don’t want the requests
RI like this idea very much. I do think it could help stave off a lot of spurious traffic. I know that it will eventually just result in this pattern being learned, too, but I think its worth exploring
RI might be misunderstanding but this seems like a CORS issue?
I have setup a system that used a custom domain on Pages as the origin and had a Worker in front of it, but they had the same top level domain. I don't think it would have mattered, though, since IIRC even subdomains are normally considered separate domains unless you use CORS.
I have setup a system that used a custom domain on Pages as the origin and had a Worker in front of it, but they had the same top level domain. I don't think it would have mattered, though, since IIRC even subdomains are normally considered separate domains unless you use CORS.
Ai have fixed the cors issue and still this cookie issues persits as on login on application section of chrome doesn't include cookie but on request header will be having it and when logout nothing is happening
Aand no cors issue is showing on consolelog
NDoes anybody know the best way to send transactional emails from Cloudflare Workers?
NI see MailChannels, but it shows that it stopped sending from Workers last year.
JSendGrid, SES, Postmark, etc. Really anything except MailChannels
BI recently jumped from SendGrid to ZeptoMail. Quite a good experience so far, better support experience, and I like their pricing model too. 
NThank you very much, I will go take a look at all of these.
Mlooks like this no longer works with wrangler v4
Mno wait... its
deploy --no-bundle thats failing.it does upload the worker, but after it exits with non-zero exit code. logs show thisWCan you try with npm?
Mi just slapped a
(bunx wrangler ... || true) around it. it throws the same error regardless of command, but it seems to work
Eanyone else pages nextjs just failing for no reasn?
EEW▲ You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 >= 20.0.0" is required.
Wit says the reason
QIs there not a bug report channel? The timestamps on the Workers Logs page are wrong. 21 minutes ago was not March 5th.
Wfix is being released monday
Mfor cloudflare tunnels exposed via public dns, how can i block any connections not from my worker zone? i know i need to write a rule to check
without this rule in place, im seeing a lot of stray requests hitting my http server
cf.worker.upstream_zone but not sure wherewithout this rule in place, im seeing a lot of stray requests hitting my http server
HCloudflare Docs
Custom rules allow you to control incoming traffic by filtering requests to a zone. You can perform actions like Block or Managed Challenge on incoming requests according to rules you define.
Mis there another option? i shouldn't have to "talk to a (sales) expert" just to write a single, simple firewall rule
Moh thats just for account-level WAF, not the same as zøne level WAF?
Min the docs, does this rule also allow non-worker requests?
if i wanted to allow only requests from workers in my zone, is this one more effective?
if i wanted to allow only requests from workers in my zone, is this one more effective?
CI believe you could do something like
cf.worker.upstream_zone != "customer-zone.com"Mmuch cleaner, cheers 
