Messages

It seems you need to register manually. I received the same messages and I contact sales team sales@opnsense.com . They did register manually and they said their automated order checking system is a bit picky at times.

Is this a different issue than the next topic?
https://forum.opnsense.org/index.php?topic=36914.0

As far as I know, OPNsense 23.7.8 was initially released with squid 6.4 on November 9, and then the FreeBSD port was updated to 6.5 late on November 10. So the squid 6.5 that now appears to be included in OPNsense 23.7.8 is likely a later fix.

If @bcookatpcsd updated at 1am EST November 10th, I'm guessing that squid 6.4 was included in the package, not squid 6.5, at that time.

Additional information.

I'm not good at English, so I read the logs roughly earlier, but after carefully reading the logs shared by @rac-hh, it seems that the ACL AUTH is defined correctly, but the ACL definition of 127.0.0.1 does not exist.

After defining a new ACL with server ip address attribute and specifying 127.0.0.1 as the IP address value, I was able to start the c-icap service without any error, and I was able to activate the c-icap connection in squid without any problem.

Code Select Expand


#icap_access allow AUTH 127.0.0.1
acl localserver srvip 127.0.0.1   
icap_access allow AUTH localserver

I think it is probably a bug in c-icap 0.5.11 rather than a problem with opnsense. I don't know when c-icap was updated in my environment, but when opnsense was updated, c-icap might be updated at the same time. The latest version of c-icap, c-icap 0.5.11, was released on September 27, 2023, and c-icap-modules-0.5.6 was released on October 2, 2023.

I met the same problem after update.
I tried to comment out the line containing "icap_access" like below, the same as rac-hh mentioned, and it works on my system.

Code Select Expand

#icap_access allow AUTH 127.0.0.1

I think it could be a workaround until the fix becomes available.