+- The Un-Official Proxomitron Forum (https://www.prxbx.com/forums)
+-- Forum: Forum Related (/forumdisplay.php?fid=37)
+--- Forum: ProxHTTPSProxy (/forumdisplay.php?fid=48)
+--- Thread: 417: SSL Certificate Failed (/showthread.php?tid=2280)
417: SSL Certificate Failed - szebenyib - Oct. 12, 2016 01:03 PM
I had a problem after making the connection to the backend after the rear proxy.
The error message was: 417: SSL Certificate Failed.
That message was about the backend's certificate, because that was only a self-signed certificate. The rear proxy's certificate was OK. The solution was to add the backend to the SSL No-Verify section of the config.ini:
[SSL No-Verify]
*backend.com
Just though I would add this here so that others can learn from this.
RE: 417: SSL Certificate Failed - qymjesmw - Mar. 16, 2017 07:13 AM
Hi szebenyib,
Thanks for posting about this. I'm experiencing the same issue.
Background:
Browser: Chromium
OS: Debian 8 Jessie.
Proxy: Privoxy
Script: ProxHTTPSProxyMII
For example, I have a router located at say 172.0.0.8 using a self-signed certificate for HTTPS and using port 444 for access through a web browser.
Trying to access this router using ProxHTTPSProxyMII fails with the typical:
Code:
417: SSL Certificate Failed
The following error occurred while trying to access https://172.0.0.8:444/Error message. Editing config.ini to allow 172.0.0.8 works fine in the following section:
Code:
[SSL Pass-Thru]
172.0.0.8However your suggestion of placing:
Code:
[SSL No-Verify]
*backend.cominto the config.ini does not work.
Am I missing something here? Are you referring to the localhost address when mentioning *backend.com?
Best,
qymjesmw