[Bug Report] None of the provided encryption modes are supported

[AnalogBot]

Bug Description

Starting today, the bot is unable to join the voice channel. It joins and leaves over and over until I issue a stop command while it spamms the error [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"] in the log.

Music source doesn't seem to make a difference. This happens when we try to play local files as well as URLs.

[20:40:07] [INFO] [Settings]: serversettings.json loaded from /jmb/config/serversettings.json
[20:40:09] [INFO] [JDA]: Login Successful!
[20:40:10] [INFO] [JMusicBot]: JMusicBot
[20:40:10] [INFO] [WebSocketClient]: Connected to WebSocket
[20:40:10] [INFO] [JDA]: Finished Loading!
[20:42:06] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[20:42:06] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[20:42:07] [INFO] [NativeLibraryLoader]: Native library libmpg123-0: loading with filter com.sedmelluq.discord.lavaplayer.natives.ConnectorNativeLibLoader$$Lambda$271/0x00000008003de440@73264fd5
[20:42:07] [INFO] [NativeLibraryLoader]: Native library connector: loading with filter null
[20:42:07] [INFO] [NativeLibraryLoader]: Native library connector: successfully loaded.
[20:42:08] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[20:42:09] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]

Steps to Reproduce

1. Issue a play command
2. Bot joins and leaves voice channel over and over
3. Issue a stop command
4. Bot stops trying and failing to join.

Expected Result

Expected bot to join voice and play the music indicated with the play command.

Debug Output

System Properties:
  java.version = 11.0.24
  java.vm.name = OpenJDK 64-Bit Server VM
  java.vm.specification.version = 11
  java.runtime.name = OpenJDK Runtime Environment
  java.runtime.version = 11.0.24+8-alpine-r0
  java.specification.version = 11
  os.arch = amd64
  os.name = Linux

JMusicBot Information:
  Version = 0.4.3
  Owner = 220737771172659211
  Prefix = !
  AltPrefix = %
  MaxSeconds = 0
  NPImages = false
  SongInStatus = true
  StayInChannel = false
  UseEval = false
  UpdateAlerts = true

Dependency Information:
  JDA Version = 4.4.1_353
  JDA-Utilities Version = 3.0.5
  Lavaplayer Version = 2.2.1

Runtime Information:
  Total Memory = 502
  Used Memory = 28

Discord Information:
  ID = 634691219334889483
  Guilds = 1
  Users = 5

Additional Info

No response

Checklist

• [x] I have looked for information about this within the documentation
• [x] I have searched for similar issues on the issues page
• [x] I am using an official release from the releases page

JMusicBot Version

0.4.3

[Tourfaint]

I can' reproduce. I turned on a bot, played a local file and everything played fine.

[AnalogBot]

The problem seems to have disappeared today without touching anything.

[LucentW]

this issue just happened to me too; restarting the bot doesn't help and it seems Discord is rolling it out gradually on all VC sessions

[22:00:04] [INFO] [JMusicBot]: Loaded config from /home/lucent/discord-music/config.txt
[22:00:04] [INFO] [Settings]: serversettings.json loaded from /home/lucent/discord-music/serversettings.json
[22:00:05] [INFO] [JDA]: Login Successful!
[22:00:05] [INFO] [WebSocketClient]: Connected to WebSocket
[22:00:05] [INFO] [JDA]: Finished Loading!
[22:00:14] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[22:00:15] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[22:00:16] [INFO] [NativeLibraryLoader]: Native library libmpg123-0: loading with filter com.sedmelluq.discord.lavaplayer.natives.ConnectorNativeLibLoader$$Lambda$284/0x93aec428@d94c63
[22:00:16] [INFO] [NativeLibraryLoader]: Native library connector: loading with filter null
[22:00:16] [INFO] [NativeLibraryLoader]: Native library connector: successfully loaded.
[22:00:16] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[22:00:17] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
[22:00:18] [ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]

JDA got an update yesterday (https://mvnrepository.com/artifact/net.dv8tion/JDA/5.6.0) and one about an hour ago (seeing their GitHub releases), the 4.4.1_353 version advertised by the POM has seemingly been pulled in the meantime 🤔

[Tourfaint]

Yeah, the bug happens depending on server region, this should be reopened. Edit: it's still very hard to consistently reproduce. Seems that 0.4.2 version doesn't have this bug and 4.3 has, but even in 4.3 i can't consistently reproduce it when changing regions in a channel.

[Kalium919]

updates on this? i got the same error today

[Morilli]

Apparently discord has deprecated (and removed support for) some old transport encryption modes: https://discord.com/developers/docs/topics/voice-connections#transport-encryption-modes. It's now required to update the JDA dependency to get support for the new encryption modes: https://github.com/Morilli/MusicBot/commit/63a0a45df4d4b076964f6587f6fcc0ce4e8e3730

[Schnoz94]

Apparently discord has deprecated (and removed support for) some old transport encryption modes: https://discord.com/developers/docs/topics/voice-connections#transport-encryption-modes. It's now required to update the JDA dependency to get support for the new encryption modes: Morilli@63a0a45

And how do you do that?

[othello777]

And how do you do that?

by applying the commit they pointed to. download it as a patch and run git apply mypatch.patch and you should have a working bot again

[vincentremon]

Hello. I'm not sure to understand / know how to "download it as a patch and run git apply mypatch.patch" :-
Is this patch applied on the latest 0.4.3 version ?