• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

squidGuard forcing incorrect redirect address

pfSense Packages
3
6
669
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C
    Crlaozwyn
    last edited by Nov 25, 2020, 5:54 PM

    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?

    1 Reply Last reply Reply Quote 0
    • B
      bla
      last edited by Nov 26, 2020, 10:26 PM

      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.

      1 Reply Last reply Reply Quote 0
      • V
        viktor_g Netgate
        last edited by Nov 27, 2020, 5:09 AM

        will be fixed on new squidGuard update (1-2 days),
        see https://redmine.pfsense.org/issues/9364#note-4

        B C 2 Replies Last reply Nov 27, 2020, 5:16 AM Reply Quote 0
        • B
          bla @viktor_g
          last edited by Nov 27, 2020, 5:16 AM

          @viktor_g Thanks for the update.👍

          1 Reply Last reply Reply Quote 0
          • C
            Crlaozwyn @viktor_g
            last edited by Nov 27, 2020, 5:48 AM

            @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-4

            Yes, much thanks! My google-fu failed me and I didn't find that post. Appreciate you bringing it to our attention.

            1 Reply Last reply Reply Quote 0
            • V
              viktor_g Netgate
              last edited by Nov 27, 2020, 4:40 PM

              squidGuard 1.16.18_11 is ready
              Please update

              1 Reply Last reply Reply Quote 0
              1 out of 6
              • First post
                1/6
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.