The 2nd one doesn't seem to affect anything, but the first one seems correlated to these logs for fa
The 2nd one doesn't seem to affect anything, but the first one seems correlated to these logs for failed requests happening in production
19 Replies
hey guys, I have been struggling all day with a 525 error code. Trying to run a fetch request...that works in the sandbox of the api I am making a request to without issue, as well as in postman, but when running from my worker app....525. What's crazy is it was working not too long ago. That said, I am reading here: https://community.cloudflare.com/t/ssl-525-problem-when-calling-an-api-from-cloudflare-worker/356930/13 that the only solution is to create a ticket with cloudflare and that its related to the cloudflare not handling the ssl handshake properly. Is that true or does anybody here have any other suggestions? Thank you
Cloudflare Community
SSL 525 problem when calling an API from Cloudflare Worker
The problem was not when displaying the page, but rather when submitting the subscription form (calling Revue API with a POST request) The CF proxy was already turned on: And we can subscribe successfully with these 2 URLs (same deployment) https://cf.thisweekinreact.com/ https://this-week-in-react.pages.dev/ I did not change anything si...
i am on the free plan and now cloudflare seemed to remove technical support...so am I SOL..any cloudflare devs on here? This error comes when trying to reach an endpoint https://sandbox.dev.clover.com/v3/merchants/SOMEID/order_types
I’d recommend asking in #workers-help - this channel is just for the open-source runtime.
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
Working on it as we speak 🙂 (https://github.com/cloudflare/workers-sdk/tree/bcoll/vitest-pool-workers/packages/vitest-pool-workers) not quite ready for release yet but getting there. 🙂 Hoping to do an initial pre-release in the next few weeks, or early next year.
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
Hello!
Hope it's the right place to ask the question.
I'm trying to build a Rust wrapper for workerd. Do you have any suggestions? I want to know if workerd can worked by ffi link.
What are you hopeing for the wrapper to do? You might be better off emulating what
miniflare does, starting a sub process running workerd.I want to build a worker test framework that can purely written in rust.
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
We are actively looking into this. Here is the relevant GitHub issue link: https://github.com/cloudflare/workers-sdk/issues/4612
GitHub
🐛 BUG: workerd inspector process doesn't die · Issue #4612 · cloudf...
Which Cloudflare product(s) does this pertain to? Workers Runtime What version(s) of the tool(s) are you using? 3.21.0 What version of Node are you using? 18.17.1 What operating system are you usin...
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
pkill -KILL workerd is your friend for the time being 🙂Hi everyone,
I'm trying to understand how Cloudflare Workers supports Node.js APIs like
path, fs, and util in its runtime. I came across the NodeJsModuleContext::require(https://github.com/cloudflare/workerd/blob/f70094898726950428b959903e50dbcf2d7920ee/src/workerd/jsg/modules.c%2B%2B#L541) function in the code, but I'm not sure where it gets the files for these APIs or if it's using something specific to Node.js.
I'd appreciate it if someone could explain:
How are Node.js APIs like path, fs, and util implemented in Cloudflare Workers?
Where does the NodeJsModuleContext::require function find the files for these APIs?
Thank you in advance for your help!GitHub
workerd/src/workerd/jsg/modules.c++ at f70094898726950428b959903e50...
The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd
Every time I stop my local server, the process in the Terminal ends normally, but if I take a look at Activity Monitor on MacOS, there will be a running app called ‘workerd’ and cost much CPU usage. I have to kill it by Activity Monitor. If I start and stop a local server many times, there will be many workerds, all of them will cost much resources.
Is it a bug or there are some important settings I missed?
Hi everyone, hope your holidays are going well!
I'm building a worker that uses
O2O to Shopify and I'm curious how I can debug this locally.
I use fetch(request) which forwards the request on to the origin (Shopify) but locally it it won't know where the origin is. If I overwrite the url to fetch from Shopify it will hit my worker in production. How are others working around this w/ O2O?cc this channel about https://discord.com/channels/595317990191398933/891052295410835476/1190006589239869590
https://developers.cloudflare.com/workers/runtime-apis/performance/ says in local development, timers increment normally but the performance console in the browser doesn't work 😦