Closed Hountez closed 4 months ago
To narrow things down, could you create a certificate exclusively for the domain Mumble uses to see if that works as expected?
Hello, sadly not at the moment but i think it is not necessary anymore, the domain runs at cloudflare and the sub-domain set in the SRV record was proxied through it (connection to the server works anyway), and it seems like this messes up the certificate check in some way.
I disabled the cloudflare proxy for the subdomain listed in the SRV entry and now no certificate error is shown.
I do not know why the certificate check would have a problem with the proxy since first: only http and https ports should be proxied by cloudflare in the free plans and second the connection is made to the domain listed in the cert so the check should work as far as I can tell without knowing what's going on behind the scenes.
Hm. No idea either. If it is no longer an issue for you, I'll close this issue though as there is no way we can figure things out without a way to reproduce the issue.
Description
Upon connecting to my server the client complains about the Certificate i use (letsencrypt), i registered multiple domains in the certificate including the one Mumble uses but I get as error that the hostname does not match any of the list of valid hosts on the certificate.
The domain used is listed as "DNS" under certificate details, this is how letsencrypt creates the certificate if multiple domains are used in one certificate and does not pose a problem in any other application i use the certificate.
The domain i use is "deutschritter.eu" if you want to test it.
Let me know if you need further information.
Steps to reproduce
Connect to the server and get greeted with an error message
Mumble version
1.3.4-1
Mumble component
Both
OS
Linux
Reproducible?
Yes
Additional information
OS: Debian 11 Mumble server installed with APT
Relevant log output
No response
Screenshots
No response