OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 19.7 Legacy Series »
  • ICAP protocol error. after reboot of opnsense
« previous next »
  • Print
Pages: [1]

Author Topic: ICAP protocol error. after reboot of opnsense  (Read 3335 times)

scream

  • Jr. Member
  • **
  • Posts: 61
  • Karma: 2
    • View Profile
ICAP protocol error. after reboot of opnsense
« on: August 06, 2019, 04:13:24 pm »
Hi together

I run web proxy (squid) with blacklist and ICAP is activated.
Then there is C-ICAP and ClamAV installed and configured.

Everything works fine but and also virus is filtered (if I try it with eicar).

After every reboot I can't open any webpage. There is always a error `ICAP protocol error.`

The error can be solved by just restart "squid" in the opnsense GUI. But it's anoying.

Any hints why this happens? Is this a known bug?

OPNsense 19.7.2-amd64
FreeBSD 11.2-RELEASE-p12-HBSD
OpenSSL 1.0.2s 28 May 2019
os-c-icap 1.7
os-clamav   1.7
squid 4.8_1


Logged

fabian

  • Hero Member
  • *****
  • Posts: 2769
  • Karma: 200
  • OPNsense Contributor (Language, VPN, Proxy, etc.)
    • View Profile
    • Personal Homepage
Re: ICAP protocol error. after reboot of opnsense
« Reply #1 on: August 06, 2019, 06:41:54 pm »
I think this is the squid bug where it marks the service as down when it gets a request and the ICAP service is not yet started. The fix would be simply changing the start order of the services. Sadly I have no idea how to do that in rc.
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 19.7 Legacy Series »
  • ICAP protocol error. after reboot of opnsense
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2