search

bitnami / vms

Bitnami VMs
https://bitnami.com
Other
203 stars 42 forks source link

wordpress on aws #1406

Closed wmgill closed 5 months ago

wmgill commented 5 months ago

Platform

AWS

bndiagnostic ID know more about bndiagnostic ID

4e239684-7200-3182-4b50-8aef24404b50

bndiagnostic output

[Apache]

Found recent error or warning messages in the Apache error log.

[Tue Feb 13 01:29:53.230301 2024] [proxy_fcgi:error] [pid 744:tid 
139985004922624] [client 2600:1700:6148:c110:4c28:8679:eccc:dbfd:56787] AH01079: 
failed to make connection to backend: httpd-UDS
 [Tue Feb 13 01:29:53.330149 2024] [proxy:error] [pid 743:tid 139985550251776] 
(2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain 
socket /opt/bitnami/php/var/run/www.sock (www-fpm:8000) failed
 [Tue Feb 13 01:29:53.330201 2024] [proxy_fcgi:error] [pid 743:tid 
139985550251776] [client 2600:1700:6148:c110:4c28:8679:eccc:dbfd:56788] AH01079: 
failed to make connection to backend: httpd-UDS, referer: 
https://drivedinediscover.com/

Press [Enter] to continue:

Please check the following guide to troubleshoot server issues:

https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro rs-apache/

The Apache configuration has errors:

AH00526: Syntax error on line 5 of 
/opt/bitnami/apache/conf/vhosts/wordpress-https-vhost.conf: SSLCertificateFile: 
file '/opt/bitnami/apache/conf/bitnami/certs/server.crt' does not exist or is 
empty

Please check the configuration.

bndiagnostic was not useful. Could you please tell us why?

I don't know what the next step should be...

Describe your issue as much as you can

I am unable to access the site via browser. Apache fails to start. I can access via SSH I had an earlier error that www was not secure, but the domain itslf was. I attempted to update the cert, but apparently royaly screwed it up. Hoping you can help so I can at least recover the work I have done to date. Thanks.

wmgill commented 5 months ago

I was able to get apache to run by following the manual install of certs as shown here. But now it points to the index.html and not the wordpress install

wmgill commented 5 months ago

after editing the /opt/bitnami/apache/conf/vhosts/wordpress-https-vhost.conf file and adding DocumentRoot /opt/bitnami/wordpress All seems to be good again...