I need to take 443 traffic to a public address and proxy it to port 81 on an internal server. In the reverse proxy settings. I have it set to 'Provide HTTPS for HTTP backend' SSL Port is set to 443 I have a certificate imported into the Reverse Proxy config. I have the Backend IP address set the 192.168.10.10:81 (IP of the internal server) When you go to the public url you get a TLS error Failed to establish a secure connection to 127.0.0.1 The system returned: (104) Connection reset by peer (TLS code: SQUID_ERR_SSL_HANDSHAKE) Handshake with SSL server failed: [No Error]. Gary, I was able to reproduce a similar error message of the reverse proxy to yours. The error arises when I reverse proxy (in SSL mode: Use SSL = Yes) a webserver but my backend Apache is not offering a listening socket on 443. So the connection from the reverse proxy to Apache on 443 is not possible. So it seems that there is an issue with the communication between the reverse proxy and the backend server. However, feel free to Contact Barracuda Networks Technical support. Our Agents can check your configuration to solve the issue. Regards, Matthias. Connection reset by peer. I can access this site fine behind our company firewall. [squid-users] Connection reset by peer > > Hi All. The system returned: (104) Connection reset by peer. The system returned: (104) Connection reset by peer. Something is definitely wrong with your squid box.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |