Apache: [proxy_http:error] AH01102: error reading status line from remote server 127.0.0.1:3000 / AH00898: Error reading from remote server returned by /api
mod_proxy couldn't read a valid response from the backend, so Apache returned 502/503.
AH00898: Error reading from remote server returned by /apiAH01102: error reading status line from remote server 127.0.0.1:3000[proxy_http:error] AH01102: error reading status line from remote server502 Proxy Error Reason: Error reading from remote serverThe proxy server received an invalid response from an upstream server Meaning
The backend crashed, closed the connection, speaks a different protocol, or responded too slowly. Check the backend log, ProxyTimeout, and that ProxyPass points to the right scheme/port. Set SetEnv proxy-initial-not-pooled 1 or ProxyPass ... disablereuse=On for keepalive races.
Common causes
- Backend crashed/restarted
- HTTP vs HTTPS mismatch to the backend
- Timeout (
ProxyTimeout) too low - Keepalive connection reuse race
- Backend not running (AH00957 / AH01114 variants)
⚡ Quick fix
- Check the backend service and its log
- Match the protocol/port in
ProxyPass - Tune
ProxyTimeoutanddisablereuse=On
Detailed fix by platform
Linux
sudo tail -30 /var/log/apache2/error.log; curl -I http://127.0.0.1:3000/
How to diagnose
- Backend — Alive?
- Scheme — http vs https?
- Timeout — ProxyTimeout?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Nginx / Apache
- nginx: [emerg] unknown directive Nginx: nginx: [emerg] unknown directive "x" in /etc/nginx/sites-enabled/x:12 — configuration file test failed
- upstream timed out Nginx: upstream timed out (110: Connection timed out) while reading response header from upstream
- AH00072: make_sock: could not bind to address 0.0.0.0:80 Apache: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 / AH00015: Unable to open logs
Other ways to find it
Where this error sits
Origin: Edge & web server. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026