Skip to content
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

Error "All APIs are down" 'try again later' #252

Closed
YAKSL opened this issue Jun 16, 2024 · 4 comments
Closed

Error "All APIs are down" 'try again later' #252

YAKSL opened this issue Jun 16, 2024 · 4 comments
Labels
wontfix This will not be worked on

Comments

@YAKSL
Copy link

YAKSL commented Jun 16, 2024

whether the song is in my favorites or in the search results, songs don't seem to play on my end anymore.
was there a recent update to youtube APIs that broke streaming? maybe the culprit is simply my location (North Africa) ? it's been at least a week since it's been like this

Capture_Musicale

okay, it might have something to do with this issue on Piped 'Got error: "Sign in to confirm that you're not a bot"' ?

Capture_Piped

i get this error randomly when using the default instance "kavin.rocks (official)" but not on other instances like "kavin.rocks libre (official)" even when i'm signed in (to piped) although it might be reffering to signing in to youtube because it seems like recently they've been enforcing it to view videos.

@YAKSL
Copy link
Author

YAKSL commented Jun 16, 2024

now here's the thing i tried using Musicale on my phone and it seemed to work just fine, Firefox on Android and Chromium, Edge on Windows

@Bellisario
Copy link
Owner

I didn't change any API recently... the issue is probably that your IP address with that specific browser (user-agent) was considered "strange" and blocked from Piped's Cloudflare, preventing you from accessing the API.

Once I opened an issue (TeamPiped/Piped#2833) because they were blocking Windows 7/8 devices (as they were considered "old browsers").

For the fact that no other instance was able to act as an alternative from the official one, this could be also because some of them use Cloudflare and others are offline: I put there as many (without CORS) as I could, but I probably need to update them (some might not work anymore at all).


My suggestion is just to wait, downtimes happens also to me sometimes (currently I don't experience it but I see a response slowdown).

A "trick" that could work (if you're not blocked by Cloudflare but Piped is still stuck on the request) is to init a request to Piped (by trying to play the song), wait 2/3 secs, reload and repeat the same multiple times... this sometimes prevents Piped from leaving you stuck on a request and "exploit" another one, giving Piped some time to fetch the data for you.


On Musicale side there's not so much to do as it relies on Piped for everything, anyway some ideas to lower the downtime rates that I could add in the future:

  • Directly fetch fresh instances from Piped Wiki (could be impossible due to CORS)
  • Allow users to add/remove/modify instances to use
  • Save songs locally (complicated because of indexedDB and space available could not be enough, as there's a max space quota of 500MB, divided by ~3MB for each song, allowing only, ideally, 166 songs to be saved)

@Bellisario
Copy link
Owner

Update

I've just found that there's an opened issue on Piped itself regarding this problem: TeamPiped/Piped#3658

Seems that Google is doing an a/b test to prevent content scraping, by requiring the user to sign-in to prove of not being a bot...


Anyway, as said before, there's nothing Musicale can do right now to prevent these issues.

Copy link

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the wontfix This will not be worked on label Jul 18, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants