I have been getting PROXY error while running some reports, It works for a day and it doesnt work for another day. The report simply runs for about 10 min and error out. Please advice
HTML response error code: 502, error HTML response time was: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST/jasperserver-pro/flow.html. Reason: Error reading from remote server
6 Answers:
It's not JasperReports problem. Try steps listed in the following page.
https://www.lifewire.com/502-bad-gateway-error-explained-2622939
I'm Getting Something like this..
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /jasperserver-pro/flow.html.
Reason: Error reading from remote server
Apache/2.2.16 (Fedora) Server at services-portal.ont-hs4.newbayasp.net Port 80
502 means Bad Gateway response. Check for jasperserver.log at the time when you get this error to see if there is anything there that indicates a fault on JasperServer side. Right now, it seems either your proxy is configured to drop requests that go beyond 10 minutes or there is a network connectivity problem.
The 502 Bad Gateway Error is an indication that something has gone wrong within the server of your application, as opposed to the client side request. At its heart, the cause is simple, two online servers are having trouble communicating. Often, simply refreshing or reloading the page (Ctrl-F5) will work, but sometimes the problem can persist for days. There are 5 main problems that cause 502 Bad Gateway responses. These include:
Server failure: The gateway receives a negative result if the target server has failed completely. This can occur due to a system crash .
Domain name not resolvable: The domain name is not resolving to the correct IP or it does not resolve to any IP. It is important to note that DNS changes could take same time until they are global fully propagated and active. This is dependant on the TTL, or time to live, defined per record.
Webserver overload: If a webserver reaches its limit, it can't answer any more requests , the gateway then delivers the status code 502 Bad Gateway.
Firewall blocks request: Firewalls can cause errors on both sides of the communication (server and client) with the forwarding of requests.
Browser error: Browser extensions can also sometimes cause errors with the display of a website and generate a 502 error .
502 Bad Gateway error is often a network error between servers on the internet, meaning the problem wouldn't be with your computer or internet connection. Empty or incomplete headers or response body typically caused by broken connections or server side crash can cause 502 errors if accessed via a gateway or proxy. Since it's just a generic error, it doesn't actually tell you the website's exact issue.
How to Solve 502 Errors
- Perform a hard-refresh in your browser. On Macs, this is done by pressing Cmd + Shift + R.
- Clear your browser cache and delete cookies. Your browser may be holding on to certain files that were saved once you visited the website with a 502 error.
- Change your DNS servers. If you’ve never changed them in the past you likely still have the default servers assigned to you by your ISP, try using open DNS servers such as Google's Public DNS.
- Finally, restart your computer/networking equipment. Some temporary issues with your computer and how it's connecting to your network could be causing 502 errors, especially if you're seeing the error on more than one website. In these cases, a restart would help.
