OK Found the answer, I had to put this : $sge_prefix = (preg_match("/\?/", $cl['u']) ? "&" : "?"); $str[] = '<iframe> src="'.$cl['u'].$sge_prefix.'sgr=ACCESSDENIED" width="1" height="1" > </iframe>'; Right before the ?> at the end of /usr/local/www/sgerror.php, which for whatever reason didn't work earlier. This can be closed :)

@bkeadle também estou com esse problema. tenho ultima versão do squid, squidGuard e lightSquid. Estou tendo problemas em gerar os relatorios no lightSquid.

@marcelloc Instalei o squidanalyzer após ativar o seu repositórios não oficial. Após instalação ainda apresenta as seguintes recomendações: Modify your httpd.conf to allow access to HTML output like follow: Alias /squidreport /usr/local/www/squidreport <Directory /usr/local/www/squidreport> Options -Indexes FollowSymLinks MultiViews AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.1 </Directory> If necessary, give additional host access to SquidAnalyzer in httpd.conf. Restart and ensure that httpd is running. Browse to http://my.host.dom/squidreport/ to ensure that things are working properly. Setup a cronjob to run squid-analyzer daily: SquidAnalyzer log reporting daily 0 2 * * * /usr/local/bin/squid-analyzer > /dev/null 2>&1 or run it manually. For more information, see /usr/local/share/doc/squidanalyzer/README file. Cleaning up cache... done. Poderia ajduar?

@doktornotor mesmo instalando o repositório não oficial, e buscando o pacote, ele gera essa recomendações de conf mesmo: Após instalar o pacote temos a seguinte recomendação. Você consegue executar? Modify your httpd.conf to allow access to HTML output like follow: Alias /squidreport /usr/local/www/squidreport Options -Indexes FollowSymLinks MultiViews AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.1 If necessary, give additional host access to SquidAnalyzer in httpd.conf. Restart and ensure that httpd is running. Browse to http://my.host.dom/squidreport/ to ensure that things are working properly. Setup a cronjob to run squid-analyzer daily: SquidAnalyzer log reporting daily 0 2 * * * /usr/local/bin/squid-analyzer > /dev/null 2>&1 or run it manually. For more information, see /usr/local/share/doc/squidanalyzer/README file. Cleaning up cache… done.

@fireix estou com o mesmo erro. Porém nem tenho cach ativo no squid. Já reiniciei o pfesene e continua.

@gertjan Thank you, I had seen this thread and followed the OP's advice prior to the expiry of the LE certificate. So I thought I was prepared. But reading again and on, there was a problem reported, not exactly mine but similar enough. (Apparently, my problem was not the certificate itself (as expected by you) but the root or the intermediate certificate (the browser on my phone did not go into those details)). I followed the advice, deleted the CAs and renewed the certificate again. This recreated the CAs and solved my problem. Still strange that I encountered the problems only on my mobile but not on my PC...

6 year old post about 2.1.5??

Solved! Found the issue, apparently the health check settings in the backend configuration was the "culprit". The default setting is HTTPS check and changed it to a basic (socket) check. So it had nothing to do with my cert or HAProxy configuration itself (beside the health check setting).

@ageekhere Yeap, of course !

OK Quick update, this is done using "Remote cache" in the config (the entire tab is done with this). I now have a working proxy for http requests, and I'm not sure on how to apply the same thing (forward every request to upstream proxy) for https without having to setup a CA. Any ideas?

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