Error binding encrypted port for https

I have a Ubuntu 20.4 server tha was running Jitsi a few months ago and has now stopped working but I have not altered anything.
I did a certbot renew and it reports they do not need renewing but I cannot connect to the server
I found that Prosody is failing to find the certs:
prosody.service - Prosody XMPP Server
Loaded: loaded (/lib/systemd/system/prosody.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-09-03 12:33:58 UTC; 4h 8min ago
Docs: Documentation – Prosody IM
Main PID: 1005 (lua5.2)
Tasks: 1 (limit: 9308)
Memory: 23.8M
CGroup: /system.slice/prosody.service
└─1005 lua5.2 /usr/bin/prosody

Sep 03 12:33:58 cider123.duckdns.org systemd[1]: Started Prosody XMPP Server.
Sep 03 12:34:16 cider123.duckdns.org prosody[1005]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Sep 03 12:34:16 cider123.duckdns.org prosody[1005]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

But I still have them:

root@cider123:/etc/prosody/certs# ls
auth.cider123.duckdns.org.crt cider123.duckdns.org.crt localhost.crt
auth.cider123.duckdns.org.key cider123.duckdns.org.key localhost.key
Could someone point me to any relavant info on how to solve the problem as I don’t want to re-install Jitsi?
PS I seem to have duplicate cert entries in conf.avail and conf.d and am not sure if this is correct:

/etc/prosody/conf.avail/cider123.duckdns.org.cfg.lua: key = “/etc/prosody/certs/cider123.duckdns.org.key”;
/etc/prosody/conf.avail/cider123.duckdns.org.cfg.lua: certificate = “/etc/prosody/certs/cider123.duckdns.org.crt”;
/etc/prosody/conf.avail/cider123.duckdns.org.cfg.lua: key = “/etc/prosody/certs/auth.cider123.duckdns.org.key”;
/etc/prosody/conf.avail/cider123.duckdns.org.cfg.lua: certificate = “/etc/prosody/certs/auth.cider123.duckdns.org.crt”;
/etc/prosody/conf.d/cider123.duckdns.org.cfg.lua: key = “/etc/prosody/certs/cider123.duckdns.org.key”;
/etc/prosody/conf.d/cider123.duckdns.org.cfg.lua: certificate = “/etc/prosody/certs/cider123.duckdns.org.crt”;
/etc/prosody/conf.d/cider123.duckdns.org.cfg.lua: key = “/etc/prosody/certs/auth.cider123.duckdns.org.key”;
/etc/prosody/conf.d/cider123.duckdns.org.cfg.lua: certificate = “/etc/prosody/certs/auth.cider123.duckdns.org.crt”;


Thanks

You can ignore those. websockets and bosh are proxied from nginx on localhost and that’s why it uses the unprotected HTTP link on 5280. Port 5281 is not used.
You can silence the error with disabling the ports jitsi-meet/prosody.cfg.lua-jvb.example at f4b46128bc9c59ed4ddf6a5229dedb5558e04924 · jitsi/jitsi-meet · GitHub