SquidGuard 1.16.18_19 update is borked

DansNGFacc

I've run into the same issue with pfSense (ver. 2.5.2) proxy-filter (Squidguard 1.16.18_19).

The proxy server (Squid 0.4.45_4) seems to functioning normally in Transparent/SSL mode, but for some reason the filter function just stopped working since 2021-07-14 according to the log.

I've tried stopping/restarting the services, and the system, and uninstalling/reinstalling Squidguard, but the filter does not filter any content at all.

ref: https://redmine.pfsense.org/issues/12125

I was just wondering if you or someone else had found any resolution?

I am now considering restoring to an earlier configuration date, and re-configure changes from then to present.

C0RR0SIVE

@dansngfacc said in SquidGuard 1.16.18_19 update is borked:

onsidering restoring to an earlier con

I tried to restore to an earlier configuration, no go... Something is wrong somewhere in the actual Squid Guard files, read the previous posts, you're going to have to edit a few files it seems like. I am surprised there aren't several others with this issue.

DansNGFacc

@c0rr0sive
I've tried editing the "squidguard_configurator.inc" file as suggested in previous post, rebooted the system and filtering is still not functioning.
I will check again tomorrow, but getting frustrated with this problem.
Please reply if you have heard/found any other possible solutions.

Thanks for your replies/input.

mki

@dansngfacc
Did SquidGuard recreate the configuration file?
If not, you have to make some configurations changes and then reapply the settings.

Please check the following file: /usr/local/etc/squidGuard1/squidGuard.conf
The ACLS' should no longer contain squidstatus.

OK

	foo  {
		pass !in-addr bar none
		log block.log
	}
	#

NOK

	foo  {
		pass squidstatus !in-addr bar none
		log block.log
	}
	#

DansNGFacc

@mki

Thank you for the advice,

I've checked the squidGuard.conf file and it didn't contain "squidstatus !in-addr" or "bar none" in the acl section (see attached jpg image)
I tried adding the "!in-addr" portion to the config, but after stopping/restarting the SquidGuard service I found that it wasn't saved or reverted to default.

Note that I'm using the Diagnostics/Edit File graphic editor.

The system still isn't filtering content.
Does the server need to be rebooted to reconfig?

DansNGFacc

System Log shows "php-fpm 44155 /diag_reboot.php: The command '/usr/bin/killall 'squidGuard'' returned exit code '1', the output was 'No matching processes were found' " as last entry after re-installing SquidGuard 1.16.18_19 package (see attached jpg)

viktor_g

Fixed in 1.16.18_20

DansNGFacc

@viktor_g

Thanks for the update,

I had proceeded to backdate config and uninstalled Squid/Squidguard temporarily. I will be re-installing from scratch, Squid-Proxy first (save config) and Squidguard-Filter second, when the update is available.

I will update post if issues continue at that time.

DansNGFacc

Reinstalled Squid & Squidguard 1.16.18_20 today and same issue is occuring. Squid Proxy Server works fine (transparent/ssl), then after installing Squidguard and configuring (Blacklist/target catagories), it initially filters content, then stops filtering any content.
(See attached system log)

Any help appreciated.

viktor_g

@dansngfacc said in SquidGuard 1.16.18_19 update is borked:

Reinstalled Squid & Squidguard 1.16.18_20 today and same issue is occuring. Squid Proxy Server works fine (transparent/ssl), then after installing Squidguard and configuring (Blacklist/target catagories), it initially filters content, then stops filtering any content.
(See attached system log)

Any help appreciated.

looks like another issue
please attach /var/squid/logs/squidGuard.log

DansNGFacc

@viktor_g

Thank you for the promp reply,
Presently I'm just running Squid - Proxy Service.
Unfortuneately, I've removed Squidguard temporarily to avoid issues with Net Users.
I normally do diagnostics/net management on Fridays, so I will reinstall/try again and send log at that time, or sooner if possible.