Captive Portal authentication has been migrated to the user manager in 2.4.4. That option probably no longer makes sense.

@hexine
The issue is likely caused by a somewhat messed up configuration somewhere. Do you have a configuration backup from before the upgrade when haproxy was still working? I wonder what the <haproxy> part of that configuration looks like..
As currently it looks like the frontend with name A and description A and without address is kinda 'broken', you could perhaps delete it and configured it fresh.?

p.s. i can make the PHP 'not' throw an error on it with a few minor changes, but still it wouldn't 'properly' work..

diff --git a/net/pfSense-pkg-haproxy-devel/files/usr/local/www/haproxy/haproxy_listeners.php b/net/pfSense-pkg-haproxy-devel/files/usr/local/www/haproxy/haproxy_listeners.php index 859ba65697cb..275b318ce75d 100644 --- a/net/pfSense-pkg-haproxy-devel/files/usr/local/www/haproxy/haproxy_listeners.php +++ b/net/pfSense-pkg-haproxy-devel/files/usr/local/www/haproxy/haproxy_listeners.php @@ -256,6 +256,7 @@ function js_callback(req) { $a_frontend_grouped = array(); foreach($a_frontend as &$frontend2) { + getarraybyref($frontend2); $mainfrontend = get_primaryfrontend($frontend2); $mainname = $mainfrontend['name']; $ipport = get_frontend_ipport($frontend2, true);

Hum, you're on to something here! The gitlab server does not use SSL in the background, so I shouldn't have it there but I disabled SSL encryption and enabled SSL checks on the WAN_HTTPS backend and that seems to have done the trick!

Sweet bananas, huge thanks!

@kom said in /usr/local/www/sarg.php: The command 'export LC_ALL=C && /usr/local/bin/sarg ' returned exit code '1', the output was 'SARG: File "" not found':

I don't know. E2Guardian isn't a supported package either. You are on your own with those.

You never touch it, and it usually works but sometimes not? Strange.

I'm using Sarg and Lightsquid for now. Let's see if it happens with Lightsquid too.
Thank you for your time, Sir. 🤓

thanks !

Thank you for this very quick fix. 😄

Package 1.16.18_1 installed.
It's working like a charm !!! 👍 😎

Thanks again.

Correct, guess we'll have to wait for the FreeBSD 12 base

It was released version 1.16.18 that corrects this problem, it worked out right here for me pfsense 2.4.4, Thanks to all

You get that response when the object requested is not in the cache and must be fetched from its source.

Thank you. was using "---" in target so this is not going.

... and then the remove (de install).

did that with no luck :(

I fixed the problem with backup config, cut out the Squid-Reverse Proxy section and Restore the modified backup file. Then the Squid-Package installed without problem.

Also does the new package 0.4.44_5.

the problem was inside this section:
<squidreverse>
<config>
<reverse_interface>wan</reverse_interface>
<reverse_external_fqdn>server11.xxx.xx</reverse_external_fqdn>
<reverse_http></reverse_http>
<reverse_http_port></reverse_http_port>
<reverse_http_defsite></reverse_http_defsite>
<reverse_https></reverse_https>
<reverse_https_port></reverse_https_port>
<reverse_https_defsite></reverse_https_defsite>
<reverse_ssl_cert></reverse_ssl_cert>
<reverse_int_ca></reverse_int_ca>
<deny_info_tcp_reset>on</deny_info_tcp_reset>
<reverse_ignore_ssl_valid></reverse_ignore_ssl_valid>
<reverse_owa></reverse_owa>
<reverse_owa_ip>192.168.10.38</reverse_owa_ip>
<reverse_owa_activesync></reverse_owa_activesync>
<reverse_owa_rpchttp></reverse_owa_rpchttp>
<reverse_cache_peer>SE9TVDE7MTkyLjE2OC4xMC4xMDs4MDtIVFRQ</reverse_cache_peer>
<revrse_uri>VVJJMTtwdWJsaWM7d3d3Lnh4eC54eA=</revrse_uri>
<reverse_acl>SE9TVDE7VVJJMQ==</reverse_acl>
</config>
</squidreverse>

@eden said in [2.4.x] Squid/ClamAV: Fix for C-ICAP 0.5.x not starting:

Hello all

I am also having this issues with the ICAP service not starting. I have edited then config as requested above no joy. I then decided to reinstall the package but this did not make a difference. I have now uninstall the squid package completely and reinstalled it. Still the service will not start.

If that is the case then your problem is not the same problem as this thread. Start a new thread with details about your configuration, any error messages from logs, etc.