Messages

Did you find a solution to this?
I've just setup a fresh install and getting the same error.

I'm not sure if this is a bug, or just me doing something wrong. On several new opnsense systems I've recently setup the Web Proxy error pages don't use the opnSense template, it reverts to the default squid template and I simply can't get the opnsense template to be used.

So I downloaded a copy of the templates and modified them as per the documentation and uploaded my custom templates. The HTML changes have taken effect as in I can see the new HTML content, but there are two css styles embedded in the page. One is my css I modified and the other is the default squid css by the looks.

Is this a bug? or am I doing something wrong?

I'm in much the same situation. We are migrating from Sophos UTM as I'm sick of the price increases and poor customer support for said price increases.

There are a number of things that the UTM could do that opnsense doesn't do as well, but over all I'm very happy with Opnsense. However not having multiple profiles for the proxy is a causing some issues.

We usually have Servers, Clients and Mobile devices all on separate networks. The servers all have the required certificates for SSL inspection. The clients may or may not have the required certificates depending on the site, and the mobiles never have the required certificates. It would be nice to do full inspection for the servers, and logging only for the other networks for reporting.

However we have had to resort to full SSL inspection for the servers, and just not process SSL at all for clients. Not ideal but its the only solution I could get to work.