9/3/2023 0 Comments Creating mumble certificateThe guide below provides information on how to setup a Discord bot. In "auto" or "manual" modes, the bridge can be controlled in Discord with the following commands: !DISCORD_COMMAND linkĬommands the bridge to join the Discord channel the user is in and the Mumble serverĬommands the bridge to leave the Discord channel the user is in and the Mumble serverĬommands the bridge to unlink, then link again.Ī Discord bot is required to authenticate this application with Discord. It can not be controlled in this mode and quits when the program is stopped The bridge starts up and immediately connects to both Discord and Mumble voice channels. It will join the voice channels when issued the link command and will leave with the unlink command The bridge starts up but does not connect immediately. The bridge will leave both voice channels once there is no one on either end It can be either manually linked (see below) or will join the voice channels when there's at least one person on each side. The bridge can be run with the follow modes: auto See the help documentation for all the options mumble-discord-bridge -help env file located in the working directory. Several configuration variables must be set for the binary to function correctly.Īll variables can be set using flags or in the environment. The site even offers a free tier for those who want to try out Mumble Discord Bridge. If hosting this application yourself seem like an difficult task please consider PatchCord.io. Mumble Discord Bridge can be hosted on any server or computer and ships in a Docker container for convenience. It was built with the hope that people can continue to use the voice application of their choice. p12 format.Mumble Discord Bridge is an open source Go application to bridge the audio between Mumble and Discord. I have tried exporting from both "certificates" and "my certificates" in keychain, clicking on the certificate individually and then r-clicking and asking to export to docs with a password as a personal info exchange. Thank you very much for the reply! I'm new to this so bear with me, but I believe it is a client certificate as I followed the steps on the mumble site for creating a free certificate via the two companies in this thread ( ), and then I exported them as per the instructions (tried one, got the error, made the other). I have also reinstalled both Mumble and Murmur. Both say they were signed by an unknown authority, but I tried telling the Comodo one to be trusted and it still doesn't work. p12 and were exported with Keychain access. It's not a big glitch as I can still use both services fine, but as it was recommended to create a secure Certificate, I wanted to try one. 14:38:31.298 1 => Connection closed: Īs soon as I switch back to the self-made Certificate auto-created by Mumble on first use, the server comes back online. 14:38:31.297 1 => SSL Error: No certificates could be verified 14:38:31.296 1 => SSL Error: The root CA certificate is not trusted for this purpose I tried using the certificate wizard to import a certificate created by StartCom and Comodo, but upon switching to either of them, my server disconnects and says " Server connection failed: The remote host closed the connection." If Terminal is open, it says: Mumble and Murmur work well (newest releases), but I have an odd issue. Sorry to pester you, I'm on Mac OSX 10.8.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |