portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 528
See original GitHub issueThis 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]
Issue Analytics
- State:
- Created 3 years ago
- Comments:19 (8 by maintainers)
Top Results From Across the Web
No certificate present in SSL/TLS configuration for https port ...
When I install on jitsi-meet on a fresh server prosody reports errors. Prosody reports: portmanager: Error binding encrypted port for https: ...
Read more >Prosody errors: connections / binding encrypted port
Apr 02 09:57:03 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Read more >portmanager https letsencrypt certificate - Google Groups
Jan 22 23:25:05 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Read more >Discussion on: Self-hosted Jitsi server with authentication
I'm on Debian 10 Buster. First, "service prosody status" complains about "portmanager: Error binding encrypted port for https: No certificate ...
Read more >Certbot did not renew cert - Let's Encrypt Community Support
... prosody[24366]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
– 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 - 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.