-
Notifications
You must be signed in to change notification settings - Fork 90
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
Music not playing | There was an error while searching #213
Comments
[09.03.2024 - 00:33] [WARN ] | Loading error handlers...
[09.03.2024 - 00:33] [ERROR] | Error handlers inhibited!
[09.03.2024 - 00:33] [DEBUG] | Music engine "Erela" has been loaded
[09.03.2024 - 00:33] [ERROR] | Prisma ORM failed to load
[09.03.2024 - 00:33] [ERROR] | Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.
In case this error is unexpected for you, please report it in https://pris.ly/prisma-prisma-bug-report
[09.03.2024 - 00:33] [INFO ] | Slash commands have been loaded. Waiting for bot to finish initializing...
(node:139) [FSTWRN002] FastifyWarning: The routes plugin being registered mixes async and callback styles, which will result in an error in `fastify@5`
(Use `node --trace-warnings ...` to show where the warning was created) |
Seems like lavaplayer has an open issue (lavalink-devs/lavaplayer#69). It also seems you can use lavalink:fix-yt-400-v3 instead of lavalink:3 in docker to fix it. |
Duplicate of #208. You can refer there to fix the issue and I'll close this. Feel free to reopen if you still have the issue. |
Yes use lavalink:fix-yt-400-v3 fix the issue but temporary. You might need to keep an eye until they release new version that really fix this issue |
https://github.com/saher228/fix-lavalink-404/releases/tag/fix |
The text was updated successfully, but these errors were encountered: