as seen in the issues linked below, google is now aggressively blocking alternate frontends, clients such as yt-dlp, and non-residential IPs.
the only solution is to use oauth (NOT cookies), but there's no way of using an alternate dlp client (or even configuring the current dlp client in whishper for that matter).
this means the more time passes, less people will be able to use this repository due to google's blocking combined with the inability to do oauth login.
Yes, confirmed . It works without --proxy option.
If assign --proxy option to go through proxy on VPS , Sign in to ... will occur .
So, what now ? Anyone has solution about this?
Description
as seen in the issues linked below, google is now aggressively blocking alternate frontends, clients such as
yt-dlp
, and non-residential IPs.the only solution is to use
oauth
(NOT cookies), but there's no way of using an alternatedlp
client (or even configuring the current dlp client inwhishper
for that matter).this means the more time passes, less people will be able to use this repository due to google's blocking combined with the inability to do
oauth
login.To Reproduce
steps to reproduce the behavior:
backend.err.log
Good news
at least it wasn't my fault, spent 2 hrs tinkering with the
.env
after making sure it works on my laptop, on a normal residential (home) network.