-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Forbidden" error when adding or refreshing APKMirror track-only apps #1973
Comments
Can report the same behaviour since a few days ago (with a different app). Update check suddenly failed with "Forbidden". Removed the app from Obtainium but could not add it again because this action is also "Forbidden".
|
I already reported it some months ago in #1097 |
Yeah it seems like cloudflare protection has gone from being inconsistent to always on. May have to remove the apkmirror source if a solution is not found. |
oh ok I did see #1097 when searching for previous tickets but I wasn't aware that my current issue was Cloudflare related. I may have to look for other sources to migrate to then |
@archon810 Do you have an idea? |
Do |
Try setting a proper user agent that references the app being used to query ("Obtainium" with the version would be a good start). |
@archon810 I've changed the user agent to |
Try with common browser user agent |
Can we change the user agent ourselves? |
Yes, in the settings of the respective app. |
When adding a non-HTML-source app (like one from APKMirror) this is not possible. |
Don't see any option to change the user agent |
1.1.32 still forbidden error appear |
Latest version now correctly identifies Obtainium in the user agent (with no option to override). @archon810 please let us know if there's anything else that can be done. If not the source should be removed. |
@ImranR98 Now that there's a proper UA, I took a look at the Cloudflare WAF stats. I found that the vast majority of "Obtainium/*" user-agent requests (over 10k over the past 24h) were allowed, with only several blocked or challenged. Is the version with this user-agent already released out into the wild? The challenge reasons were:
Perhaps your test includes one of the challenged urls or you're using tor? Otherwise, please let me know on Telegram what you're querying for and perhaps your IP so I could look into it. Furthermore, I can explain how APKUpdater/APKGrabber use our API and perhaps generate an API key for Obtainium so that you don't have to ping our feeds at all and instead batch request 100 apps at a time. In return, I ask only that Obtainium, just like APKGrabber and APKUpdater, continues to show users our download pages so that we can generate some ad revenue and pay for our server and operational costs. |
Thanks @archon810, good to see that it's working for most people (I'm still seeing "Forbidden" with the couple of apps I just tested, "Garmin Connect IQ" and Netflix). The RSS feed request fails, for example https://www.apkmirror.com/apk/netflix-inc/netflix/feed/.
Yes, a proper API would probably be better than using the RSS feed. Obtainium currently only queries for one app at a time - so using the API would not be more efficient in that sense - but I'm guessing the API provides more info, is easier to parse, and may allow for other features like search. Do you know how we could include the API key in Obtainium without making it public? Not sure how APKUpdater/APKGrabber do it. Or would it be okay to make that public?
Yes, APKMirror is a "track-only" source and will stay that way. |
So at least I still have forbidden errors too, all the time. |
Hello, how to set the "Custom user-agent for APKMirror",I wasn't able to find the button.I'd be grateful if you could advise me. |
Prerequisites
Describe the bug
APKMirror applications are track-only on Obtainium, but when refreshing or trying to install new apps on APKMirror, Obtainium returns "Forbidden". It doesn't seem to be related to my network so I'm not sure why Obtainium is having trouble with this site.
To Reproduce
Please complete the following information:
I can provide any logs or screenshots if needed
The text was updated successfully, but these errors were encountered: