From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mumble not connecting to umurmur archlinux server
Date: Sun, 01 May 2022 04:13:52 +0200 [thread overview]
Message-ID: <20220501021352.nEHFahdomHJhVL_k0-tqXpD8BvXN2xTvCpb7vT9MTyE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23461@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
Closed issue by egrain on void-packages repository
https://github.com/void-linux/void-packages/issues/23461
Description:
### System
voidlinux, x86_64 musl.
* package:
mumble | 1.3.1 | 2 | musl | 4M | Open source, low-latency, high quality voice chat for gaming
### Expected behavior
Connecting to the server.
### Actual behavior
(Voidlinux) Client saying: Remote host closed connection.
(Archlinux) Server saying: umurmurd[144061]: WARN: SSL handshake failed: -16512
### Steps to reproduce the behavior
Install a umurmur server on Archlinux and connect to it via mumble from a void musl machine.
### things I tried
After I got the SSL handshake failed error, I did the whole Openssl create key/certifcate thing on the voidmachine, used these for the umurmur server instead, still no worky.
Deleted the .config/Mumble/*.p12 certificates. Made new ones. Same result.
Archlinux mumble clients connect fine though without issue in both cases (creating the key/cert files for the server with either openssl/libressl).
Tomorrow I'll install an umurmur server on a voidmachine, to see if that works.
Thanks for reading. Thanks for helping. I'm new here, don't bite my head off. Thanks.
prev parent reply other threads:[~2022-05-01 2:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 20:02 [ISSUE] " egrain
2020-07-08 14:58 ` Johnnynator
2020-07-08 15:03 ` Johnnynator
2020-07-08 15:04 ` egrain
2020-07-08 15:05 ` Johnnynator
2020-07-08 15:27 ` egrain
2020-07-08 15:36 ` egrain
2020-07-08 17:59 ` egrain
2020-07-08 18:11 ` egrain
2020-07-10 7:52 ` codingHahn
2020-10-22 11:27 ` egrain
2022-04-17 2:06 ` github-actions
2022-05-01 2:13 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220501021352.nEHFahdomHJhVL_k0-tqXpD8BvXN2xTvCpb7vT9MTyE@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).