Murmur is unable to read the certificates from */live/YOURURL/*.pam
Change the user in rc.d/murmur to root, then in the murmur.ini-file uname=murmur and erverything is fine.
What tool are you using to fetch the LetsEncrypt certificates? Couldn't you use the post-hook functionality to change the group ownership of the certificate/key to "murmur" and make sure the files are mode 440 ? This would be trivial with security/dehydrated.
I ask this because the requested change would be rather disruptive to existing users.
I use the Certbot (as root) tool from the ports, i also tried to change the permissions from the certs to murmur 440, but no success.
Everything else (nginx, tomcat etc) works normal with the root permissions not so murmur. But its funny that startup murmur as root, and let it run as murmur (uname=murmur in the ini-file) works perfectly.
I assume that a directory in the path to the certificate and key files is not allowing non-root users to access it.
The other applications and the change you propose likely read the certificate and key before dropping privileges.
I will investigate this further. Your feedback on this matter has been greatly appreciated.
Maybe you can change the startup-script to look into murmur.ini, if uname=murmur is set start it with root, otherwise startup as murmur (like now). With this "solution" you would not disrupt others installation, just an idea, don't know if this is "clean".
For new installations set uname to murmur
Thank you very much for investigate in this case.
Or just inform at the end of installation, that if letsencrypt/certs with root then change this and that. I think its the easy and clean way.
Any news on this?
(In reply to Mark Felder from comment #3)
> The other applications and the change you propose likely read the certificate and key before dropping privileges.
You're absolutely right. For example, apache starts httpd as root, reads config and certificate files and then forks with www user, passing the data to them. Same goes for nginx, probably. The problem with murmur can be observed because it doesn't change the user by default.
I don't think anything should be done on our (ports) side, it is a purely configuration complexity that user should be able to overcome himself.