The below warning occurs when the browser does not trust the SSL certificate presented by the ‘Caching Proxy’. The reason this is the case is that we are using a ‘Self-Signed certificate’, which is our only option for an internal network appliance like this.

  • On Firefox the only option is to select ‘Advanced’ and add an ‘Exception’.

  • On Chrome installing the ca.pem into the computer’s ‘Certificate Store’ will solve this problem too.

What happens if the Server IP address changes?

The ‘SSL certificate’ we generate includes the Servers’ ‘IP Address’. We strongly suggest having a server with a fixed local network address. Connecting to the server using an ‘IP Address’ that does not match the one that the computer had when the certificate was issued also generates certificate warnings.

Did this answer your question?