-
Notifications
You must be signed in to change notification settings - Fork 99
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
IPTorrents Authentication Doesn't Work #106
Comments
I can't test since I don't have an account anymore. |
It looks like its the same issue -- whatever service they use (something like cloudfare) makes you wait 5 seconds before redirecting you to prevent bots it seems. Not sure if there is going to be an easy way around that. You may be able to repro, or at least see what I'm seeing by navigating to iptorrents in incognito or on a VPN without logging in. |
It's a cloudfare protection and it's a pain in the ass.. We have the same problem on yggtorrent provider. |
Sorry for the off-topic. |
It's been a while now and It may have changed but I remember having some troubles running chrome inside Heroku or Now services (with free plans). BTW, good job with the puppeteer solution. |
@JimmyLaurent I was right, Heroku doesn't allow running Docker as root so that's why it doesn't work and for vercel it's planned: unixfox/pupflare#3 |
@unixfox Still off topic: you might be interested by this buildpack, I made some tests and ran puppeteer flawlessly on heroku. @sgianelli I added a new experimental cloudflare bypass. It's like pupflare, but only use puppetteer to grab cookies. So if it doesn't bother you to use chromium headless, you might be interested. |
Hiya! I'm running into the same issue as @sgianelli with IPtorrents |
It looks like you cannot authenticate to IpTorrents right now because of the browser identification redirect they do now. If you have a valid cookie then it works but it doesn't seem like torrent-search-api is able to get that cookie on its own now.
The text was updated successfully, but these errors were encountered: