Error Reading From Remote Server Proxy Error
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this error reading from remote server meaning site About Us Learn more about Stack Overflow the company Business Learn more
Proxy Server Received An Invalid Response
about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server
Apache Proxy Error Reading From Remote Server
Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer
Proxy Error Reading Status Line From Remote Server
The best answers are voted up and rise to the top Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 (Debian) mod_proxy and Jetty 6.1.18 up vote 46 down vote favorite 23 Apache is receiving requests at port :80 and proxying them to Jetty at port :8080 The proxy server received an invalid response from an upstream server The proxy server could proxy error reading from remote server returned by not handle the request GET /. My dilemma: Everything works fine normally (fast requests, few seconds or few tens of seconds long requests are processed ok). Problems occur when request processing takes long (few minutes?). If I issue request instead directly to Jetty at port :8080 the request is processed OK. So problem is likely to sit somewhere between Apache and Jetty where I am using mod_proxy. How to solve this? I have already tried some "tricks" related to KeepAlive settings, without luck. Here is my current configuration, any suggestions? #keepalive Off ## I have tried this, does not help #SetEnv force-proxy-request-1.0 1 ## I have tried this, does not help #SetEnv proxy-nokeepalive 1 ## I have tried this, does not help #SetEnv proxy-initial-not-pooled 1 ## I have tried this, does not help KeepAlive 20 ## I have tried this, does not help KeepAliveTimeout 600 ## I have tried this, does not help ProxyTimeout 600 ## I have tried this, does not help NameVirtualHost *:80
Proxy Error The proxy server received an invalid response the proxy server received an invalid response from an upstream server from an upstream server. The proxy server could not setenv proxy nokeepalive 1 handle the request GET /admin/search-indexes.action. Reason: Error reading from remote server Apache/2.2.15 (CentOS) 502 proxy error reading from remote server Server at confluence.com Port 80 Cause This error message triggered when an SSL connection is configured from the browser to Apache, and http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de Apache does a reverse proxy to your Tomcat server. Internet Explorersends the wrong host information in an SSL connection and confuses Apache VirtualHosts. In short, the server name presented is that of the reverse DNS resolution of the IP, not the one in the URL. https://confluence.atlassian.com/confkb/proxy-error-when-viewing-the-content-indexing-page-389777939.html Workaround There are three workarounds for this issue: Remove the reverse proxy Make a configuration where there's only one IP address per SSL virtual hosts/server name1 server name == 1 IP address == 1 certificate == 1 Apache Virtual Host Use a different browser References: Server Name Indication Was this helpful? Yes No Thanks for your feedback! Why was this unhelpful? It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © 2016 Atlassian Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting http://stackoverflow.com/questions/20406845/proxy-error-502-the-proxy-server-received-an-invalid-response-from-an-upstream ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Proxy Error 502 : The proxy server received an invalid response from an upstream server up vote 24 down vote favorite 6 We are building a mass mailing sending application in Java. Mail is being send by error reading third party SMTP. After sending 400-500 mails tomcat6 service get stopped. Below is the error. Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /lin/Campaignn.jsp. Reason: Error reading from remote server Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request. Apache Server at msizzler.com Port 80 But when we are sending from localhost I did not received any error. It from remote server send all the mails. Please help me to sort it out this problem. java email proxy tomcat6 share|improve this question asked Dec 5 '13 at 17:36 Ranjeet Ranjan 1332210 add a comment| 3 Answers 3 active oldest votes up vote 26 down vote The HTTP 502 "Bad Gateway" response is generated when Apache web server does not receive a valid HTTP response from the upstream server, which in this case is your Tomcat web application. Some reasons why this might happen: Tomcat may have crashed The web application did not respond in time and the request from Apache timed out The Tomcat threads are timing out A network device is blocking the request, perhaps as some sort of connection timeout or DoS attack prevention system If the problem is related to timeout settings, you may be able to resolve it by investigating the following: ProxyTimeout directive of Apache's mod_proxy Connector config of Apache Tomcat Your network device's manual share|improve this answer answered Jan 29 '14 at 2:18 rmeakins 899611 add a comment| up vote 16 down vote Add this into your httpd.conf file Timeout 2400 ProxyTimeout 2400 ProxyBadHeader Ignore share|improve this answer edited Sep 6 at 16:52 Ian Hunter 3,47473559 answered Feb 18 '14 at 9:23 Albert Maclang 16112 8 Try it why? What's your explanation of why this might work? –EJP Feb 18 '14 at 9:55 These directives work great under Centos 6.6 with Apache 2.2.15. Thanks! –James Wo