@nfld_republic haproxy-package uses version 1.8 and is not affected. Only version 2.0 and above.
haproxy-devel-package is using 2.2.14 and thus affected. Fixed version is 2.2.17.

@alexander90 no

EDIT:
This part "(./..(rar|mp3|exe|vpu))" doesn't work, rest of settings, i.e. radio|teamviewer works fine, sites are blocked.

we decided to go with:

xyz-web -- for all internal web interfaces

e outra coisa eu tenho duas interface lan 192.168.1.1 e wifi 172.168.0.1 na lá esta ok mais como devo fazer pra usar na wifi tbem pq são faixas de ip diferente

hello
today I ran into this problem, and in the last version available today (I think it was 1.16.18_20)
when checking the system log I could see that the error is due to the file being treated as a ".tar" file without compression.
When I downloaded the file on another host, unzipped it, and used the url with the .tar file, it managed to extract and process the list of categories correctly.

Here is the log that showed what the package was trying to do:

Sep 10 14:01:33 firewall php[10138]: squidGuard_blacklist_update.sh: The command '/usr/bin/tar zxvf /tmp/squidguard_blacklist.tar -C /tmp/squidGuard/unpack' returned exit code '1', the output was 'tar: Failed to set default locale tar: Error opening archive: Unrecognized archive format'

Sep 10 14:01:43 firewall php[10138]: squidGuard_blacklist_update.sh: The command '/bin/cp -f -p /tmp/squidGuard/arcdb/blacklist.files /usr/local/etc/squidGuard' returned exit code '1', the output was 'cp: /tmp/squidGuard/arcdb/blacklist.files: No such file or directory'

greetings

5491a6f4-4c82-4788-b155-a39e2d260f55-bild.png

So this is what I need to get a away from since there is obviosly a max number of rows pfSense accepts. I have reached that maximum.....

Right so if Squidguard is blocking that traffic it will try to display an error page but that is hosted in the firewall behind that self signed cert over https.

As a test only try setting the firewall webgui to http.

If that works you need to change the Squidguard settings to either not display an error page or redirect to an externally host page over http.

Steve

@rupesh issue resolved.Found this great post @ (https://github.com/PiBa-NL/pfsense-haproxy-package-doc/wiki/pfsense_2_3_haproxy_sni_plus_offloading_backends