Webserver protection fails with 'error reading status line from remote server' in reverseproxy log

Hi Gerald,

please post a screenshot of your business rule affecting the servers.

Thank you 

Ian

Hi,

thank you for posting. From here I will wait until one of the wiz kids provides a greater insight.

Please provide some guidance LuCar Toni

Thank you 

Ian

Hi Gerard ,,

Could you check by enabling Stickey session on pathSpecificrouting.

Sticky Session Cooky did not make any difference, I also removed the path specific routing to no effect.

When I google on the response: 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,    I find lots of references to Apache problems in combination with SSL on webservers.

The strange thing is that both the Synergy server and the Exchange server have this problem, and both worked when we still had the UTM9 in front.

Best regards, Gerard

The case is solved; the problem was that XG's reverse proxy failed when a number of older SSL protocols and ciphers were enabled in Windows 2008R2.

Solution was disabling all protocols but TLS 1.0, 1.1, 1.2 and all ciphers but Triple DES and AES (using a free toool by Nartec).

This behaviour should be improved by XG not tripping over availability of these protocols, but warning the administrator that these webservers could be vulnerable in the LAN

Best regards, Gerard 

The case is solved; the problem was that XG's reverse proxy failed when a number of older SSL protocols and ciphers were enabled in Windows 2008R2.

Solution was disabling all protocols but TLS 1.0, 1.1, 1.2 and all ciphers but Triple DES and AES (using a free toool by Nartec).

This behaviour should be improved by XG not tripping over availability of these protocols, but warning the administrator that these webservers could be vulnerable in the LAN

Best regards, Gerard