poro
poro
CDCloudflare Developers
Created by poro on 4/26/2024 in #general-help
nameservers changed +24hr ago. Cloudflare status still pending.
Hi, i've changed my nameservers on my registrar but Cloudflare still states the operation is pending. in the stats section of dig's output i get :
;; Query time: 59 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Apr 26 17:50:04 CEST 2024
;; MSG SIZE rcvd: 79
;; Query time: 59 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Apr 26 17:50:04 CEST 2024
;; MSG SIZE rcvd: 79
i believe 1.1.1.1 belongs to cloudflare, so my registrar might have updated the nameservers correctly. Could the issue be on cloudflare's side ? DNSSEC doesnt seems enabled as delv returned
;; none:29: no crypto support
delv: No trusted keys were loaded
;; none:29: no crypto support
delv: No trusted keys were loaded
8 replies
CDCloudflare Developers
Created by poro on 4/17/2024 in #general-help
`wrangler pages dev`, error in _worker.js can't find D1 table
I've been trying to run locally a Pages project but i keep getting an error in my _worker.js. The D1 table i'm trying to work on cannot be found. The issue doesn't happen in prod. my wrangler.toml was generated with wrangler pages download config so it should be fine. i noticed there is no --remote option (as when working with workers)
3 replies
CDCloudflare Developers
Created by poro on 2/20/2024 in #workers-help
Locally testing w/ workers
On previous versions of wrangler when i was running wrangler dev i had the following output on console:
[mf:inf] Ready on http://*:54299
[mf:inf] - http://127.0.0.1:54299
[mf:inf] - http://192.168.1.98:54299
[mf:inf] - http://localhost:54299
[mf:inf] - http://[::1]:54299
[mf:inf] Ready on http://*:54299
[mf:inf] - http://127.0.0.1:54299
[mf:inf] - http://192.168.1.98:54299
[mf:inf] - http://localhost:54299
[mf:inf] - http://[::1]:54299
Now i receive this output :
[wrangler:inf] Ready on http://localhost:54241
[wrangler:inf] Ready on http://localhost:54241
Does that mean i cant communicate with my worker on http://192.168.1.98 ? Because when i try i get :
curl: (7) Failed to connect to 192.168.1.98 port 54241 after 6 ms: Couldn't connect to server
curl: (7) Failed to connect to 192.168.1.98 port 54241 after 6 ms: Couldn't connect to server
I was wondering if i needed more configuration to be able to test a worker running locally with another device on my home network.
4 replies
CDCloudflare Developers
Created by poro on 12/19/2023 in #workers-help
Store a JWT to be pulled from a worker
I'm need a worker to attach a JWT in the headers of a call to a 3rd party API. This JWT should be refreshed every ~30min. My plan was to have a chron job triggering a worker to generate a new JWT. But i'm unsure of where i should store that JWT so that my other worker making the API calls can retrieve it. Secrets cannot be set by worker
3 replies