squidGuard forcing incorrect redirect address
-
I'm finally getting around to configuring squidGuard for my home network. I have a valid certificate (let's call it pfsense.site.com).
squidGuard redirects everything to the IP of 192.168.1.1 (pfsense IP), which doesn't have a valid certificate (name doesn't match, since cert is for pfsense.site.com). This results in the error: "Failed to establish a secure connection to 192.168.1.1". While I'd prefer to fix the IP certificate issue, a bit of searching indicates I'd have to do self-signed certs for the IP and, since that requires client-side intervention, isn't a workable solution.
No matter what I put in the "Redirect Info" box, it always goes to that same IP. I tried editing the config file, but it reverts when I try to apply changes. Individual target categories do the same thing. Doesn't matter if I redirect to pfsense.site.com or google.com - everything redirects to that IP. Here's an example from the config file:
dest Test { domainlist Test/domains redirect https://192.168.1.1:443/sgerror.php }
Nowhere in any of my (visible) settings is that IP listed or selected. Any help?
-
I'm experiencing the exact same issue as you. This has only been happening since the latest SquidGuard update (1.16.18_10). I think it's a bug. Hopefully it will be fixed soon.
-
will be fixed on new squidGuard update (1-2 days),
see https://redmine.pfsense.org/issues/9364#note-4 -
@viktor_g Thanks for the update.
-
@viktor_g said in squidGuard forcing incorrect redirect address:
will be fixed on new squidGuard update (1-2 days),
see https://redmine.pfsense.org/issues/9364#note-4Yes, much thanks! My google-fu failed me and I didn't find that post. Appreciate you bringing it to our attention.
-
squidGuard 1.16.18_11 is ready
Please update