-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Anti-CAPTCHA no longer works - Instance blocked #1183
Comments
YouTube has changed something and doesn't accept solved CAPTCHAs anymore. I have same problem. |
uh-oh, thats not good. The only real possibility to bypass reCAPTCHA on Server right now is to install Squid Proxy on your server and use it in your browser. Navigate to YouTube and solve the captcha manually. After you have been successfully redirected to YouTube, open the developer console and copy the "GOOGLE_ABUSE_EXEMPTION" cookie and paste it manually into Config.yml. after that restart invidious and it works again for about 1-2 hours. I wonder is there a Anti-CAPTCHA Service that response with Cookie instead of a Hash like Anti-Captcha.com it does. |
Sometimes YouTube accepts CAPTCHAs instantly, but more often you need to try like 20 more times. I see no pattern here. |
yea this is affecting search to in invidio us |
Dont Blame the Dev here... Its Googles shit if they change their system so often... |
ceb2529 |
@artsemionov nope, doesn't work. |
How feasible would it be to adapt Buster to run on a server? |
Unfortunately this was bound to happen sooner or later. i hope there is a workaround but it might be necessary to implement a backup method that Google cannot block. and for that the challenge that the invidious server gets has to be answered by the the invidious server. for that invidious would have to proxy it to one of its users receive back the answer and then reply to YouTube's servers like i suggested in the past. |
For all that want to still use the service just use a different instance https://instances.invidio.us/ |
I wonder is there a way in invidious to use Multiple Proxies in sequential mode to bypass CAPTCHA? |
Thanks! Just to be sure: this loses our playlists and subscriptions, right? |
Just want to let u know that i also contacted Anti-CAPTCHA about this situation. maybe they find a solution.
|
Did you try solving CAPTCHA via proxy? Maybe they started to compare IPs of who solves and who posts the CAPTCHA. |
yes i tried it via proxy, i wrote a NodeJS script with puppeteer and Chrome.. |
@rustynail1984 I mean there is a NoCaptchaTask at anti-captcha.com that requires setting up a proxy on same server that sending CAPTCHA post requests. |
@artsemionov yes i tried it via NoCaptchaTask and Proxy. But i cant solve the proxy with the responded hash. it redirect me to https://www.google.com/sorry/index I hope this is the correct way to post the hash.. |
You can export/import your data under @rustynail1984 Thanks for sharing your results. I tried something similar in add-proxy and encountered the same issue. |
i also tried this in invidious.
but unfortunately this doesn't work either. Request is sent to Anti-CAPTCHA i see it in Dashboard. See the following Errors:
|
Thanks to everyone involved in getting things working. |
Just got an email from anti-captcha
Maybe this also applies to youtube.com. |
Indeed, there is "data-s" in recaptcha page. |
Should be fixed with 6435c7b. |
yes |
Unfortunately no, I still get this error and one time i got this error |
What about we use buster (as he said) ? like type some lines of code that uses buster addon to solve captcha for us using watson speech to text or any service else ? |
I'm doing some test in with NodeJS and I was successful. I was able to bypass the captcha on google.com/sorry. After this i will share my Code. |
As glad as I am someone is figuring this out, I can't help to think that the moment you post the work-around, Google developers will be on it, developing a counter-measure. |
No no no, nobody wants private software here. Invidious works very well. YouTube receive too much requests from a single ip address, and therefore send captcha. That's the reason why some little instances still work: they have less users, and send less requests to YouTube. |
As mentioned earlier, I was able to bypass Recaptcha on google.com/sorry. The second problem, I can't solve the second captcha on youtube.com, it tells me hash key (from anti-captcha) is wrong. Here is my nodejs code: https://pastebin.com/Q7YXGSDH |
Ok seems it is 1/2 solved with this fix. It works now for google.com/sorry but not for the second Captcha on youtube.com video page.
|
just as a quick idea: |
youtube-dl probably fails too eventually if use it too much and you will have to solve a captcha in the browser |
Unfortunately it's no longer working for "Google sorry". |
I could be wrong, but I believe this is a caching error. I assume you are referring to the HTTP 403 error? |
"Read timed out " :( |
This a known issue: #1132 |
TopJohnWu played this game for a few years with Magisk and Google. They still need to come up with something and we just break it in a few weeks and they waste more money on it. |
Sounds about right to be fair |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Anti captcha is fixed for now. |
Hi there,
unfortunately the Anti-CAPTCHA suddenly stops working.. CAPTCHA requests are sent to Anti-captcha.com and solved, but no more cookies are saved in config.yml.
I run invidious on a cloud server without docker
I also tried it on another server and via Docker, same problem.
From the Docker log I could see the following error:
Exception: Missing hash key: HTTP::Headers::Key(@name="location")
Does anyone have any idea what I can do?
The text was updated successfully, but these errors were encountered: