This is about murmur on GNU/Linux
If a certificate is specified in the config file, but it has a wrong order of helper cert and cert, or a typo in the path or there is an permission error and the cert fails to load, the server is just starting up any way and generates a self signed cert which is stored in the database.
This is a really stupid behaviour, the reason is obvious:
If the the specified cert couldn't be loaded, this has to stop the starting up process.
The Admin has chosen to use his own cert by specifying this in the config file, murmurd has to respect the users choice and not to ignore this choice by making it's own decisions.
As long as you don't look in the log file the server seems to start up completely normal, but the cert you want is just gone.
The self signed cert that is generate by murmurd has to be delete out of the database by calling murmurd with -wipessl, only than you can use your own cert again. This is not even noted in the manpage of murmurd. You have to search the internet to even find this way go back to the configuration you want. (Are want the people to use this self generated cert by force?)