could be that your client automatically retries, some of the s3 libraries do I think on 5xx errors
could be that your client automatically retries, some of the s3 libraries do I think on 5xx errors
DI usually have retries set to 0 in aws4fetch
Cliving life on the edge
CB2 has a article here: https://www.backblaze.com/blog/b2-503-500-server-error/
I guess they use 500/503 errors to switch between vaults and such, no LB in front, it gets routed to a vault and if it fails because it's full the request dies. Kind of interesting
I guess they use 500/503 errors to switch between vaults and such, no LB in front, it gets routed to a vault and if it fails because it's full the request dies. Kind of interesting
As we’ve described in our developer docs, the best decision is to write your integration in a way that it retries in the event of a 500 or 503.
CI guess that's not for S3 though although it can still run into similiar errors
UBackblaze is the king of being slow and constant errors
Cuploads are free because half the time they fail /s
U
realCreally cheap though
CI've wanted to try B2 before but I don't have large enough needs and we get R2 free
UI used B2 for a little bit for storing on demand video clips from live streams and it was super bad switched to stackpath which was just resale of wasabi or whatever
UBut very good and fast
JWe're big B2 users and I'm a fan of their service. You do have to design with 5xxs by design though when using their native APIs at least: https://www.backblaze.com/docs/cloud-storage-integration-checklist
Tools that integrate with Backblaze B2 Cloud Storage and are featured on the Backblaze B2 integrations page must follow specific guidelines.
JIf you use their S3 compatible API, it's all transparently handled for end-users nowadays, which is very nice
Jor at least, in theory it should, lol
Dahhh, that makes sense, I've always be using their S3 API. Never wanted to touch a native cloud storage API 
Junfortunately we were about ~18 months early with our integration so the S3 compat API didn't exist 
DSemi-related question, is there any perf difference between virtual and path-style S3 APIs?
Din practice it looks like both point to the same IP anyway
JI think the path-style is old and planned to be deprecated
Jbut otherwise I don't think so
JCIf you're talking R2 S3-compat specifically I really doubt there would be any diff, already a compat layer on top
Dis it actually gonna be deprecated though?
Cthey entirely stopped that though as noted at the top, and said they would provide at least a years heads up before doing it again, so it looks like it'll still be around for a while
Jyeah fair, maybe one day
HHey all, does anyone have experience in setting up DDNS for bypass rule in Access policy (zero trust)?
I used to have static IP from my ISP and I just bypassed access via that IP but I don't anymore. Wondering if anyone has experience in using DDNS for the bypass rule?
I used to have static IP from my ISP and I just bypassed access via that IP but I don't anymore. Wondering if anyone has experience in using DDNS for the bypass rule?
CYou’d have to use the API to update the bypass IP but it is doable.
HThanks. I will checkout the update access policy call.
https://developers.cloudflare.com/api/operations/access-policies-update-an-access-policy
https://developers.cloudflare.com/api/operations/access-policies-update-an-access-policy
Interact with Cloudflare's products and services via the Cloudflare API
HThat was easy, thanks for the suggestion
CDoes Services Binding work for 
I get the error:
wrangler local mode? I get the error:
Cannot read properties of undefined (reading 'fetch')Coh, local worker can only bind to another local worker 
NHi, i'm testing with R2 and aws lambda . aws lambda i hosted on us-east-1 regon. get object latency is very high. around 400 - 500 milliseconds. anyone have tips to improve the peroformance?. thanks
VYou don't have to pay, you can ask for access in the thread browser-rendering-apiBrowser Rendering API Beta Access
OHi, I have a fairly easy problem to solve. Please could someone help me with that?
I've already logged using wrangler login, but as soon as I start I get the error as following
I've already logged using wrangler login, but as soon as I start I get the error as following
✘ [ERROR] A request to the Cloudflare API (/accounts/719e33....9acb3c939/d1/database) failed.
Authentication error [code: 10000]
Getting User settings...
👋 You are logged in with an OAuth Token, associated with the email
...OI've tried instead of oauth use api token, but still no success.
CLOUDFLARE_API_TOKEN=xxxx bunx wrangler d1 create production
✘ [ERROR] A request to the Cloudflare API (/accounts/719e33xxxxc939/d1/database) failed.
Authentication error [code: 10000]
Getting User settings...
👋 You are logged in with an API Token, associated with the email _!
┌─────────────────────────────┬──────────────────────────────────┐
│ Account Name │ Account ID │
├─────────────────────────────┼──────────────────────────────────┤
│ _'s Account │ f707xxxxb32 │
└─────────────────────────────┴──────────────────────────────────┘
🔓 To see token permissions visit https://dash.cloudflare.com/profile/api-tokens O
Ok I got this work. The account id doesn't match with one presented in wrangler.toml file
PIs there any way to escalate an issue related to cloudflare warp routing? I have tried raising the issue in cloudflare warp support site and they just marked it as solved after 3 weeks. I also tried emailing cloudflare NOC and did get a reply from them. I replied back and haven't gotten any reply back from them
PMany European and US IPs are getting routed via cloudflare Singapore from mumbai which is increasing the latency dramatically
PTraffic is indeed routing via Singapore on that first MTR. This is part of some temporary restrictions on our backbone that include cable cuts and that we're working with the provider to get a fix. This might be present for other routes that we transport over the backbone and it will add a few additional ms of latency.
PThis is what they said when I emailed NOC
PAfter that I requested them to put warp on airtel upstream till cloudflare routing issues gets fixed
CThere was back and forth with Indian ISPs routing for a while
Cmy understanding is they don't really want to play nice and would rather route stuff internationally
PUmm
PThere seems to be a misunderstanding. When connecting to Warp Mumbai colo(nearest colo), some IPs are routed from Mumbai to Europe through Singapore. Warp initially used Airtel/Sify as their upstream on many IPs, and a few weeks ago, it was entirely on Airtel. However, recently, they reverted to Cloudflare routing on many european and American IPs, causing high latency as it gets routed via Singapore due to a temporary restriction on their backbone. Initially, it went directly from Mumbai to Europe on cloudflare routes
