[Ghost] How to delete SSL Certificate in Bitnami Ghost Image configured by bncert tool?

[Harsh-2002]

Describe your issue as much as you can

I want to setup my Ghost EC2 instance with Cloudfront but the issue I'm getting is my domain is redirecting to EC2 DNS. Previously i used this instance to setup SSL with domain. I don't know what causing the issue. To check if everything is properly configured in Cloudfront I launched another instance with Ghost image and this time it is working perfectly, I used AWS certificate manager to setup SSL.

So i think the issue is with the Previously configured SSL certificate or may be other thing that i didn't know.

Please help. If you want I can share my server ssh access.

[jotamartos]

I'm getting is my domain is redirecting to EC2 DNS

Please look for any redirection-related line in the /opt/bitnami/apache/conf/bitnami/bitnami.conf file and the ones inside the /opt/bitnami/apache/vhosts folder (specially the ghost-related ones).

Once you remove the redirection, please restart Apache

sudo /opt/bitnami/ctlscript.sh restart apache

[Harsh-2002]

Now I'm facing another issue

apache already running
ghost not running
mysql already running

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

[Harsh-2002]

           total        used        free      shared  buff/cache   available

Mem: 975Mi 438Mi 118Mi 0.0Ki 418Mi 400Mi
Swap: 634Mi 0.0Ki 634Mi

sudo 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 Wed 2023-09-20 09:55:16 UTC; 3min 44s ago
Process: 1455 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE)
Tasks: 298 (limit: 1146)
Memory: 697.0M
CPU: 2.479s
CGroup: /system.slice/bitnami.service
├─664 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
├─666 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
├─667 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
└─991 /opt/bitnami/mysql/bin/mysqld --defaults-file=/opt/bitnami/mysql/conf/m>

Sep 20 09:55:16 ip-172-31-6-79 bitnami[1622]: ## 2023-09-20 09:55:16+00:00 ## INFO ## Runn>
Sep 20 09:55:16 ip-172-31-6-79 bitnami[1622]: ## 2023-09-20 09:55:16+00:00 ## INFO ## Runn>
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Control process exited, code=e>
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Failed with result 'exit-code'.
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 664 (httpd) remai>
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 666 (httpd) remai>
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 667 (httpd) remai>
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 991 (mysqld) rema>
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: Failed to start LSB: bitnami init script.
Sep 20 09:55:16 ip-172-31-6-79 systemd[1]: bitnami.service: Consumed 1.688s CPU time.

Sep 20 10:03:39 ip-172-31-6-79 bitnami[1932]: ## 2023-09-20 10:03:39+00:00 ## INFO ## Runn>
Sep 20 10:03:39 ip-172-31-6-79 bitnami[1932]: ## 2023-09-20 10:03:39+00:00 ## INFO ## Runn>
Sep 20 10:03:39 ip-172-31-6-79 systemd[1]: bitnami.service: Control process exited, code=e>
░░ Subject: Unit process exited
░░ 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.
Sep 20 10:03:39 ip-172-31-6-79 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'.
Sep 20 10:03:39 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 664 (httpd) remai>
Sep 20 10:03:39 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 666 (httpd) remai>
Sep 20 10:03:39 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 667 (httpd) remai>
Sep 20 10:03:39 ip-172-31-6-79 systemd[1]: bitnami.service: Unit process 991 (mysqld) rema>
Sep 20 10:03:39 ip-172-31-6-79 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 325 and the job result is failed.
Sep 20 10:03:39 ip-172-31-6-79 systemd[1]: bitnami.service: Consumed 1.671s 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.
lines 2265-2298/2298 (END)

[jotamartos]

Hi,

Did you make any change lately to the Ghost's folder (/opt/bitnami/ghost)? Do you get any error message when starting the Ghost service?

sudo /opt/bitnami/scripts/ghost/start.sh

[Harsh-2002]

Hello, it's currently working as expected. I would like to inquire about a specific situation. When I run the following command sudo su ghost -c "ghost backup" to perform a backup in Ghost, it prompts me to enter an email and password. Is there a way to execute this command without the need for an email & password prompt or can I set it like env variables? I'm interested in this because I'd like to automate the backup process and have the backups uploaded to an S3 bucket using a script.

[jotamartos]

When I run the following command sudo su ghost -c "ghost backup" to perform a backup in Ghost, it prompts me to enter an email and password. Is there a way to execute this command without the need for an email & password prompt or can I set it like env variables?

that's a Ghost-related question. Please take a look at its forums and documentation to get more information about how to use the CLI.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.