starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

Server registration fails - Unsupported certificate #3105

New issue

Open

opened 2026-02-20 22:18:07 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 22:18:07 -05:00

Owner

Originally created by @edshot99 on GitHub (Feb 17, 2026).

Description

A certificate generated with acme-client works for everything but the Mumble registration server.

Steps to reproduce

Start server
Wait
Error occurs

Mumble version

1.4.0

Mumble component

Server

OS

OpenBSD

Reproducible?

Yes

Additional information

An acme-client certificate on another server still works fine.
Self-signed certificates also work fine.
Using default TLS ciphers didn't change anything.

Relevant log output

<X>2026-02-17 16:31:14.445 SSL: OpenSSL version is 'LibreSSL 4.2.0'
<W>2026-02-17 16:31:14.445 Initializing settings from /etc/murmur.ini (basepath /etc)
<W>2026-02-17 16:31:14.446 Binding to address 0.0.0.0
<C>2026-02-17 16:31:14.447 MetaParams: Adding 1 intermediate certificates from certificate file.
<W>2026-02-17 16:31:14.974 MetaParams: TLS cipher preference is "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA"
<W>2026-02-17 16:31:16.527 Murmur 1.4.0 running on OpenBSD: OpenBSD 7.8 [x64]: Booting servers
<W>2026-02-17 16:31:34.395 1 => Server listening on 0.0.0.0:64738
<W>2026-02-17 16:34:52.457 1 => Registration failed: Error while reading: error:1404C413:SSL routines:ST_OK:sslv3 alert unsupported certificate

Screenshots

No response

Originally created by @edshot99 on GitHub (Feb 17, 2026). ### Description A certificate generated with acme-client works for everything but the Mumble registration server. ### Steps to reproduce 1. Start server 2. Wait 3. Error occurs ### Mumble version 1.4.0 ### Mumble component Server ### OS OpenBSD ### Reproducible? Yes ### Additional information An acme-client certificate on another server still works fine. Self-signed certificates also work fine. Using default TLS ciphers didn't change anything. ### Relevant log output ```shell <X>2026-02-17 16:31:14.445 SSL: OpenSSL version is 'LibreSSL 4.2.0' <W>2026-02-17 16:31:14.445 Initializing settings from /etc/murmur.ini (basepath /etc) <W>2026-02-17 16:31:14.446 Binding to address 0.0.0.0 <C>2026-02-17 16:31:14.447 MetaParams: Adding 1 intermediate certificates from certificate file. <W>2026-02-17 16:31:14.974 MetaParams: TLS cipher preference is "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA" <W>2026-02-17 16:31:16.527 Murmur 1.4.0 running on OpenBSD: OpenBSD 7.8 [x64]: Booting servers <W>2026-02-17 16:31:34.395 1 => Server listening on 0.0.0.0:64738 <W>2026-02-17 16:34:52.457 1 => Registration failed: Error while reading: error:1404C413:SSL routines:ST_OK:sslv3 alert unsupported certificate ``` ### Screenshots _No response_

deekerman added the

support

label

2026-02-20 22:18:07 -05:00

deekerman commented

2026-02-20 22:18:07 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Feb 18, 2026):

Is this a Let's Encrypt certificate?

@Krzmbrzl commented on GitHub (Feb 18, 2026): Is this a Let's Encrypt certificate?

deekerman commented

2026-02-20 22:18:07 -05:00

Author

Owner

@edshot99 commented on GitHub (Feb 18, 2026):

Yes

@edshot99 commented on GitHub (Feb 18, 2026): Yes

deekerman commented

2026-02-20 22:18:07 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Feb 19, 2026):

@davidebeatrici do you have any idea?

@Krzmbrzl commented on GitHub (Feb 19, 2026): @davidebeatrici do you have any idea?

deekerman commented

2026-02-20 22:18:07 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Feb 19, 2026):

How did you generate the certificate? Could you provide it here (only the public PEM, not the private key)?

@davidebeatrici commented on GitHub (Feb 19, 2026): How did you generate the certificate? Could you provide it here (only the public PEM, not the private key)?

deekerman commented

2026-02-20 22:18:07 -05:00

Author

Owner

@edshot99 commented on GitHub (Feb 19, 2026):

How did you generate the certificate?

acme-client with default non-staging Lets Encrypt server

Could you provide it here (only the public PEM, not the private key)?

Working

groovyexpress.com.fullchain.pem.txt

Not working

us1.groovyexpress.com.fullchain.pem.txt

@edshot99 commented on GitHub (Feb 19, 2026): > How did you generate the certificate? [acme-client](https://man.openbsd.org/acme-client.1) with default non-staging Lets Encrypt server > Could you provide it here (only the public PEM, not the private key)? Working [groovyexpress.com.fullchain.pem.txt](https://github.com/user-attachments/files/25428476/groovyexpress.com.fullchain.pem.txt) Not working [us1.groovyexpress.com.fullchain.pem.txt](https://github.com/user-attachments/files/25428479/us1.groovyexpress.com.fullchain.pem.txt)