International users not able to fetch from R2 bucket?
I have a few users that are failing to fetch from R2 bucket. It works for them through USA vpn.
How can i resolve this?
How can i resolve this?
HWhat country are they from? What error are they getting?
AIndia and Spain.
Getting a failed to fetch error on web browser when they try to fetch the file after uploading a file
Getting a failed to fetch error on web browser when they try to fetch the file after uploading a file
ASorry, any other details i can provide to help? I'm not sure if i have the exact error log but I can try to find it
Abasic flow is i have just
- get signed URL
- upload an mp3 or mp4 file
- fetch the uploaded URL to sync with application state.
HWith India, there is an ISP that likes to block the S3-compatible endpoint for some reason. I haven't seen any reports from Spain, but it might be similar
HAre you able to see if there is some kind of status code? Does it fail to connect entirely?
AThe indian user is using JOI isp if that helps
AFrom my interaction with user, it did not even make a network rqeuest?
Aor did not get a response*
Ai could be wrong, i didn't get to extract actual browser logs
Ai do have a worker proxy setup over R2, if that helps
HYeah, that's the one, Jio has had issues for a while
HYou might be able to run it via Workers/a custom domain. That shouldn't be blocked
A:/ is there any workaround?
Athe problem is i need to support MP4 video range requests, i believe thats only supported through worker proxy
HCustom Domains should be able to do Range requests? Though for larger files, you may need to disable cache
Aand just to clarify, pointing a custom domain name over my worker proxy is not the same as pointing an R2 bucket directly at a custom domain?
I currently am setup with the former
I currently am setup with the former
Asubdomain "assets.website.com" -> worker proxy -> R2
HYour way should work too, but it also incurs a Worker request
Ahmm ok, is this just something the user needs to work out with their ISP then?
