workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
š¦rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
ā”instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
š¤turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
Proxying console logs
Has anyone experimented with proxying the global
console to e.g. capture the console logs?What Auth solution providers are people
What Auth solution providers are people using with workers and how easy/difficult are they to work with? Curious what other are using and what the experience has been like.
Cloudflare subdomain redirecting to main domain
Any idea why my subdomain keeps redirecting to main domain? Opened a cloudflare ticket, been 14 days and no response
https://fr.ellasbubbles.ca/ -> Keeps redirecting to https://ellasbubbles.com/
My research makes it seem like its a problem with the SSL certificate...Websocket issue with Flexible SSL
Hey everybody! I'm new here and could use some guidance. I've been using Cloudflare for a while now, but I haven't delved into setting up Websockets before. My goal is to avoid direct connections to my origin server and keep its IP address protected. Currently, I'm using the Cloudflare Flexible SSL method, where clients connect to Cloudflare on port 443 secured by Cloudflare's SSL certificate. On my origin server, I only have Apache listening on port 80, and I don't have an SSL certificate installed to reduce the SSL overhead.
Recently, I created a new WebSocket app and am attempting to set it up to work through Cloudflare. However, I'm facing some difficulties. I've confirmed that Websockets are enabled in the network settings of my Cloudflare panel, and I've also verified that the WebSocket server is running and the listening port is open. I've tried using port 8080, and it's worth noting that the current WebSocket server I'm using doesn't support SSL connections.
The issue I'm facing is that when I try to connect to the WebSocket using my domain name, I receive a "connection failed" message. To investigate further, I performed a tcpdump on my origin server but didn't see any incoming requests from Cloudflare.
I would greatly appreciate any help or guidance you can provide. I'm eager to learn from your experiences. Thank you!...
If you get a status code of 200 back
If you get a status code of 200 back from our API, it means your message has been queued for delivery. Whether or not it actually gets delivered is something you can only determine by watching your inbox for a non-delivery receipt. We will send an NDR if the message bounces for some reason. Otherwise, you can assume it got delivered. We only queue for up to six hours, so that's the maximum time you will have to wait to get an NDR.
I am super new to JS and webtech in
I am super new to JS, and webtech in general (i'm a security engineer flailing helplessly) and am really struggling with how i could implement auth for pages hosted on cloudflare. From what i can tell, i might be able to use workers, but really struggling to find good examples to crib from.
The gist of what i'm doing is:
I create a page for each user, it contains mostly similar content, with like 2-3 personalization tokens. Nothing fancy, just text, images, videos and one or two embedded components. It seemed smart to just use static pages, but I can't for the life of me get the idea of using workers and middleware to allow users to auth with a magic link, or something else simple like that. I'm really trying to avoid providing basic auth/shared passwords if i can manage it. ...
``` const cache key c req url
``` const cache_key = c.req.url
let response = await caches.default.match(cache_key)
if (response) {...
We use Wrangler 3 and the Sentry CLI to
We use Wrangler 3 and the Sentry CLI to push the
dist folder generated by wrangler deploy --outdir=./dist to sentry as a release. Some errors do seem to point to the right file, others don't for some reason, also stuff like deduplication and grouping don't always work like we expect to yet.CPU fail
this either needs some good debugging utilities or serious rework.. suddenly all ci systems failing without reason is not great.
maaan i was about to try out workers
maaan i was about to try out workers with some discord rich presence biz, but i just saw that discord intentionally blocks socket connections from CF workers. a tragedy
I m getting
I'm getting
```bash
service core:user:chainfuseapi-plugins-rss2json: Uncaught Error: Dynamic require of "node:stream" is not supported
at index.js:1:383
at index.js:18:4350...
has anyone managed to get itty router v4
has anyone managed to get itty-router v4 types working with cloudflare's worker types? the main issue appears to be that both libraries have bespoke typings for
Request and Responsefancy 100 agree there is something in
<a:fancy_100:1092953135552667708>% agree, there is something in the works that means inactive DOs won't get charged
The plugin documentation
The plugin documentation?
You're using normal git integration, added the html contact form as is (needs the
data-static-form-name attribute to be set to anything), you have the functions folder in your root (not in your output directory) with the _middleware.ts file, you can see in build logs under the functions tab, the middleware listed under route configuration?...but i get a warning abt cloudflared when
but i get a warning abt cloudflared when running a normal apt update anyway lol