Andrew Lawrence DeMarsh: > Package: mumble-server > Version: 1.3.0~git20190125.440b173+dfsg-2 > Severity: important > > Dear Maintainer, > > When adding SSL Certs from LetsEncrypt to the mumble server that was > operating with self signed certs it was found that the Server would > fail to start up with the following error: > > root@mumble:/# murmurd -ini /etc/mumble-server.ini -v > <W>2019-09-14 23:40:58.428 SSL: OpenSSL version is 'OpenSSL 1.1.1c 28 May > 2019' > <W>2019-09-14 23:40:58.428 Initializing settings from > /etc/mumble-ff-server.ini (basepath /etc) > > <C>2019-09-14 23:40:58.430 MetaParams: Failed to find certificate matching > private key. > <F>2019-09-14 23:40:58.430 MetaParams: Failed to load SSL settings. See > previous errors. > > This is not a permissions issue as the certificates are in roots home folder > and it is running as root. > These are standard SSL Cert from letsencrypt recieved using acme.sh.
It's unusual to run mumble-server/murmur as root, and also unusual to have SSL certificates in the root user home folder. Mumble is typically started as root but then the user switched to the user listed in the configuration file in /etc/mumble-server.ini. The default setting is: "uname=mumble-server". Have you set the 'uname' setting to "root"? The Mumble wiki has some LetsEncrypt instructions here: https://wiki.mumble.info/wiki/Obtaining_a_Let%27s_Encrypt_Murmur_Certificate note that the instructions above discuss the folders in the path needing "directory execute permissions" for the server to be able to read the certificates. Other users have had issues getting mumble-server with LetsEncrypt certificates but eventually got it working after discussing it in the #mumble IRC channel on irc.freenode.net. If you get the chance to ask there I think they can help debug the issue further. -- Chris -- Chris Knadle chris.kna...@coredump.us
