HOME Downloads Documentation Development Blacklists Contributions Contact

  Troubleshooting squidGuard

There may be times your squidGuard starts behaving in ways it it not supposed to. This may be due to a typo or some other tricky circumstance.
There are some tricks to find out what's going wrong.

  1. Permissions
    Make sure that the squid user can read the squidGuard configuration. This includes the path to the configuration file.
    You can check this by becoming the squid user (with su or login) and get to the relevant data.
    The blacklist and db files must belong to your squid user. If squid cannot access (or modify) them blocking will not work.

  2. SquidGuard dry-run
    To verify that your configuration is working run the following command (changed to reflect your configuration):

    Dry-run squidGuard
    echo "http://www.example.com - - GET" | squidGuard -c /tmp/test.cfg -d 

    If the redirector works properly you should see the redirection URL for the blocked site. For sites not being part of your blacklists the output should end with:

    2007-03-25 16:18:05 [30042] squidGuard ready for requests (1174832285.085)
    2007-03-25 16:18:05 [30042] squidGuard stopped (1174832285.089)

    Some remarks about the different entries of the echoed line:

    • The first entry is the URL you want to test.
    • The second entry is the client IP address. If you configured access control based on IP addresses make sure to test allowed and not allowed IP addresses to ensure proper working.
    • In the third entry (the first - ) you can specify a username. This is only of importance if you have access control based on user names. Make sure to check different names with different access to verify your configuration.

 Getting started
 Destination ACLs
 Source ACLs
 Redirect Rule
 Time Constraints
 Regular Expressions

Runtime Options
About blocking
Known Issues
Other Sources

  © Powered by Shalla Secure Services 2019