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

Squid unable to load single website.

Scheduled Pinned Locked Moved Cache/Proxy
4 Posts 2 Posters 1.1k 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.
  • T
    TheNetStriker
    last edited by Feb 7, 2019, 2:39 PM

    For some weeks now my Squid proxy is unable to load the website https://community.openhab.org but all other websites seam to work. The website worked before and I didn't change anything in the settings. Now I'am getting a timeout from the proxy every time. If I enable the access log I can only find this line from the website:

    07.02.2019 15:19:24 10.242.2.2 TCP_TUNNEL/200 community.openhab.org:443 - 46.101.248.207

    I'm running pfSense 2.4.4-RELEASE-p2 (amd64) and squid version 0.4.44_7. Has maybe something changed in one of the latest pfSense or Squid updates?

    1 Reply Last reply Reply Quote 0
    • K
      KOM
      last edited by Feb 7, 2019, 3:18 PM

      It works fine for me with squid 0.4.44_7.

      T 1 Reply Last reply Feb 7, 2019, 4:53 PM Reply Quote 0
      • T
        TheNetStriker @KOM
        last edited by TheNetStriker Feb 7, 2019, 5:23 PM Feb 7, 2019, 4:53 PM

        @kom I've just tested this with the internet explorer and there the page loads after about 1 minute. I guess this takes to long for the Chrome browser and is recognized as a timeout.

        So it is not the problem that the website is not working at all, but it loads very slowly. But without the proxy the page loads in a few seconds. What could cause such a delay on the proxy?

        Edit: The hardware the firewall is running on cannot be the problem. I have a Dell server only for pfSense with an Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz and 4 GB ram. CPU load is only 1% most of the time and memory usage is at 17%, so it is totally overpowered for my needs.

        Edit2: I just found a solution to my problem here: https://serverfault.com/questions/644604/squid-https-tunnelling-using-connect-very-slow
        After I've enable to option to try DNS IPv4 first the website was very fast again. It seams as there is a 60 second timeout on IPv6 resolution in squid.

        1 Reply Last reply Reply Quote 0
        • K
          KOM
          last edited by Feb 7, 2019, 5:33 PM

          Glad you got it sorted out.

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