ERR_EMPTY_RESPONSE means the server accepted the TCP connection but closed it without sending an HTTP response. Typical for PHP-FPM/Apache crashes, nginx timeouts toward the upstream, or OOM kills. Causes: backend died, worker_connections exhausted, DB query hung. Fix: check backend logs, nginx error_log, systemctl status, raise PHP memory_limit.
This error blocks HTTPS access. Below: causes, fixes, working config, FAQ.
tail -f /var/log/nginx/error.log — look for "upstream prematurely closed" or "recv() failed"tail -f /var/log/php8.x-fpm.log — look for "child exited on signal" or OOMphp_admin_value[memory_limit] = 512Msystemctl status php-fpm nginx — all running?curl -H "Host: example.com" https://IP/server {
listen 443 ssl http2;
server_name example.com;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256;
ssl_prefer_server_ciphers off;
ssl_stapling on;
ssl_stapling_verify on;
}SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freeRefused — TCP connect failed (no listener). Empty — connection established but reply is empty. The cause is deeper: the worker died after accept().
Large POST bodies exceed nginx <code>client_max_body_size</code> or PHP <code>post_max_size</code>. PHP-FPM rejects, nginx drops the connection → empty response.
Enable nginx <code>access_log</code> with <code>$upstream_response_time</code> and <code>$upstream_status</code>. An empty upstream_status with a timestamp is the moment.
Temporarily, yes. The problem returns. Find the root cause in the logs.