4YL WP Theme

AH01075 | AH01095 [proxy_fcgi:error]

AH01075 Error dispatching request to : (reading input brigade) The client closed the TCP connection before PHP–FPM finished reading the body (common on slow or aborted posts).

AH01095 prefetch request body failed to 0.0.0.0:0 (httpd-UDS) Same scenario but logged while using Unix-domain sockets (Bitnami default).

These are network interruptions, not PHP bugs. Occasional entries are normal. If they spike, check: CloudFront/ELB idle timeouts (set ≥ 60 s). Very large uploads - raise ProxyTimeout or FcgidIOTimeout.

PHP Warning/Fatal inside proxy_fcgi:error
require_once(/bitnami/wordpress/wp-settings.php): No such file or directory
One request on May 19 03:53 shows WordPress core missing during a read. Most of the time that means:

A deployment or plugin update was running and briefly moved/renamed the file, or The file was deleted.

SSH in and verify /opt/bitnami/wordpress/wp-settings.php exists.

If it’s gone, extract it from the same WordPress version or re-install core.

Add Bitnami’s recommended automatic backups (snapshot + mysqldump) before future updates.

ssl:warn AH01909 www.example.com:443:0 server certificate does NOT include an ID which matches the server name

That’s Bitnami’s self-signed placeholder cert firing during the nightly log-rotation restart at 04:23 UTC.

Once Let’s Encrypt is correctly installed and the vhost’s ServerName/SSLCertificateFile point to your real cert (/opt/bitnami/apache/conf/bitnami/certs/4yourlogos.com.crt), the warning disappears.