Website not working after renewing certificate

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

I ran this command:sudo /opt/bitnami/ctlscript.sh start

It produced this output: Job for bitnami.service failed because the control process exited with error code.
See "systemctl status bitnami.service" and "journalctl -xe" for details.

My web server is (include version):Apache (Bitnami)

The operating system my web server runs on is (include version):"Debian GNU/Linux 11 (bullseye)

My hosting provider, if applicable, is: AWS Lightsail (LAMP not the wordpress)

I can login to a root shell on my machine (yes or no, or I don't know): - Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): - No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):- certbot 1.12.0

Guide I followed - Tutorial: Using Let’s Encrypt SSL certificates with your LAMP instance in Amazon Lightsail | Lightsail Documentation

My website and app was working perfectly until i tried to renew my website and the end message was successful for renew but when i check my website ssl exiry it same as before renew (09 Feb 2023). Today i wen back to same guide and followed the step 7 : Step 7: Create links to the Let’s Encrypt certificate files in the Apache server directory and ran ```
sudo /opt/bitnami/ctlscript.sh stop then sudo /opt/bitnami/ctlscript.sh start but it start showing the error.

Job for bitnami.service failed because the control process exited with error code.
See "systemctl status bitnami.service" and "journalctl -xe" for details.

The journalctl -xe response

Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 105610>
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: Failed to start LSB: bitnami init sc>
░░ 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 107777 and the job result is failed.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Consumed 1.383s CPU>
░░ 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.
Feb 04 03:08:39 ip-172-26-3-59 sshd[1057688]: Received disconnect from 52.174.2>
Feb 04 03:08:39 ip-172-26-3-59 sshd[1057688]: Disconnected from authenticating >
lines 1616-1638/1638 (END)
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056103 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056104 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056105 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056106 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056107 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056108 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Unit process 1056109 (php-fpm) remains running after unit stopped.
Feb 04 03:08:33 ip-172-26-3-59 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 107777 and the job result is failed.
Feb 04 03:08:33 ip-172-26-3-59 systemd[1]: bitnami.service: Consumed 1.383s 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.
Feb 04 03:08:39 ip-172-26-3-59 sshd[1057688]: Received disconnect from 52.174.28.224 port 58200:11: Bye Bye [preauth]
Feb 04 03:08:39 ip-172-26-3-59 sshd[1057688]: Disconnected from authenticating user root 52.174.28.224 port 58200 [preauth]

sudo /opt/bitnami/ctlscript.sh status
apache not running
mariadb not running
php-fpm not running

My website is down and i am not able to find solutions for this. I also noob in these. Please help me out

2

Have you tried rebooting the entire system?

3 Likes
3

Yes i tired just after you told me to. I restart lightsail instance by console but still same error.

4

This won't (necessarily) help with the problem you describe. But, if you don't absolutely need a wildcard cert you would be better off following the below tutorial and using bncert. The bncert tool can automatically renew certs for you. The tutorial you followed requires a manual renewal. Renewals are recommended every 60 days.

https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-lets-encrypt-certificates-with-wordpress

Many noob's (as you describe yourself) think a wildcard is "better" without realizing the difficulties it can cause. If you just have a small number of domain names that won't change often it may be much easier to not use a wildcard and automate with bncert.

3 Likes
6

Right now first priority is to make website up and running then i will delete the existing certificate and get one with the bncert. I am stuck. Now my website page back to default debian page.Please help me out from this

7

I am not a bitnami expert. But have you tried looking at the output of those commands for further debug information?

By the way, your Apache Server is responding to HTTP requests It is just the HTTPS request that are failing. So the status message that shows Apache is not running seems incorrect.

You might try Bitnami Support

3 Likes
8

I second this. Bitnami is such a different (weird) system than regular systems that there's almost noone with knowledge of it on this Community.

4 Likes
9

There are some misconfigurations in settings and that might not be a big thing for someone who know these things and i really don't want to mess up with our server because of data we have and i am not able to access phpmyadmin and this is very important and i can't lose it. As per the descriptions i mentioned (I can provide more) what you think where our system having an issue(s).

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.