| 1 |
|
| 2 |
Some errors that can occur with certificates when using MITM |
| 3 |
|
| 4 |
|
| 5 |
Certificate supplied by server was not valid: |
| 6 |
This message is produced when openssl detects an error in the target server's certificate. |
| 7 |
The message after the ":" is an openssl message. Check the openssl documentation on how to bug |
| 8 |
fix the error. |
| 9 |
|
| 10 |
Common ones are:- |
| 11 |
|
| 12 |
Certificate supplied by server was not valid: self signed certificate in certificate chain |
| 13 |
|
| 14 |
Certificate supplied is self-signed. |
| 15 |
If you are happy to allow full access to this site then add it to exceptionsitelist. |
| 16 |
To allow access with content checking then add site to nocheckcertsitelist. |
| 17 |
|
| 18 |
|
| 19 |
Certificate supplied by server was not valid: unable to get local issuer certificate |
| 20 |
|
| 21 |
Indicates that an invalid certificate has been supplied by target server. |
| 22 |
|
| 23 |
If you get this error a lot (on most sites) then openssl is not set-up correctly. |
| 24 |
Check you have an up-to-date certificate bundle installed. |
| 25 |
|
| 26 |
If you get this on a site that works ok in browser going direct check that browser has not |
| 27 |
got a certificate exception for the site. If a direct browser accepts the sites certificate, then |
| 28 |
check your openssl cert bundle is up-to-date. Is it is, use openssl command line debuging options from |
| 29 |
the server e2guardian is installed on. |
| 30 |
|
| 31 |
Failed to negotiate ssl connection to client |
| 32 |
|
| 33 |
Possible causes: |
| 34 |
|
| 35 |
Your rootCA is not installed on the client system - get user to install it. |
| 36 |
|
| 37 |
App is using CONNECT but not using https protocol. If you want to allow access to app add |
| 38 |
site name to exceptionsitelist. |
| 39 |
|
| 40 |
App on client system does not respect client certificate store. If you want to allow access to app add |
| 41 |
site name to exceptionsitelist. |
| 42 |
|
| 43 |
Failure of network connection to client. |
| 44 |
|
| 45 |
No SSL certificate supplied by server |
| 46 |
|
| 47 |
Server is trying to negotiate SSL connection without supplying certificate, so is insecure. |
| 48 |
If you are happy to allow full access to this site then add it to exceptionsitelist. |
| 49 |
To allow access with content checking then add site to nocheckcertsitelist. |
| 50 |
|
| 51 |
Server's SSL certificate does not match domain name |
| 52 |
|
| 53 |
SSL certificate supplied by target server does not match domain name, so is insecure. |
| 54 |
If you are happy to take risk and allow full access to this site then add it to exceptionsitelist. |
| 55 |
To allow access with content checking then add site to nocheckcertsitelist. |
| 56 |
|
| 57 |
Failed to negotiate ssl connection to server |
| 58 |
|
| 59 |
Target server is listening on port 443 for a non-https protocol. |
| 60 |
If service is required add site to exceptionsitelist. |
| 61 |
|
| 62 |
Transitory network failure after initial connection. |
| 63 |
|
| 64 |
General - if issues persist turn logsslerrors = on in e2guardian.conf - This will log detailed openssl stack errors |
| 65 |
in syslog. Openssl documentation can then be consulted to help determine the cause of the error. |