[WordPress] Wordpress keeps crashing due to lack of memory about vms HOT 1 CLOSED

Hi,

(1) with regards to the Apache issues, there is no instruction in the documentation how to resolve these.

Those are WordPress/plugins related issues so you should ask their developers to know more about them

[Tue Feb 08 03:54:08.466236 2022] [proxy_fcgi:error] [pid 1170:tid 140545791801088] [client 220.253.111.118:57673] AH01071: Got error 'PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/ woocommerce/packages/woocommerce-admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/woocommerce/packages/woocommerce- admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/ PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in / bitnami/wordpress/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149PHP message: PHP Warning: Illegal string offset 'slug' in /bitnami/wordpress/wp-content/plugins/ woocommerce/packages/woocommerce-admin/src/API/Reports/PerformanceIndicators/Controller.php on line 149', referer: https://www.questcoffee.com.au/wp-admin/

(2) with regards to the Connectivity issues, should ports 22, 80, and 443 be opened?

I have access to your instance so ports are opened

❯ curl -LIk 3.106.5.161
HTTP/1.1 301 Moved Permanently
Date: Tue, 08 Feb 2022 15:23:39 GMT
Server: Apache/2.4.52 (Unix) OpenSSL/1.1.1d
X-Powered-By: PHP/7.4.27
X-Redirect-By: WordPress
Location: https://3.106.5.161/
Access-Control-Allow-Origin: *
Content-Type: text/html; charset=UTF-8

HTTP/1.1 200 OK
Date: Tue, 08 Feb 2022 15:23:41 GMT
Server: Apache/2.4.52 (Unix) OpenSSL/1.1.1d
X-Powered-By: PHP/7.4.27
Link: <https://3.106.5.161/wp-json/>; rel="https://api.w.org/", <https://3.106.5.161/wp-json/wp/v2/pages/734>; rel="alternate"; type="application/json", <https://3.106.5.161/>; rel=shortlink
Content-Type: text/html; charset=UTF-8
(3) with regards to the available RAM memory, which is suggested as a likely cause of Wordpress crashing. My website has been working fine for the last 2 years, and this issue only started after the recent server migration to an updated Bitnami instance. It doesn’t make sense why suddenly RAM memory is insufficient.

You should monitor the performance of the server just in case you run out of memory at some time. These guides will help you

https://docs.bitnami.com/aws/faq/troubleshooting/troubleshoot-server-performance/ 7
https://docs.bitnami.com/aws/apps/wordpress/troubleshooting/deny-connections-bots-apache/

from vms.