what "notifications" are these? how are they sent?
what "notifications" are these? how are they sent?
Ipost req to discord api
Ndiscord hook yes, using fetch
Wok, have you debugged what discord has returned? workers all come from the same IP so if you don't send a bot token it's pretty easy to be rate limited.
Wwe use webhooks extensively in here from Workers (see #cloudflare-blog & #cloudflare-status along with other internal channels) so things are running fine
Noh I see
Iiirc there 2 endpoints for discord webhooks
one returns a response based on success
the other just returns 201
one returns a response based on success
the other just returns 201
Imake sure u sue the first and log it some other manner
NI will try adding a bot token and see if this solves my issue
Ntyvm @Walshy | Deploying and @IdkWhatever69
Ifollow the discord api specs
dont just randomly add headers
dont just randomly add headers
NYea ofc, I will read first how the headers should look like
Ibump if anyone has suggestions
WWalternatively, generate yourself with
wrangler deploy --dry-run --outdir dist
.Is this a bug? I literally just made the worker and used
.It also makes the wrangler.toml main be index.ts when the script it downloads is worker.ts
.Well actually no, it seems to all be a bit messed up
Ghello, im reading about durable objects and websockets and id like to understand how they differ from websockets in workers
i've previously built a few minigames using ws with tools like soketi where there's one ws server and all clients connect to it, so it's pretty straightforward to communicate with them
durable objects seem to enable a similar experience, where there's only one instance of DO (given the same id)
how is this different from workers and ws server implemented there? would every client connect to a different worker (and thus ws server) being there alone?
i've previously built a few minigames using ws with tools like soketi where there's one ws server and all clients connect to it, so it's pretty straightforward to communicate with them
durable objects seem to enable a similar experience, where there's only one instance of DO (given the same id)
how is this different from workers and ws server implemented there? would every client connect to a different worker (and thus ws server) being there alone?
LIs there a list of possible values in
this page only lists one example, but no comprehensive "these exist" list: https://developers.cloudflare.com/workers/runtime-apis/request/
Request.cf.continent?this page only lists one example, but no comprehensive "these exist" list: https://developers.cloudflare.com/workers/runtime-apis/request/
HI have a worker on example.myname.workers.dev and i created an alias for the worker on my domain, for example ex.mydomain.com. If I curl to the workers.dev it will work normally however if i curl to the alias i will always get "moved permanently". do i need to set up any special rules for this?
Hbrowser normal access works totally fine
.Are the paid numbers per day as well?
KIs there any technical documentation on how the wasm file is built and what exactly has to be exposed for it to be a valid wasm for cloudflare and what the zip should look like that is uploaded + where to upload it?
Or do I just have to reverse engineer everything and try to find it out?
Or do I just have to reverse engineer everything and try to find it out?
BSeems like this was an outage on the
workers.dev domain that was returning HTTP 520 Bad Gateway for POST/PUT/PATCH requests? Seems to be resolved now.
LHi, can anyone point me to some documentation for using a Worker to build and deploy to Cloudflare Pages? Trying to convert a Pages Function to a Worker since I only need it to run once a day, but having some trouble wrapping my head around how to use a Worker to deploy to Pages instead of the Function routing I'm currently using.
LIt seems this is the closest I can get to a proper list: https://developers.cloudflare.com/ruleset-engine/rules-language/fields/standard-fields/#ipsrccontinent
which... is a totally different document from the worker docs...
which... is a totally different document from the worker docs...
Eits almost certainly the same list, the IP info comes from the same place and in the same format regardless if you read it in ruleset or workers
KDo you want to trigger a Pages build from a worker or push code from a Worker to Pages?
For the first one you can create a Deploy hook and trigger a new build by calling the URL.
For the first one you can create a Deploy hook and trigger a new build by calling the URL.
LThe gist of my scenario is that I want to call an API that returns a timetable. I only need to call the API once a day to grab the latest timetable. I then want to build a static page which includes an HTML table of the timetable that was returned in the API response. Finally, I want to push that HTML page to the corresponding route in the Pages project.
I have the first two steps down -- calling the API and building the page from the response. It's the last step -- deploying that page to a corresponding route in a Pages project -- that I'm struggling with.
I'll look into Deploy hooks. It sounds like that's what I might be looking for.
I have the first two steps down -- calling the API and building the page from the response. It's the last step -- deploying that page to a corresponding route in a Pages project -- that I'm struggling with.
I'll look into Deploy hooks. It sounds like that's what I might be looking for.
Ehey guys i am currently exploring different solutions to implement a machine learning model in python into my cloudflare stack. my first idea was to have a cronjob in my worker sending an http request to the python app but if i could get rid of an http endpoint i would do it, any suggestions? could queues be a good idea?
NHey everyone, i have a little problem, in my application on build step i got this error, i try to change build command to install --legacy-peer-deps && my_build_command
but its not working, what i can do more ?
but its not working, what i can do more ?
FPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.Nsorry i am new here i dont know all rules )) and i dont sure what the category of this question
Myo for some reason setting workers smart placement on wrecks any post request for iceland users?
happened suddenly today about an hour ago users from iceland told us services are down only for them, any post request always gives 520 error for some reason atm\
happened suddenly today about an hour ago users from iceland told us services are down only for them, any post request always gives 520 error for some reason atm\
CSwitch to
standard placement – I also had a huge uptick the last couple days in 520s on our API specifically affecting random users.
MYea i did and that fixed it, also images from our public r2 bucket randomly dont work for some users as well
Cis there a similar placement for R2? (I haven't used R2 at all)
DAny good minifiers and/or prettifers that work on HTML in a Worker?
MNo dont think so
Cinteresting, you may want to try disabling http3 and/or http2 to origin
.On the dashboard, if you make a real time logs, log, does it ever timeout or if you keep the window open it'll always show logs for however long it's open for?
Wit should timeout after 6 hours
Wbut the dash starts to break down after a thousand or so entries, keeping it open for 6 hours i fully expect the tab to crash way before then
.Gotcha, thanks. Thought there would be some kinda "if it goes over this it'll probably crash" lol
.Trying to add Sentry but getting this...?
.Nvm got it
.Can someone help me install sentry? I made a new project but when I try and add it on the dashboard it says I have no options
BI also had similar a couple of days ago, and it's back again. 100% of POST/PUT/PATCH requests against the
workers.dev domain are failing with 520. Requests against custom domains seem to function normally.BThis is actually becoming a huge days-long downtime issue (on our paid workers plan)... is anyone from the Cloudflare team aware of it because I can't see it on the status dashboard?
CI can't recreate. I have https://hello-world-billowing-brook-b77a.cyberjake.workers.dev/ and I can hit it with any method.
