• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Error : The requested URL could not be retrived - pfsense - squid3

Scheduled Pinned Locked Moved pfSense Packages
6 Posts 2 Posters 4.2k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N
    notaduck
    last edited by Feb 1, 2015, 11:10 PM Feb 1, 2015, 11:00 PM

    Hello ;)
    i have some problems with squid3
    i did follow this guide 100 % https://doc.pfsense.org/index.php/Setup_Squid_as_a_Transparent_Proxy

    but i am getting this error almost on every website i am trying to access/visit

    ERROR
    The requested URL could not be retrieved
    
    The following error was encountered while trying to retrieve the URL: http://squidclamav.darold.net/tuning.html
    
        ICAP protocol error.
    
    The system returned: [No Error]
    
    This means that some aspect of the ICAP communication failed.
    
    Some possible problems are:
    
        The ICAP server is not reachable.
    
        An Illegal response was received from the ICAP server.
    
    Generated Sun, 01 Feb 2015 22:47:23 GMT by localhost (squid/3.4.10)
    
    

    i tried to look in my /var/squid/log folder to see if there was any report in the logs and the only thing i did find was this, but i am not sure what i should do to make it work ?

    i dont get why i am getting a warning about subnet 10.0.0.3 because it is my wifi subnet?

    015/02/01 12:09:58 kid1| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
    2015/02/01 12:09:58| pinger: Initialising ICMP pinger ...
    2015/02/01 12:09:58|  icmp_sock: (1) Operation not permitted
    2015/02/01 12:09:58| pinger: Unable to start ICMP pinger.
    2015/02/01 12:09:58|  icmp_sock: (1) Operation not permitted
    2015/02/01 12:09:58| pinger: Unable to start ICMPv6 pinger.
    2015/02/01 12:09:58| FATAL: pinger: Unable to open any ICMP sockets.
    2015/02/01 13:28:17 kid1| WARNING: (A) '10.0.0.3' is a subnetwork of (B) '10.0.0.0/16'
    2015/02/01 13:28:17 kid1| WARNING: because of this '10.0.0.3' is ignored to keep splay tree searching predictable
    2015/02/01 13:28:17 kid1| WARNING: You should probably remove '10.0.0.3' from the ACL named 'localnet'
    2015/02/01 13:28:17| pinger: Initialising ICMP pinger ...
    2015/02/01 13:28:17|  icmp_sock: (1) Operation not permitted
    2015/02/01 13:28:17| pinger: Unable to start ICMP pinger.
    2015/02/01 13:28:17|  icmp_sock: (1) Operation not permitted
    2015/02/01 13:28:17| pinger: Unable to start ICMPv6 pinger.
    
    1 Reply Last reply Reply Quote 0
    • N
      notaduck
      last edited by Feb 2, 2015, 4:22 PM

      i just found out it is only in transparent mode i am getting this error ?

      1 Reply Last reply Reply Quote 0
      • N
        notaduck
        last edited by Feb 4, 2015, 11:43 AM

        isn 't there no one at all with an possible solution?

        1 Reply Last reply Reply Quote 0
        • K
          KOM
          last edited by Feb 4, 2015, 2:20 PM

          Do you have the integrated AV stuff running?

          1 Reply Last reply Reply Quote 0
          • N
            notaduck
            last edited by Feb 4, 2015, 5:38 PM

            @KOM:

            Do you have the integrated AV stuff running?

            i just reinstalled pfsense to start with a clean install. i configured the transparent proxy and everything was working this time.
            Then i enabled the integrated antivirus and i got the same error as before. is there anyway to get the antivirus to work ?

            1 Reply Last reply Reply Quote 0
            • K
              KOM
              last edited by Feb 4, 2015, 5:55 PM

              is there anyway to get the antivirus to work?

              No idea, but then I don't use that stuff.  I played with the Clam package but it was slowing down our link too much, and we already subscribe to a large vendor AV solution on all clients and servers here so the Clam stuff was redundant and less effective.  I know the new 2.2 using HAVP, but I still won't use it.

              1 Reply Last reply Reply Quote 0
              6 out of 6
              • First post
                6/6
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received