jitsi-meet: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 528

This Issue tracker is only for reporting bugs and tracking code related issues.

Description

When I install on jitsi-meet on a fresh server prosody reports errors.

Current behavior

Prosody reports: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 528

Expected Behavior

systemd[1]: Started Prosody XMPP Server.

Possible Solution

Add these https_certificate and https_key to /etc/prosody/conf.d/jitsi.example.com.cfg.lua

https_certificate = "/etc/prosody/certs/jitsi.example.com.crt";
https_key =  "/etc/prosody/certs/jitsi.example.com.key";

Steps to reproduce

Install jitsi meet on a fresh server.

$ sudo apt install jitsi-meet
$ sudo systemctl status prosody
$ sudo cat /var/log/prosody/prosody.log

Environment details

$ uname -a 
Linux 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1+deb10u1 (2020-04-27) x86_64 GNU/Linux

$ apt list jicofo jitsi-* --installed
jicofo/stable,now 1.0-549-1 all [installed,automatic]
jitsi-meet-prosody/stable,now 1.0.4025-1 all [installed,automatic]
jitsi-meet-turnserver/stable,now 1.0.4025-1 all [installed,automatic]
jitsi-meet-web-config/stable,now 1.0.4025-1 all [installed,automatic]
jitsi-meet-web/stable,now 1.0.4025-1 all [installed,automatic]
jitsi-meet/stable,now 2.0.4468-1 all [installed]
jitsi-videobridge2/stable,now 2.1-183-gdbddd169-1 all [installed,automatic]

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 19 (8 by maintainers)

Most upvoted comments

@Blueshawk - Exactly. For people who are trying hard to troubleshoot an issue, such misleading errors just add to a lot of unnecessary work, which could be prevented by having misleading errors eradicated through properly documented configuration beforehand.

tacerus on Apr 26, 2021

– https_ports = { }; – Remove this line to prevent listening on port 5284 <-- this comment is causing confusion.

It should say what it does if enabled, not this double negative.

–https_ports = { }; – uncomment this line to enable listening on port 5284

But more importantly, for those of us troubleshooting a gray screen with .js errors it means we just went on yet another snipe hunt.

Blueshawk on Jan 22, 2021

Sure, I’ve already installed Jitsi on several servers.

On Jan 7, 2021, at 7:45 AM, Jan-Peter Rühmann notifications@github.com wrote:

Im getting it too, any solution?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jitsi/jitsi-meet/issues/6473#issuecomment-756196826, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOKIXBWAGWCX3CN65HI2S4LSYXJJZANCNFSM4MUAY4XQ.

draconid719 on Jan 7, 2021

Find your configuration file in /etc/prosody/conf.d, open it and you should see a line you can uncomment to get rid of that error.

crouchingtigerhiddenadam on Jun 15, 2020

I’m getting this error as well Jul 31 02:40:50 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281 Jul 31 02:40:50 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

VirtualHost "__OVERWRITE_WITH_HOSTNAME__"
    authentication = "anonymous"
    ssl = {
        key = "/home/ubuntu/efs-ssl/__OVERWRITE_WITH_HOSTNAME__.key";
        certificate = "/home/ubuntu/efs-ssl/__OVERWRITE_WITH_HOSTNAME__.crt";
    }
    modules_enabled = {
        "bosh";
        "pubsub";
        "websocket";
    }
    c2s_require_encryption = false
    consider_bosh_secure = true

VirtualHost "auth.__OVERWRITE_WITH_HOSTNAME__"
    authentication = "internal_plain"
    admins = { "focus@auth.__OVERWRITE_WITH_HOSTNAME__"}
    modules_enabled = {
        "bosh";
        "pubsub";
        "websocket";
    }
    ssl = {
        key = "/home/ubuntu/efs-ssl/auth.__OVERWRITE_WITH_HOSTNAME__.key";
        certificate = "/home/ubuntu/efs-ssl/auth.__OVERWRITE_WITH_HOSTNAME__.crt";
    }
    c2s_require_encryption = false
    consider_bosh_secure = true
Component "conference.__OVERWRITE_WITH_HOSTNAME__" "muc"
Component "jitsi-videobridge.__OVERWRITE_WITH_HOSTNAME__"
    component_secret = "OTBDEV"
Component "focus.__OVERWRITE_WITH_HOSTNAME__"
    component_secret = "OTBDEV"

ecommerce-technician on Jul 31, 2020

That’s fine @damencho. As it’s an issue and suggested fix where on the community do you want me to add this?

With respect, I’m following contribution guidelines: https://github.com/jitsi/jitsi-meet/blob/master/CONTRIBUTING.md

crouchingtigerhiddenadam on Apr 29, 2020