PfSense 2.1.5 + Squid3 reverse proxy = very slow :(

  • Hi guys,

    I have an issue with my pfSense 2.1.5 installation, where I have a reverse proxy (Squid3) running, and everything is working fine, but the download speed is freaking slow. I have an up- and download of between 100 and 300 Mbit (hosted dedicated server), when I bypass the proxy to my web server (port forwarding to the owncloud host), I am getting around 8 to 18 Mbyte / s, but when using reverse proxy, it is capped to 250 kbyte / s! More over, the cap is done per connection, i.e. 2-3 simultaneous downloads are always capped to 250 kbyte / s each.

    I have no traffic shaping rules set. Does anyone have an idea?


  • Ok, problem solved. I've setup an Ubuntu machine with Squid3 as reverse proxy - no limitations, as expected. So either the squid3 package is compiled hard with limit, or there is another limitation factor (which I doubt). So pfSense is not an answer to all questions, after all (though it works great for me, but I have to drop reverse proxy functionality).


  • I'd guess your hard drive isn't spectacular on pfsense.

  • How so? It's all running on the same hypervisor, hence the same hard drive. I guess, you just wanted to say something smart?

  • I'd guess I'm the dummy thats not having problems. (-:

    But if you are sure that disk performance won't impact squid performance, you know more than me.

    Chances are good also that if the disk isn't the problem, your settings are.  It works for others, although I generally like to avoid squid unless I'm forced to use it.

    There are other possibilities as well, such as CPU allocated to the pfsense VM.

    Generally speaking, when you jump on a forum calling something broken that works for thousands of other people because you couldn't figure it out, it doesn't make you look all that great.

    Standing up a second VM just for squid is abit resource heavy.  I'd keep working on pfsense.

  • I am also having the same issue, fast disks, 2GB RAM. Squid3 data transfer is less than 1Mbit on a 50 Mbit connection using the reverse proxy feature.
    Did you resolve this?