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
Has anyone here ever experienced issues
wrangler dev --experimental-local
instance on a local network ip?for clarity `unstable dev` is a wrapper
unstable_dev
is a wrapper around wrangler dev
, so wrangler dev --local
corresponds to local: true
in unstable_dev
Hey there how do you access R2 bindings
unstable_dev
local: true mode? It seems it's creating fake R2 bindings.Hey there anyone using local false with
i m unable to authenticate with wrangler
wrangler login
and approve everything just fine, but when it comes to running something like wrangler dev
, i get authentication errors such as Authentication error [code: 10000]
.
i manually created an API token via the dashboard, and if i use that with the CLOUDFLARE_API_TOKEN
environment variable, then things work! i wonder if the token generated by wrangler login
is invalid somehow?...Error: Could not proxy request: TypeError: fetch failed
[pages:err] Error: Could not proxy request: TypeError: fetch failed
error all of a sudden. I thought this is an issue with the new version and so downgraded to the version (2.9.1) which I was using earlier but issue still persists. Changed the port of vite dev server to make sure that the port number is not in use already but issue still remains. What could be the reason behind this issue?and `jq` can extract super easily
jq
can extract super easily:
curl_prod accounts/:account/pages/projects/:pages-project/deployments -s | jq '.result[0].deployment_trigger.metadata.commit_hash
curl_prod accounts/:account/pages/projects/:pages-project/deployments -s | jq '.result[0].deployment_trigger.metadata.commit_hash
I m running into an `Authentication
Authentication error [code: 10000]
error when executing wrangler dev
@ 2.8.1
and I am wondering if I have the correct permission scopes to run the wrangler v2 dev command, can someone confirm if this is sufficient scoped permissions?
- account (read)
- user (read)
- workers (write)...
If I do that I can t run wrangler it s
yarn wrangler
, which I can't do from outside the project)It s really hard to say I posted https
Logpush Worker
logpush = true
to your wrangler.toml
Then head to the logpush dash: https://dash.cloudflare.com/?to=/:account/logs
And create a job
...Hi how would I go about using wrangler
Hello one my workers suddenly can t be
workers.api.error.internal_server [code: 10002]
error. There's no error at compile time, and the wrangler.toml
file has been untouched for 2 weeks (git is my witness). Last time I published it was 2 days ago, and now with reversed changes I still can't publish it.
So is it just the Cloudflare's API going through some troubles (and status page is up to date), or potentially breaking changes introduced to wrangler?...Basically with Pages you would only pay
Invalid regexp error
wrangler secret put raw mode error
echo "VALUE" | wrangler secret put MY_SECRET
and I keep getting the same error. (I'm using wrangler@beta)
```sh
ERROR Raw mode is not supported on the current process.stdin, which Ink uses as input stream by default....