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

    SquidGuard failed to start after upgrade to 2.2.3

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 3 Posters 1.5k Views
    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.
    • V
      velbon
      last edited by

      Dear All,
      After upgrade from 2.2.2 to 2.2.3 my SquidGuard failed and even though i tried manually to restart it still fails.
      I received this error under the logs:

      php-fpm[13251]: /rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -k reconfigure' returned exit code '1', the output was '2015/06/28 01:42:42| parseConfigFile: squid.conf:69 unrecognized: 'url_rewrite_bypass' squid: ERROR: No running copy'

      1 Reply Last reply Reply Quote 0
      • X
        xbipin
        last edited by

        i have the same issue, can u try this, in squidguard goto target categories and create one empty category, hit save and then apply

        1 Reply Last reply Reply Quote 0
        • I
          ismaelnoble
          last edited by

          parseConfigFile: squid.conf:69 unrecognized: 'url_rewrite_bypass' squid: ERROR: No running copy'

          ^^ theres the issue, for some reason it does not like the url rewrite rule. given that its the weekend i dont have access to my work lab atm so i cant dig into it too much. but u can try

          https://forum.pfsense.org/index.php?topic=88683.msg531957#msg531957

          to see if it helps resolve it…

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