-
Notifications
You must be signed in to change notification settings - Fork 28
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
YT sync no longer working #440
Comments
Further update: yt-dlp community is reporting a lot of trouble lately with YT blocking access because it detects it as a "bot". My guess is that if your server gets flagged, YT sync may no longer work (no idea if that's temporary or permanent). Just another reason why creators should upload directly to PeerTube, I guess. |
Yah we are seeing the same issue....nothing got fixed for you? I do not know if there is a solution for this ... Chocobozzz/PeerTube#6522 |
Yup, looks like the blame all lies with Google on this one. The importance of not having a single source of content online... |
i activated sync some days ago with 7 channels, |
Yes but if your IP gets banned by youtube then it will not work anymore.... |
I can confirm that youtube is blocking based on IP. Latest Peertube version includes an option to set some HTTP proxy in front of yt-dlp, so you can deport the traffic on a non-flagged IP. This is not ideal, but their is no simple technical solution to restriction imposed by youtube... |
Randomly about 1-2 weeks ago, YT syncs for channels stopped working on my server. I thought it might be because I was still on PeerTube 5.x.x (due to issues with Yunohost being able to upgrade to 6.x.x), so after some effort, I was finally able to get PeerTube updated to latest 6.2.1. However, after doing so, YT imports for all channels are still failing. Here is part of the error log I'm seeing:
...it continues on like that for a while (I can get more if needed and finally concludes like so:
I definitely have users with channels that are depending on this to work, so any help is appreciated!
The text was updated successfully, but these errors were encountered: