Error on prosody without any reasons - No key present in SSL/TLS configuration for https port 5281

Then jicofo is either not running or not able to start at all.

i am also getting same issue did you find it

Another one who has the same problem, is there any solution? for the error

portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

As has been mentioned above:

Background

In a default setup the prosody instance used with Jitsi does not need to terminate TLS traffic itself. Instead, the BOSH extension of prosody is accessed through a reverse proxy (usually nginx) which does the TLS handling and forwards external traffic to prosody’s bosh listener via plain http. That’s why you should have the option consider_bosh_secure=true in your prosody config, as also explained at https://prosody.im/doc/setting_up_bosh

The Error

If prosody is configured to use the bosh module, it defaults to listening to both http and https connections on ports 5280 and 5281 respectively. However, in a default Jitsi setup, the certificate that prosody wants to use for listening on port 5281 does not exist. In consequence, Prosody complains about this missing certificate and key file and throws the infamous error:

portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Nevertheless, unless your setup diverts from the default setup you can simply ignore this error message. Prosody will still listen on port 5280 for plain http connections and that is all thats needed for a working default Jitsi setup.

Get rid of the error message

You can configure prosody to not listen for https connections on port 5281 by simply adding the following line to your prosody config file:

https_ports = { }

This tells prosody to not even attempt to open an https ports and, thus, the error you are worried about is neither thrown nor logged in the error log.

1 Like