Renew certificate done, but cannot start again ctlscript

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.

My domain is:
gtv6world.com

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.

After this, I tried:

systemctl status bitnami.service

And saw this error:

Failed to start LSB: bitnami init script

My web server is (include version):
Lightsail on Amazon. I don't know which version if there is any.

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

My hosting provider, if applicable, is:
Amazon, Lightsail

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

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):
I don't remember exactly but I think I'm not using Certbot (certbot --version and certbot-auto --version tell me that certbot is not installed). This goes in time to a few months so I'm not sure (if there is a method I could use to determine if I used it to initiate SSL I'd like to try it) but I think I didn't use it. I think I used this guide: Install SSL certificates on Bitnami stacks for Lightsail
But I'm also pretty sure I had setup the auto renew so I don't really know.
I believe that the SSL certificate worked fine until it expired after a few month, which is probably normal, except if I actually had auto renew. But anyway I just tried today to renew the certificate using this guide: Renew an SSL certificate on a Bitnami stack in Lightsail
Using the first method ( I couldn't even use the second one because I had no "letsencrypt" foler in "/etc".
I successfully stopped it, renew the cert (the expiration date is now in 90 days) but I cannot do:

sudo /opt/bitnami/ctlscript.sh start

It does not work, and the error doesn't give me much to work with. And my website is not accessible anymore...

Thanks in advance

2

we need to see more detailed log for bitnami to say about anything, you'd better visit bitnami forum. I think while they use certbot under the hood you are not supposed to touch it by yourself -

3 Likes
3

Is there any way to like delete all current certifications and retry from zero? I'll try to get more log for bitnami

4

sorry I havent used bitnami at all- and as your command ran was just starting bitnami, unrelated to certficiate renewal by itself so have no idea

4 Likes
5

Here are the logs for journalctl -xe:

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'.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 669 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 673 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 674 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 675 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 676 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 677 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 678 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 679 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 680 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 681 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 682 (php-fpm) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Unit process 694 (mysqld) remains running after unit stopped.Jan 28 14:26:49 ip-172-26-1-214 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 1228 and the job result is failed.Jan 28 14:26:49 ip-172-26-1-214 systemd[1]: bitnami.service: Consumed 1.939s 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.

6

It's ok, thank you for trying

1 Like
7

did you try rebooting? from log it failed to shutdown properly and ghost processes remain so reboot may fix that

3 Likes
8

Yep, I did reboot the Lightsail instance and it did not change anything

9

As orangepizza already said, there is not anything related to your certs in those errors.

The error log said to contact debian support at link below. You should try that

https://www.debian.org/support

3 Likes
10

It seems a bit far fetched to reach debian support but I agree with the fact that it is probably not linked to the certs.
I've found the exact method I used to initiate the certs, it is this one: Enabling HTTPS on your WordPress instance in Amazon Lightsail | Lightsail Documentation

So I used the bncert-tool, but I also remember that there was still a warning on the browser when visiting the website. This could have been linked to many things but I did some research at that time and found out that I could fix that by adding code to a file (probably /opt/bitnami/apache/conf/vhosts/wordpress-vhost.conf I think) by adding something related to FilesMatch or something like that.
Anyway I think it did not even work but it may also have broken some things now.

11

That's a good guide for Wordpress / Lightsail

Yeah, debian support maybe a stretch but we're not bitnami, Wordpress, or Lightsail experts either.

Usually I just refer bncert problems to the bncert troubleshooting guide. But, I"m not sure the problem you have is even in bncert it looks more fundamental than that. Still, if you have bncert issues you might see below link:

https://docs.bitnami.com/aws/how-to/understand-bncert/

4 Likes
12

However you have had certificates issued here is a list crt.sh | gtv6world.com, the latest being 2023-01-28.
So from being able to get a Let's Encrypt Certificate Issued you should be good to go. :slight_smile:

2 Likes
13

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