-
Notifications
You must be signed in to change notification settings - Fork 15
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
Piped Proxy IP Issues #162
Comments
Note that you can easily switch out the piped instance to one in this list (or even host your own). I personally am currently using the |
I know the public instance list and now the official libre instance also does not work. I removed my YouTube subscriptions yesterday because of error parsing all YouTube subs from all instances, which then I looked at Piped's GitHub and found that YouTube is blocking and severely rate limiting Piped IPs (see here and here), and I have been unable to add my YouTube subs back to the subscription list on Pipeline likely due to this reason, so it is likely that if it worked for you, you managed to get things working before the libre instance hit the rate limit. I get that it's something you're not likely to be able to fix on your end right now, at least until Piped decides what they want to do, but again, just pointing it out for you to keep an eye on. |
Now I understand. The situation seems pretty bad looking at the issue you sent. Hopefully they are able to provide a fix. |
Hello,
This is mostly a heads-up that currently nothing on Piped is working with YouTube because YouTube is blocking all Piped proxy IP addresses. This means that Pipeline is currently not working with YouTube at all. If Piped is not able to fix this, it may require a different way of accessing YouTube.
The text was updated successfully, but these errors were encountered: