error reading status line from remote server

Operating System & Version
centos-release-7-8.2003.0.el7.centos.x86_64
cPanel & WHM Version
n/a

JoshDerp8

Registered
Oct 26, 2020
2
0
1
United Kingdom
cPanel Access Level
Root Administrator
I'm getting this error randomly, just woke up to lots of DMs asking why my webhost was down, haven't touched anything.

Code:
[Tue Oct 27 05:38:34.323385 2020] [proxy:error] [pid 6426] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:2095 (127.0.0.1) failed
[Tue Oct 27 05:38:34.323467 2020] [proxy_http:error] [pid 6426] [client ip:52431] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Tue Oct 27 05:38:34.323611 2020] [proxy:error] [pid 6426] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:2095 (127.0.0.1) failed
[Tue Oct 27 05:38:34.323622 2020] [proxy_http:error] [pid 6426] [client ip:52431] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Tue Oct 27 05:51:39.866153 2020] [proxy_http:error] [pid 1497] (104)Connection reset by peer: [client ip:63618] AH01102: error reading status line from remote server 127.0.0.1:2082
[Tue Oct 27 05:51:39.866240 2020] [proxy:error] [pid 1497] [client ip:63618] AH00898: Error reading from remote server returned by /___proxy_subdomain_cpanel/
[Tue Oct 27 05:51:49.357681 2020] [proxy_http:error] [pid 1497] (104)Connection reset by peer: [client ip:63618] AH01102: error reading status line from remote server 127.0.0.1:2082
[Tue Oct 27 05:51:49.357714 2020] [proxy:error] [pid 1497] [client ip:63618] AH00898: Error reading from remote server returned by /___proxy_subdomain_cpanel/502.shtml
[Tue Oct 27 06:44:18.439050 2020] [mpm_prefork:notice] [pid 1489] AH00169: caught SIGTERM, shutting down

Also I can't get the cpanel/whm version since the version command returns another error and of course I can't get into the website.
 

cPanelAaronH

Well-Known Member
Staff member
Dec 31, 2014
70
19
133
Houston Texas
cPanel Access Level
Root Administrator
Hello,

If you are always getting odd cruft, it may be a DNS template or possible disk going bad. I would check /var/log/messages for any signs of disk errors.

For the Proxy error, that sounds like the service went offline. Can you check for MaxRequestWorkers in the /usr/local/apache/logs/error_log log.

Feel free to open a ticket as well if you're still seeing having problems with either of those issues.