the certificate for the websocket server expired 2 days ago, however the one for accessing the admin pages expires in 3 months. so it appears the lets encrypt certificate is auto updating just fine for the admin apache server but whatever asterisk is using for the websocket server doesn’t appear to autoupdate
Sorry but I can’t see how restarting Asterisk (automatically randomly when the certificate expires and is renewed) would be a good idea in any regard. That’s the only way you’d get Asterisk to understand the new certificate.
i restarted it, and the server. for whatever reason the server running at 8089 is using the original lets encrypt cert but it has since updated and the admin pages are using the correct one
ahhh, got it. in the advanced settings, the path for https crt and key was: /etc/asterisk/keys/integration/webserver.crt and /etc/asterisk/keys/integration/webserver.key but those cert files are older
those files show an update of May 17th (/etc/asterisk/keys/integration/webserver.key) but in /etc/asterisk/keys/ there are crts and key files updated as of today and are named the hostname.key and hostanme.crt