how can i binding kv remote?
wrangler version 4.42.0
wrangler.toml
[[kv_namespaces]]
binding = "Blog_KV"
id = ""
preview_id = ""
remote = true
error_msg
✘ [ERROR] e = kj/async-io-unix.c++:1655: failed: connect() blocked by restrictPeers()
stack:
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4bd8b60
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4bd9300
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@30e6940
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4bcc230
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4bcc650
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4babf40
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@330b3c7
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@330c151
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@330e674
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@32e81c0
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@32efc60
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@3307840
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1e209c0
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b86880
/home/guojw/workspace/opengx_blog/backend/blog_backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2a03ef0;
sentryErrorContext = jsgInternalError; wdErrId = teujbq3p8d1qf50fr2cdfh75
✘ [ERROR]
i startup with npx wrangler dev --remote but i can't get the content of kv? why?
and i use vscode remote , and then forward the port. i open the browser in my windows
update 4.47.0 and use npx wrangler dev, maybe local workers and remote kv, but why 500 error?
✘ [ERROR] Critical Error: Rust panic: panicked at src/services/user_service.rs:8:60:
called `Result::unwrap()` on an `Err` value: JavaScript(JsValue(Error: KV GET failed: 500 Internal
Server Error
Error: KV GET failed: 500 Internal Server Error))
at null.<anonymous>
(file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:16689)
at null.<anonymous>
(file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:10941)
at u (file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:163)
at __wbg_call_525440f72fbfc0ea
(file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:10914)
at [object Object]x105294)
at [object Object]xe9d14)
at [object Object]xf82de)
at [object Object]xf59cf)
at [object Object]x106d3a)
at [object Object]xfa99f)
at [object Object]x5fa13)
at [object Object]x29f0b)
at [object Object]xde077)
at [object Object]x10740c)
at [object Object]x1073fe)
at [object Object]x108251)
at X (file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:1139)
at f (file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:609)
✘ [ERROR] Critical RuntimeError: unreachable
at [object Object]xf59f5)
at [object Object]x106d3a)
at [object Object]xfa99f)
at [object Object]x5fa13)
at [object Object]x29f0b)
at [object Object]xde077)
at [object Object]x10740c)
at [object Object]x1073fe)
at [object Object]x108251)
at X (file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:1139)
at f (file:///home/guojw/workspace/opengx_blog/backend/blog_backend/build/index.js:2:609)
✘ [ERROR] Uncaught RuntimeError: unreachable
at blog_backend.wasm.std::panicking::panic_with_hook::h5f62ad9dc4d6300a
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[654]:0xf59f5)
at blog_backend.wasm.core::panicking::panic_fmt::ha095fedb92b6396f
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[990]:0x106d3a)
at blog_backend.wasm.core::result::unwrap_failed::h90b13c69eec28497
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[759]:0xfa99f)
at blog_backend.wasm.blog_backend::handlers::index_handler::{{closure}}::h31f6d73489692220
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[145]:0x5fa13)
at
blog_backend.wasm.wasm_bindgen_futures::future_to_promise::{{closure}}::{{closure}}::h951112c3bbb8008c
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[90]:0x29f0b)
at blog_backend.wasm.wasm_bindgen_futures::queue::QueueState::run_all::hee568ed064bf2d88
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[417]:0xde077)
at blog_backend.wasm.wasm_bindgen_futures::queue::Queue::new::{{closure}}::ha831149ab8f99950
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[1025]:0x10740c)
at blog_backend.wasm.wasm_bindgen::convert::closures::_::invoke::hfdaf8063fb49fae2
(wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[1024]:0x1073fe)
at blog_backend.wasm.wasm_bindgen::convert::closures::_::invoke::hfdaf8063fb49fae2 externref
shim (wasm://wasm/blog_backend.wasm-0058b13a:wasm-function[1096]:0x108251)
at X
(file:///home/guojw/workspace/opengx_blog/backend/blog_backend/.wrangler/tmp/dev-aZnvBY/index.js:152:5)
at f
(file:///home/guojw/workspace/opengx_blog/backend/blog_backend/.wrangler/tmp/dev-aZnvBY/index.js:117:14)
[wrangler:info] GET / 500 Internal Server Error (135255ms)
✘ [ERROR] Uncaught Error: The Workers runtime canceled this request because it detected that your Worker's code had hung and would never generate a response. Refer to: https://developers.cloudflare.com/workers/observability/errors/
Hi @GVger 👋
A few days ago we had a big outage (https://blog.cloudflare.com/18-november-2025-outage/) I suspect that that might have been why you've seen these internal server errors, just to make sure, could you please try again and let me know if you're still getting these? 🙏
@dario-piotrowicz still 500 status code. i startup workers local and use remote kv
Please can you provide us with a reproduction that we can test out? Ideally in the form of a github repository with instructions on how to reproduce the error.