Voice requires encryption

[Wikijito7]

As stated here, Discord will enforce E2EE when a user (or bot) is trying to connect to a Voice Channel. This would had a grace period on which clients could connect using the legacy non encrypted voice. It seems that the grace time is over and now Discord is returning an error when trying to connect to a VC without encryption.

It seems that we'll have to implement DAVE, Discord's Audio and Video End-to-End Encryption, if we want to connect to a VC. Is it on the roadmap?

I'll add the log as well.

[DefaultDispatcher-worker-6] ERROR dev.kord.voice.gateway.DefaultVoiceGateway - 
java.lang.IllegalStateException: Voice Gateway (689108711452442667) closed: 4016 Unknown encryption mode.
    at dev.kord.voice.gateway.DefaultVoiceGateway.handleClose(DefaultVoiceGateway.kt:233)
    at dev.kord.voice.gateway.DefaultVoiceGateway.start(DefaultVoiceGateway.kt:112)
    at dev.kord.voice.gateway.DefaultVoiceGateway$start$1.invokeSuspend(DefaultVoiceGateway.kt)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:35)
    at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:101)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
    at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:829)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)

[DRSchlaubi]

I don't think this is related to E2EE (since no libs except for the c++ one supports it), this is rather related to #990, since the voice stuff is largely maintained by @psmarko he would have to speak to that. In the meantime you can use lavalink.kt, which supports the new encryption mode

[Wikijito7]

I've tested compiling locally #990 and it seems to work now using my current config (using kord-voice with lavaplayer). Maybe we could take that PR and try to finish it/merge it. What do you think @DRSchlaubi @psmarko?

bot-1            | HttpClient: RESPONSE: 200 OK
bot-1            | METHOD: GET
bot-1            | FROM: REDACTED
bot-1            | BODY Content-Type: application/json; charset=UTF-8
bot-1            | BODY START
bot-1            | [{"name":"Hit FM Summer Hits","url":"https://radio4.dixi.md/listen/hit_fm_summer_hits/hitfmsummerhits128.aac","favicon":"","countrycode":"MD"}]
bot-1            | BODY END
bot-1            | [lava-daemon-pool-playback-1-thread-1] INFO com.sedmelluq.lava.common.natives.NativeLibraryLoader - Native library libmpg123-0: loading with filter com.sedmelluq.discord.lavaplayer.natives.ConnectorNativeLibLoader$$Lambda/0x00007f43ac3d31c0@761b02a0
bot-1            | [lava-daemon-pool-playback-1-thread-1] INFO com.sedmelluq.lava.common.natives.NativeLibraryLoader - Native library connector: loading with filter null
bot-1            | [lava-daemon-pool-playback-1-thread-1] INFO com.sedmelluq.lava.common.natives.NativeLibraryLoader - Native library connector: successfully loaded.

[psmarko]

The last work I've done is actually with #990. IIRC that version doesn't actually implement the encryption logic yet. There were some design choices I haven't worked through either after trying to pick it up from Luke.

I think the fix you're seeing in that PR, is simply that Kord is aware of the new modes, and won't throw the unknown mode exception. IIRC it won't actually use it or something along those lines.

Unfortunately, I'm out the country for a few more weeks and don't have a dev environment nor my local version of #990.

Is this exception happening all the time now? If so, we could probably just update the enum with the missing modes, and Kord won't complain (hopefully, haven't investigated it yet).

[Wikijito7]

Pretty far it doesn't crash anymore. I could try to debug to find what's going on and determine why it works now. It may be what psmarko said, but I'll have to confirm. I'm going to try to find some time tomorrow to check it and I'll get back to you.

[H4kt]

Stumbled upon this just today. Voice functionality worked fine just a couple of days ago.

[chimbersaw]

I encounter this issue from time to time. Restarting doesn't help but after some time it just goes away. idk what causes this

[Wikijito7]

Exactly, it worked fine until a couple of days ago, where it stopped working entirely, getting the same error. As I can see in other API wrappers, it isn't just a Kord error and it seems like Discord is trying new things, breaking the old encryption.

[Wikijito7]

Update: I've generated a local version of #990 and it works once again. It seems that it works with that encryption enum. @DRSchlaubi @psmarko sorry for the mention, but maybe that part should be merged. If I have time, I could try to debug it, as i said in the past 😅 I didn't had time between work and personal stuff.

[chimbersaw]

I encounter this issue from time to time

Happened again randomly. Wanted to try #990 as suggested but both snapshot repos mentioned in the readme don't work. I guess i need to compile it locally

[chimbersaw]

Unfortunately I guess it's time to switch to a different discord wrapper now