-
-
Notifications
You must be signed in to change notification settings - Fork 4k
Description
Which package is this bug report for?
voice
Issue description
- open a voice connection
- try to play an audio ressource
- see the error
Error: Cannot play audio as no valid encryption package is installed.
-
Install sodium, libsodium-wrappers, or tweetnacl.
-
Use the generateDependencyReport() function for more information.
at Object.fallbackError (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:166:9)
at Networking.encryptOpusPacket (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:663:17)
at Networking.createAudioPacket (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:653:50)
at Networking.prepareAudioPacket (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:599:33)
at VoiceConnection.prepareAudioPacket (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:1412:29)
at AudioPlayer._preparePacket (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:981:18)
at AudioPlayer._stepPrepare (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:962:14)
at prepareNextAudioFrame (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:87:29)
at audioCycleStep (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:76:3)
at Timeout._onTimeout (file:///D:/Users/user/Documents/Bot/node_modules/@discordjs/voice/dist/index.mjs:83:45)
Code sample
No response
Package version
discord.js@14.6.0 @discordjs/opus@0.8.0 ffmpeg-static@5.1.0 libsodium-wrappers@0.7.10 @discordjs/voice@0.13.0
Node.js version
v16.17.1
Operating system
windows 10 and ubuntu 22.04 server
Priority this issue should have
High (immediate attention needed)
Which partials do you have configured?
Not applicable (subpackage bug)
Which gateway intents are you subscribing to?
Not applicable (subpackage bug)
I have tested this issue on a development release
No response