Bug 63229 - Internal error (specific information not available): [client 10.132.46.153:54838] AH01102: error reading status line from remote server xxxxxxxxxxx.:8000, referer: Node Application Url
Summary: Internal error (specific information not available): [client 10.132.46.153:54...
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.4.46
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-04 14:21 UTC by Prajjwal Khonde
Modified: 2021-02-11 23:56 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Prajjwal Khonde 2019-03-04 14:21:18 UTC 
Hi 
We are currently facing login issue for our nodejs based application.

Apache version : Apache/2.4.23 

We are getting below error In Apache side

[Mon Mar 04 04:39:12.799051 2019] [proxy_http:error] [pid 29059] (20014)Internal error (specific information not available): [client 10.132.46.153:54838] AH01102: error reading status line from remote server xxxxxxxxxxx.:8000, referer: Node Application Url


Also tried adding below property in conf file:
 SetEnv force-proxy-request-1.0 1
 SetEnv proxy-nokeepalive 1

But not worked for us

attached config files

ServerName xxxxxxxxxxx.com 
SetEnv force-proxy-request-1.0 1 
SetEnv proxy-nokeepalive 1 
ProxyPreserveHost On ProxyPass / Node Application Url 
ProxyPassReverse / Node Application Url 
ErrorLog logs/file_error.log 
CustomLog logs/file_access_log combined

Any help would be appriciated
Comment 1 Prajjwal Khonde 2019-03-04 14:24:27 UTC 
For some users it working fine . But for some it causing issue.
Comment 2 Prajjwal Khonde 2019-03-04 14:29:20 UTC 
On frontend we are getting 

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

Reason: Error reading from remote server

Apache/2.4.23 (Red Hat) Server at XXXXXXXXX Port 80
Comment 3 gunjitchhatwal 2021-02-11 23:56:36 UTC 
This issue is happening with 2.4.46 version as well. We have tried the commonly suggested workarounds as well but it hasn't helped. We do not see an entry corresponding to the failed request.