🐛 BUG: MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. #4709
Comments
|
Just tried updating my node environment to Node.js v18.19.0. The issue persists. Mercifully, I have learned that npm start will do "just fine" for me, so I'm now able to continue my dev. yay. |
|
same for node 20, bare "hello-world" worker created by C3 cli. |
|
if you are using a mac, it likely has to do with folder permissions, make sure you give yourself full rights: chown R user folder etc. |
|
Works for me if i first kill any proccess on port 3000 and then run Using WSL |
|
@tdobson can you please re-run this command with can you please then provide these debug logs so we can investigate? thanks! |
lrapoport-cf
added
awaiting reporter response
|
I'm not @tdobson but I was running into the same thing w/ node 20.10.0 and Wrangler 3.26.0, here are my debug logs: logsInteresting – seems to be an SSL error? |
|
same here with miniflare README example code maybe related to cloudflare/workerd#2589? import { Miniflare } from "miniflare";
// Create a new Miniflare instance, starting a workerd server
const mf = new Miniflare({
script: `addEventListener("fetch", (event) => {
event.respondWith(new Response("Hello Miniflare!"));
})`,
});
// Send a request to the workerd server, the host is ignored
const response = await mf.dispatchFetch("http://localhost:8787/");
console.log(await response.text()); // Hello Miniflare!
// Cleanup Miniflare, shutting down the workerd server
await mf.dispose();zsh ❯ cat package.json
{
"name": "little-tooth-5b50",
"version": "0.0.0",
"private": true,
"scripts": {
"deploy": "wrangler deploy",
"dev": "wrangler dev",
"start": "wrangler dev"
},
"devDependencies": {
"wrangler": "^3.0.0"
}
}%
zsh ❯ cat test.mjs
import { Miniflare } from 'miniflare';
// Create a new Miniflare instance, starting a workerd server
const mf = new Miniflare({
script: `addEventListener("fetch", (event) => {
event.respondWith(new Response("Hello Miniflare!"));
})`,
});
// Send a request to the workerd server, the host is ignored
const response = await mf.dispatchFetch('http://localhost:8787/');
console.log(await response.text()); // Hello Miniflare!
// Cleanup Miniflare, shutting down the workerd server
await mf.dispose();
zsh ❯ node --version
v21.5.0
zsh ❯ node test.mjs
workerd/util/symbolizer.c++:96: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
*** Fatal uncaught kj::Exception: kj/compat/tls.c++:72: failed: OpenSSL error; message = error:0900006e:PEM routines:OPENSSL_internal:NO_START_LINE
stack: 104e9353b 104e952c3 10415c5a3 10415e6c3 104165deb 1041695b3 104167f03 104155147 10415976b 104159653 10415963b 106223883 106223bcb 10622232b 1062220fb 10414c1af 182fd50df
/Users/yqrashawn/workspace/home/little-tooth-5b50/node_modules/miniflare/dist/src/index.js:8480
throw new MiniflareCoreError(
^
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at #assembleAndUpdateConfig (/Users/yqrashawn/workspace/home/little-tooth-5b50/node_modules/miniflare/dist/src/index.js:8480:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Mutex.runWith (/Users/yqrashawn/workspace/home/little-tooth-5b50/node_modules/miniflare/dist/src/index.js:3405:16)
at async #waitForReady (/Users/yqrashawn/workspace/home/little-tooth-5b50/node_modules/miniflare/dist/src/index.js:8530:5)
at async Miniflare.dispatchFetch (/Users/yqrashawn/workspace/home/little-tooth-5b50/node_modules/miniflare/dist/src/index.js:8599:5)
at async file:///Users/yqrashawn/workspace/home/little-tooth-5b50/test.mjs:11:18 {
code: 'ERR_RUNTIME_FAILURE',
cause: undefined
}
Node.js v21.5.0 |
petebacondarwin
added
awaiting Cloudflare response
|
@tdobson could you try running |
penalosa
added
awaiting reporter response
|
@penalosa same shit... |
petebacondarwin
added
awaiting Cloudflare response
penalosa
added
awaiting reporter response
|
@penalosa yes it doas. but i'm sure the cert file is okay, is there anyway to check that? |
|
@a5r0n Could you try running |
|
I resolved the issue by disabling my IPv6 localhost in my |
|
I'm trying to trace a similar problem with 3.63.1 however I'm not using pages, just doing basic wrangler worker development. I've tried the solutions above regarding certs however I'm not using pages and everything runs fine with 3.57.1. With 3.63.1, one of the things logging identified is that when wrangler init did not create the .dev or .dev.vars files, which it seems to require now? However creating those files didn't resolve all of the issues. Log file attached. |
|
|
I had the same problem. I switched wrangler to wrangler 3.57.1 and it worked fine. |
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above. Node.js v20.11.0 i changed the version to 3.57.1 but still not working |
|
I believe you are experiencing an issue with a recent change to workerd that break on Windows 11? |
i have windows 10 can you provide me anything to fix this issue its been an houe now and i am not able to find something |
|
|
We have fixed this regression for nitro proxy using this method. |
How to do this on windows? |
|
I fixed this error by running |
|
@divofred |
You just have to change the compatibility date to "2024-05-12" in your wrangler.toml file |
|
umm.. is that a good practice ? |
The latest version of wrangler is buggy, so you are downgrading to the previous version. Since you are going back to 3.57.1, it is good practice to change the compatibility date. Hope this makes it clear |
|
oh.. so the problem is in Wrangler.. |
用这个可以了. |
|
I was also getting this error on Windows 10, with the latest wranger installed a few minutes ago via The error is quite vague and unhelpful, but a Google search led me here. I ran: ...and now the dev server is starting up correctly. |
|
I got the following error while using the latest version of Wrangler: |
|
Same error for me as Zaid mentioned above with 3.71.0. Downgrading to 3.57.1 works again on Win 10 |
|
Same error in Windows 10, even following steps from #4709 (comment) do not work in a hello world project: The latest version without the error is EDIT: Installing latest VS C++ Redistributable fixed the issue! 100% related to #6170 |
|
I am having the same issue on Fedora Linux 40. |
Working, Thanks a lot. |
|
|
Yes, you need to restart after installing VC Redist. |
and others
Which Cloudflare product(s) does this pertain to?
Pages, Workers Runtime, Wrangler core, Miniflare
What version(s) of the tool(s) are you using?
wrangler 3.22.3, miniflare version 3.20231218.1, workerd 1.20231218.0
What version of Node are you using?
v16.17.1
What operating system are you using?
Debian 12.4 (latest stable)
Describe the Bug
Hey I'm a junior developer (or maybe lower) and I followed
https://developers.cloudflare.com/pages/framework-guides/deploy-a-react-site/
to deploy a static React site to cloudflare pages. It worked brilliantly, and I was starting on the development (which, as a newbie, means enthusiastically testing out code that doesn't work).
Suddenly I started getting these errors when through up a development site.
I tried removing bits of code that might have caused it that I'd recently changed, and I don't think that's it.
At first glance, the error log reads like "oh, you already have something running on that port"
but if you look at the examples in error between those - you see what's happening:
I did a bit of digging into the locations of the error messages.
When I look at that file, it literally just says
In miniflare/dist/src/index.js, I tried adding a couple of console logs - and to me, that didn't add much useful, but maybe it did to you.
The project compiles and deploys to Cloudflare Pages just nicely.
From my point of view, it's frustrating because I don't care about serverside functions. It'd be a neat feature for the future, but I need to suck less at React before I want to play with that. If there's an obvious option I can use to disable it, I'd be hyped - this is my first project with Cloudflare Pages and I was enjoying it til this point.
I wonder if this is linked to this other bug report. I suspect not, but if it is - feel free to merge etc
Thanks for taking a look at this. Happy to provide other info etc.
If you want me to test something for you - I'd be happy to, and if you could dumb things down/give me the commands to run - I'd really appreciate it.
Please provide a link to a minimal reproduction
https://github.com/tdobson/cloudflare-wrangler-setup-problem-example
Please provide any relevant error logs
The text was updated successfully, but these errors were encountered: