-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Revert back to http connection #957
Comments
How do you know that the quic workaround is banned by Google? I do agree that it may fix #917 but if the workaround is still working why reverting to a state where almost every invidious would stop working due to the Google captcha? |
Use https://anti-captcha.com will solve the captcha problem. |
@unixfox because people are being banned? |
@tleydxdy I didn't experience any ban at all (my instance is yewtu.be). |
Hi sir, may i know how to block all the API endpoints except for web uses like you said? I want to implement it on my instance too. Please help. |
I just used the status parameter of Caddy like this:
|
I use Debian 10, can you advice what file should i edit? |
If you installed the Caddy webserver with this script: https://github.com/sayem314/Caddy-Web-Server-Installer |
Ok sir, i will try it. Thanks a lot for the help! 👍 |
There are two different kinds of CAPTCHAs: The first is similar to one of the reported errors in TeamNewPipe/NewPipe#2924, and looks like this: (For reference, the "submit" button makes a POST request to After a successful POST YouTube returns a new cookie The second one is more generic and looks like this: After a successful POST (to The The |
@omarroth Thus, the automatic captcha solving doesn't work because invidious doesn't check if the instance is partially blocked. Like only for fetching the channels. |
This is the only cookie that is currently supported. For clarification, what does e.g.
return for you? (you may also need to specify |
That's strange because the automatic anti-recaptcha never wants to activate itself. I though the anti-recaptcha was only designed for watching videos according to the source code: https://github.com/omarroth/invidious/blob/master/src/invidious/helpers/jobs.cr#L239 I'm on the phone but the curl command should returns the same second page with "our systems have detected...". Everytime I fetch a channel I get a JSON::ParseException like described in #963 |
My bad you are right @omarroth, it does indeed support the cookie Can you add that new URL in the source code or come up with a way to detect if a request that invidious does is redirected to |
I have similar behavior but with video informations, like comments, likes etc |
I'm trying to implement anti-captcha for NewPipe. Currently I receive second type of captcha - "https://www.google.com/sorry/index..." and try to make post with 3 params: "q", "continue" and "g-recaptcha-response" but never receive GOOGLE_ABUSE_EXEMPTION cookie nor any redirect url. What I do wrong? |
What's the error message given by Google? Also what's the status code when doing a request? If it's a 400 status code then there is something wrong in your code. |
It remains the same page with same url "https://www.google.com/sorry/index.." and 429 status code, like I didn't post at all. |
Is your request a POST request?
The best way to know if your request is correct or incorrect is to use a proxy like mitmproxy and compare your request with a request made in a browser. EDIT: Here is an example code from one of my project: https://github.com/unixfox/proxy-sorry-google-recaptcha/blob/master/anticaptcha.js#L53. I hope this will help you. |
Yes, I do POST with okhttp3.
I can confirm that "q" value I post is the same as located in page. I see omarroth closes previous connection just before POST. I parse the page, close connection, wait for the captcha task and then POST. Could it be the reason? |
LOL. In case anybody need this: |
I had the same issue with got, that's why I had to set |
Oh. I wish I understand JS well. In any case thank you for help! |
Now that using quic will be banned too, I think we should go back to using http, as it's less dependency, and less fragile (on Alpine at least). or offer it as a build option?
The text was updated successfully, but these errors were encountered: