Squid Status Page

JonathanLee

Hello Fellow Netgate Community Members,

Can someone please confirm if the Squid package status page issue is corrected in the latest version of pfsense plus?

Thank you I would love to update but I am stuck because of this issue.

aGeekhere

@JonathanLee Does this also affect the community edition?

JonathanLee

@aGeekhere yes I have tested it on a VM of 2.8.1-BETA and64 20250729-1541 and it has the same issue without any custom config same problem. I want to upgrade so bad but I need that package to work.

aGeekhere

@JonathanLee Will this might be it for squid for pfsense then as it has been deprecated. Might have to move to using squid in a docker container.

will give it a bit to see if there is any response from the devs

JonathanLee

@aGeekhere I can’t upgrade pfSense because of the Squids issues. The ones that were talked about for reasoning of depreciation were also all resolved upstream a couple Squid stable versions ago. I just have to wait it out still on 23.05.01 keep testing it

aGeekhere

@JonathanLee Even though those issues were fixed as far as pfsense is concerned the package has been depreciated so they will not fix it. Unless they change their stances on the future of the package. Try and report the issue to pfsense bug tracker and see if they close the issue with "will not fix".

JonathanLee

@aGeekhere I have reported it and what is amazing as someone changed the version so it must be getting worked on.

aGeekhere

@JonathanLee any update? where can we view the progress?

JonathanLee

https://redmine.pfsense.org/issues/15410

Squid also released …

“The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-7.2 release!

This release is, we believe, stable enough for general production use.
We encourage all users of any previous version of Squid to upgrade to it.

It can be downloaded from GitHub, at
https://github.com/squid-cache/squid/releases/tag/SQUID_7_2

Since version 7.1, squid offers many security fixes and improvements;
details can be found in the release notes and in the changelog

Please remember to run "squid -k parse" when testing the upgrade to a new
version of Squid. It will audit your configuration files and report
any identifiable issues the new release will have in your installation
before you "press go".

If you encounter any issues with this release please file a bug report at
https://bugs.squid-cache.org/

--
Francesco Chemolli”

JonathanLee

Resolution:
Bug #15410 - cache_object:// scheme removed in Squid 6.
squidclient sends Proxy-Authorization header which Squid 6 rejects
for squid-internal-mgr endpoint.

Fix: Modified /usr/local/www/status_squid.php to use curl instead
of squidclient, sending Authorization header directly:

exec("/usr/local/bin/curl -s --max-time 10 -u 'admin:PASSWORD'
http://<interface_ip>:3128/squid-internal-mgr/info", $result);

Note: cachemgr_passwd is configured in squid.conf but under normal
circumstances manager access is controlled by manager_hosts ACL
(src 127.0.0.1 ::1 192.168.1.1). Password is only required because
curl/squidclient must authenticate — direct browser access from
allowed IPs would prompt via WWW-Authenticate challenge.

Upstream bug: pfSense bugtracker #15410

JonathanLee