GMS Outage Cause

1. The Traffic Flood (The "Outage" Cause)

These lines show one single IP (92.27.72.247) firing rapid-fire requests, which exhausted your server's available slots and caused everyone else to time out.

The Flood (24 requests in 8 seconds from one IP):

[Wed Feb 11 08:22:19.344591 2026] [ssl:debug] ... [client 47.251.93.227:52138] AH02034: Initial (No.1) HTTPS request... (... 22 more requests follow immediately ...) [Wed Feb 11 08:22:27.063855 2026] [ssl:debug] ... [client 47.251.93.227:52138] AH02034: Subsequent (No.24) HTTPS request...

The Consequence (Other users timing out because the server is full):

[Wed Feb 11 08:21:42.330073 2026] [ssl:info] [pid 19625] (70007)The timeout specified has expired: [client 82.132.245.172:60795] AH01991: SSL input filter read failed. [Wed Feb 11 08:22:12.065995 2026] [ssl:info] [pid 19622] (70007)The timeout specified has expired: [client 92.27.72.247:33098] AH01991: SSL input filter read failed. [Wed Feb 11 08:23:10.342812 2026] [ssl:info] [pid 19623] (70007)The timeout specified has expired: [client 82.132.229.69:39589] AH01991: SSL input filter read failed.

2. The PHP Configuration Error (Log Bloat)

These lines appear on almost every single request. While they don't "crash" the site, they slow down processing by forcing the server to write to the error log constantly.

[Wed Feb 11 08:19:24.354428 2026] [:error] [pid 19621] PHP Notice: Constant ENVIRONMENT already defined in /var/www/html/app.milverdene.com/index.php on line 76 [Wed Feb 11 08:19:24.354439 2026] [:error] [pid 19621] PHP Notice: Constant ENVIRONMENT already defined in /var/www/html/app.milverdene.com/index.php on line 78