quran-ios icon indicating copy to clipboard operation
quran-ios copied to clipboard

File urls are blocked

Open ravshansbox opened this issue 3 years ago • 9 comments

Recitation and translation file urls are blocked in some countries(at least in Uzbekistan). Please, ask reviewers (they are complaining and may decrease score averages) to install a vpn and try again if they can't download.

ravshansbox avatar Jan 01 '22 22:01 ravshansbox

Oh, it's like 99% of Uzbekistan reviews complaining about this issue. Thanks for pointing it out. I've replied to them all. However, do you know if there is a way to detect this, so the app can provide such information directly?

mohamede1945 avatar Jan 02 '22 21:01 mohamede1945

It's quite tricky to detect them, because they are not timeouting the request, rather returning some invalid response. Attaching curl output to https://quranicaudio.com site. image How about spinning up a proxy-like (not an exact proxy, it's blocked as well) http server where you pass url you want to download and it serves it's content?

ravshansbox avatar Jan 02 '22 23:01 ravshansbox

I see. What about quran.com? is it not reachable as well?

mohamede1945 avatar Jan 02 '22 23:01 mohamede1945

quran.com is reachable and also playing recitation without vpn. It’s audio files cdn looks like not blocked.

ravshansbox avatar Jan 03 '22 01:01 ravshansbox

@ahmedre Could you look at this please? It's probably affecting the Android app as well. Seems like the whole country is blocked, almost all reviews from Uzbekistan is complaining about this issue. Maybe we could do something with DNS to serve the audio and translation content from a quran.com url?

mohamede1945 avatar Jan 03 '22 03:01 mohamede1945

I spent a bunch of time on this a few months back, the problem is it's a cat and mouse game. see quran/quran_android#1210

ahmedre avatar Jan 03 '22 03:01 ahmedre

Just FYI, just changing DNS didn't solve the issue for me.

ravshansbox avatar Jan 03 '22 04:01 ravshansbox

@ahmedre From the conversation it seems you found a solution. Is it a client-side fix? Could you point me to the commit I don't see it linked there, please?

mohamede1945 avatar Jan 05 '22 02:01 mohamede1945

the fix worked temporarily for some time, but I am getting more reports again, so not sure it'll help or not, but I'll ping you the details.

ahmedre avatar Jan 05 '22 08:01 ahmedre