SSL Certificate issue and MySQL could not be started

Keywords: WordPress - AWS - Technical issue - Services (Apache, MariaDB, MySQL…)

bnsupport ID: 5ce88717-7a65-a257-50f2-11b50299ae02

bndiagnostic output:

? Apache: Found possible issues
? Resources: Found possible issues
? Connectivity: Found possible issues
https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-errors-apache/
https://docs.bitnami.com/bch/apps/moodle/troubleshooting/deny-connections-bots-apache/
https://docs.bitnami.com/installer/faq/linux-faq/administration/increase-memory-linux/
https://docs.bitnami.com/general/faq/administration/use-firewall/

bndiagnostic failure reason: I do not know how to perform the changes explained in the documentation

Description:

 [Tue Sep 14 05:56:46.083061 2021] [proxy_fcgi:error] [pid 14966:tid
140293235836672] [client **ip_address**:35208] AH01079: failed to make
connection to backend: httpd-UDS, referer: http://blog.techmantu.com/
 [Tue Sep 14 05:56:46.083600 2021] [proxy:error] [pid 14966:tid 140293235836672]
(111)Connection refused: AH02454: FCGI: attempt to connect to Unix domain socket
/opt/bitnami/php/var/run/wordpress.sock (wordpress-fpm) failed
 [Tue Sep 14 05:56:46.083614 2021] [proxy_fcgi:error] [pid 14966:tid
Press [Enter] to continue:
140293235836672] [client **ip_address**:35208] AH01079: failed to make
connection to backend: httpd-UDS, referer: http://blog.techmantu.com/
AH00526: Syntax error on line 46 of
/opt/bitnami/apache2/conf/bitnami/bitnami.conf: SSLCertificateFile: file
'/opt/bitnami/apache2/conf/server.crt' does not exist or is empty

Your disk is almost full: You could try to increase your instance’s storage.

Filesystem Size Used Avail Use% Mounted on /dev/xvda1 9.7G 9.6G 52M 100% /

Please check your cloud provider’s documentation for more information.

Your instance has little available RAM memory.

 total used free shared buff/cache available Mem: 990 343 81 24 565 411 Swap: 0
0 0

You could try to increase your instance’s memory.

Hello @selvan,

You will need to first increase your instance disk space as explained in the following guide:

https://docs.bitnami.com/aws/how-to/attach-ebs-volume/

After that, restart the instance from the AWS console and then your services from the console:

sudo /opt/bitnami/ctlscript.sh restart

If you need to increase your instance’s memory, you can check this guide:

https://docs.bitnami.com/aws/faq/administration/change-server-type/

Regards,
Francisco de Paz

AH00526: Syntax error on line 46 of

/opt/bitnami/apache2/conf/bitnami/bitnami.conf: SSLCertificateFile: file

‘/opt/bitnami/apache2/conf/server.crt’ does not exist or is empty

Hello @selvan,

My bad, I missed that error. I see that you are using two domains and are using two symlinks:

$ ls -la /opt/bitnami/apache2/conf
lrwxrwxrwx  1 root    root     57 Sep  8 07:31 server.crt -> /opt/bitnami/letsencrypt/certificates/2.domain.com.crt
lrwxrwxrwx  1 root    root     60 Sep  8 07:24 server.crt.old -> /opt/bitnami/letsencrypt/certificates/blog.domain.com.crt

The thing is, the certificate 2.domain.com.crt doesn’t exist at /opt/bitnami/letsencrypt/certificates/, that is why it is saying the file does not exist.

You shouldn’t configure this using two different certificates. You should instead use a single certificate for both domains. To reconfigure this, you will need to first fix the current issue and then generate a new certificate for both of your domains. To do that, remove you non-existent server.crt at /opt/bitnami/apache2/conf and rename server.crt.old:

sudo rm /opt/bitnami/apache2/conf/server.crt
sudo mv /opt/bitnami/apache2/conf/server.crt.old /opt/bitnami/apache2/conf/server.crt

After that run again our bncert-tool configuring both domains in the newly generated certificate.

Regards,
Francisco de Paz

Hi Franciso de Paz,
Thanks for your solution.I tried the command through putty gen software but it is not working. If you dont mind can we have video call and i can explain what went wrong ,what i need.

Regards,
Karthikeyan Selvan.

Hello @selvan,

Unfortunately, we do not offer that kind of support. We can continue the discussion here, as it could also help the community solve similar cases in the future. Could you please share the commands you tried and the error they produced?

Regards,
Francisco de Paz