Dear Maintainer,
mumble-server complains about, not being able to read the certificates, certbot created for my
nginx server.
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
* I wanted to properly verifiy my domain via letsencrypt, since I
already use a Webserver anyways.
* Honestly, the workaround to the issue was fairly obvious: just change the
permissions to given directories/files, given in the error messages:
$ chmod 755 /etc/letsencrypt/live/
$ chmod 755 /etc/letsencrypt/archive/
$ chmod 744 /etc/letsencrypt/archive/privkey1.pem
However, this seems quite lazy and insecure?! At least letyencrypt
discourages this "workaround", so I wanted to report it just to be sure.
Especially since this "workaround" is specifically mentioned in your WIKI:
https://wiki.mumble.info/wiki/Obtaining_a_Let%27s_Encrypt_Murmur_Certificate
* It works, but I am not happy/convinced
* I am not sure if this issue is more related to letsencrypt/certbot
then to mumble-server to be honest, but since mumble-server is the
first program for me to show this kind of issue, I decided to report
it here. Also, I didn't come accross this issue under Debian 10.
I would have expected mumble-server to work out of the box with these
certificates, especially since I have the feeling it did work already.