Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

🐛 Error: No audio formats found #13

Open
HyperKids opened this issue Oct 22, 2024 · 9 comments
Open

🐛 Error: No audio formats found #13

HyperKids opened this issue Oct 22, 2024 · 9 comments

Comments

@HyperKids
Copy link

Describe the bug
"Error: No audio formats found" when attempting to play a song/video

How To Reproduce
Steps to reproduce the behavior:

  1. Fresh install - Debian, started via pm2
  2. Queue a song/video with /play

Expected behavior
Error does not occur

Environment (add if possible)

  • Node.js version: 18.17.0

Additional information & screenshots

4|npm  | Error: No audio formats found
4|npm  |     at Song.makeResource (/root/megumin/structs/Song.ts:73:24)
4|npm  |     at processTicksAndRejections (node:internal/process/task_queues:95:5)
4|npm  |     at async MusicQueue.processQueue (/root/megumin/structs/MusicQueue.ts:192:24)

Song shows up as "undefined" in queue

@hoangvu12
Copy link
Owner

I believe this error occurred because the Invidious instance failed to return audio formats, which is unrelated to the bot. You can try changing the instance.

@HyperKids
Copy link
Author

I've tried three different Invidious instances. Am I perhaps formatting the link wrong in config? I'm using the format https://invidious.link.here.

@hoangvu12
Copy link
Owner

I've tried three different Invidious instances. Am I perhaps formatting the link wrong in config? I'm using the format https://invidious.link.here.

Make sure that you can actually watch videos on the instance, try many different videos because some videos are cached.

@HyperKids
Copy link
Author

Okay, I see what is going on. All the Invidious instances listed require login - the only one as of writing that works without login is inv.nadeko.net (which doesn't work if I'm trying to host this on a VPS due to CloudFlare). invidious.jing.rocks seems to work for search, but anything under the /api/v1/videos/ endpoint returns "This content isn't available, try again later".

This can probably be closed? Seems that there's just a lack of public Invidious instances that don't require login. Or perhaps the answer is to add authentication support.

@hoangvu12
Copy link
Owner

Can you list instances that require to login? I'll give it a look and try to implement it.

@HyperKids
Copy link
Author

HyperKids commented Oct 22, 2024

You can pull pretty much any URL from this uptime list, but I'll list a few below:

These ones say "Please #" when hitting the /api/v1/videos/<videoid> endpoint:

These ones say "This content isn't available" when hitting the /api/v1/videos/<videoid> endpoint:

I assume the "This content isn't available" errors are the Invidious instance getting blocked, and that there's nothing we can do about it.

@hoangvu12
Copy link
Owner

Ah, actually "Please #" is an error from YouTube, not from the Invidious. iv-org/invidious#4975

@HyperKids
Copy link
Author

Okay, I found an Invidious instance that is working (I've emailed you directly with the URL). Everything works when setting USE_INVIDIOUS_PROXY to true!

About the error, that's a big yikes - seems like instances everywhere are getting blocked.

@hoangvu12
Copy link
Owner

That's nice to hear, YouTube been blocking Invidious really hard recently. I guess we can't do anything until Invidious team comes up with a good solution.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants