Unable to restart Lightsail/Nginx website after certificate renewal

Question

Hello,

Our website has been working fine (on Lightsail/Debian) since we got it initially set up 3 months ago. However, after renewing the Let's Encrypt certificate, we're unable to get it started up and running again.

The site is has a static IP and is not using any load balancers.

In addition to trying to restart the services as described below (*sudo /opt/bitnami/ctlscript.sh start*) we also rebooted the Lightsail instance which didnt help either.

We ran into issues following this [**AWS documentation**](https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-lets-encrypt-certificates-with-nginx#renew-a-lets-encrypt-certificate-nginx) on renewing certificates.

Everything up to Step 6: completed successfully as confirmed in the console:

```
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue
Waiting for verification...
Cleaning up challenges

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/collaboratevideo.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/collaboratevideo.com/privkey.pem
   Your certificate will expire on 2024-01-25. To obtain a new or
   tweaked version of this certificate in the future, simply run
   certbot again. To non-interactively renew *all* of your
   certificates, run "certbot renew"
 - If you like Certbot, please consider supporting our work by:

Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le
```

The problem is at the end of step 7 (7.6): "Enter the following command to start the underlying services that you stopped earlier: *sudo /opt/bitnami/ctlscript.sh start*"  When we attempt to restart the underlying services we get the following error:

```
bitnami@ip-x-x-x-x:~$ sudo /opt/bitnami/ctlscript.sh start
Starting services..
Job for bitnami.service failed because the control process exited with error code.
See "systemctl status bitnami.service" and "journalctl -xe" for details.
```

"systemctl status bitnami.service" returns:

```
bitnami@ip-x-x-x-x:~$ systemctl status bitnami.service
● bitnami.service - LSB: bitnami init script
     Loaded: loaded (/etc/init.d/bitnami; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2023-11-02 19:28:33 UTC; 3min 32s ago
    Process: 1542 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE)
      Tasks: 19 (limit: 542)
     Memory: 160.6M
        CPU: 1.099s
     CGroup: /system.slice/bitnami.service
             ├─662 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
             ├─666 php-fpm: pool www
             ├─667 php-fpm: pool www
             ├─668 php-fpm: pool www
             ├─669 php-fpm: pool www
             ├─670 php-fpm: pool www
             ├─671 php-fpm: pool www
             ├─672 php-fpm: pool www
             ├─673 php-fpm: pool www
             ├─674 php-fpm: pool www
             ├─675 php-fpm: pool www
             └─688 /opt/bitnami/mariadb/sbin/mysqld --defaults-file=/opt/bitnami/mariadb/conf/my.cnf --basedir=/opt/bitnami/mariadb --datadir=/bitnami/mariadb/data --sock>

Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 669 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 670 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 671 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 672 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 673 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 674 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 675 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 688 (mysqld) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: Failed to start LSB: bitnami init script.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Consumed 1.056s CPU time.
```

"journalctl" returns:

```
bitnami@ip-x-x-x-x:~$ journalctl -xe
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit bitnami.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit bitnami.service has entered the 'failed' state with result 'exit-code'.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 662 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 666 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 667 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 668 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 669 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 670 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 671 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 672 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 673 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 674 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 675 (php-fpm) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Unit process 688 (mysqld) remains running after unit stopped.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: Failed to start LSB: bitnami init script.
░░ Subject: A start job for unit bitnami.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit bitnami.service has finished with a failure.
░░ 
░░ The job identifier is 1029 and the job result is failed.
Nov 02 19:28:33 ip-x-x-x-x systemd[1]: bitnami.service: Consumed 1.056s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit bitnami.service completed and consumed the indicated resources.
Nov 02 19:28:33 ip-x-x-x-x sudo[1533]: pam_unix(sudo:session): session closed for user root
Nov 02 19:28:38 ip-x-x-x-x dhclient[409]: PRC: Renewing lease on eth0.
Nov 02 19:28:38 ip-x-x-x-x dhclient[409]: XMT: Renew on eth0, interval 9160ms.
Nov 02 19:28:38 ip-x-x-x-x dhclient[409]: RCV: Reply message on eth0 from fe80::d3:9bff:fea0:de96.
```

We would appreciate any help getting this resolved as our website is currently offline. Thank you!

Answer

Please share the results of the following commands:

sudo systemctl status bitnami.service
sudo journalctl -xe
sudo gonit
sudo gonit status

Also, share the content of /var/log/daemon.log

Unable to restart Lightsail/Nginx website after certificate renewal

Relevant content