npx wrangler pages deploy is erroring for me, Cloudflare having API issues?
npx wrangler pages deploy ✘ [ERROR] Received a malformed response from the API
upstream connect error or disconnect/reset before headers. retried and the latest reset reason: conn... (length = 114)
GET /accounts/***/pages/projects/example -> 503 Service Unavailable
C
A
WA
D
wrangler secret put INNGEST_SIGNING_KEY doesn't make it available in the "environment variables", inngest sync fails and to put it in environment variables, I need to add it to wrangler.toml as "plain text" and deploy.WA
S
AA
R
wrangler dev --remote is it possible to only specify to run R2 remotely but other service to be run locally?R
J
MMJJCgetPlatformProxy() of wrangler?
R
M
B
Kwrangler dev if that's what you're trying to do?Kwrangler dev is Miniflare under the hood, and runs Workers
Jwrangler version in your package.json?Jnpx likes to be annoying with caching. What happens if you run npx wrangler@3.63.1 devJnpm create cloudflare@latest: https://developers.cloudflare.com/workers/get-started/guide/
JJnpm create cloudflare@latest. That'll ensure you get all the right dependencies and thingsJJminiflare directly for some specific purpose, or just run a script on Cloudflare Workers?Jwrangler dev is not how you'd invoke something like that - the miniflare API runs via node, but is not generally something 99% of users will need to touchJnpm create cloudflare@latest, it'll give you a basic foundation script and a dev script you can run via npm run dev, etc.JMiniflare like that via wrangler dev. The miniflare APIs are intended for much lower programattic access and is what wrangler uses under the hoodoJnode and not wrangler. But if this is for some test suite, the vitest integration is going to be your best option: https://developers.cloudflare.com/workers/testing/vitest-integration/✘ [ERROR] More than one account available but unable to select one in non-interactive mode.
Please set the appropriate `account_id` in your `wrangler.toml` file.
Available accounts are (`<name>`: `<account_id>`):wrangler secret put INNGEST_SIGNING_KEYPS D:\others\durable-objects-template> wrangler dev
⛅️ wrangler 3.63.1
-------------------
Your worker has access to the following bindings:
- Durable Objects:
- COUNTER: Counter
⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\wrangler-dist\cli.js:29765
throw a;
^
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at #assembleAndUpdateConfig (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:9178:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Mutex.runWith (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:3521:16) {
code: 'ERR_RUNTIME_FAILURE',
cause: undefined
}
Node.js v20.14.0wrangler dev --remote ERROR [unhandledRejection] connect ECONNREFUSED 127.0.0.1:63231 8:51:07 AMgetPlatformProxy()wrangler devwrangler devwrangler devwrangler devwranglerwranglerwranglerpackage.jsonnpxnpx wrangler@3.63.1 devnpm create cloudflare@latestnpm create cloudflare@latestnpm create cloudflare@latestminiflarenodenodenpm run devMiniflare[[d1_databases]]
binding = "DB"
database_name = "name"
database_id = "<uuid>"
migrations_dir = "./migrations"
[env.preview]
[[d1_databases]]
binding = "DB"
database_name = "name-preview"
database_id = "<uuid>"
migrations_dir = "./migrations"