Thank you for the pointers. I spent a fair amount of time trying to figure this out and here is what actually resolved the issue: Thank you for the clarification on where the certificates are installed. I did not know that although I had observed several locations with the certificate files. I think the original issue is because the terms of service for letsencrypt had not been agreed to. At least that was the error message that kept coming up when I was manually running the script to renew certificates (at least I think)
Steps to resolve issue:
Login to Console and login using FileZilla
Backup /home/user-data/ssl contents (Use Filezilla)
Delete /home/user-data/ssl contents but not the folder (Use Filezilla)
DO NOT DELETE ssl_private_key.pem (for SSH secure access)
Stop Nginx
Run command
sudo service nginx stop
Upgrade the certificates
sudo certbot certonly --standalone -d box.[mydomain].com -d [mydomain].net -d [mydomain].info
(I have multiple domains resolving to the same root domain)
Start Nginx
sudo service nginx start
Rerun Mail In A Box command
sudo mailinabox
- During the new run for mail in a box install, I was prompted to accept the terms of agreement for letsencrypt service
Login to Mail In A Box Web Interface
Select TLS and Provision certificates (this worked in provisioning and creating new certificates)
Logout Mail In A Box
Restart system from Console
Login back to Mail In A Box web interface and things were looking normal again with the new certificates
Reference website:that was helpful in me figuring out the above steps