Closed DlgshKurd closed 8 months ago
[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 (https://github.com/lavalink-devs/lavaplayer/issues/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.
It also seems you can use lavalink:fix-yt-400-v3 instead of lavalink:3 in docker to fix it.
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
I posted a ready-made fix on v4 and v3. Use it!
https://github.com/saher228/fix-lavalink-404/releases/tag/fix