Re: [squid-users] Status page error

[Jonathan Lee]

Thank you for the reply and information  Sent from my iPhone On Apr 11, 2025, at 20:28, Amos Jeffries <squ...@treenet.co.nz> wrote: On 11/04/25 03:47, Jonathan Lee wrote: Hello fellow Squid users, Does anyone use pfSense squid package that knows a possible solution to this issue ? I have went as far as to remove all custom config and go to complete splice all and it still occurs with or without cache enabled and or squid guard enabled. It is something I just don’t know how to correct it. I worked on testing it in command line a while back but could not find a way to get the status page working again. Show Quoted Content On 11/04/25 03:47, Jonathan Lee wrote: Hello fellow Squid users, Does anyone use pfSense squid package that knows a possible solution to this issue ? I have went as far as to remove all custom config and go to complete splice all and it still occurs with or without cache enabled and or squid guard enabled. It is something I just don’t know how to correct it. I worked on testing it in command line a while back but could not find a way to get the status page working again. On 11/04/25 03:47, Jonathan Lee wrote: Hello fellow Squid users, Does anyone use pfSense squid package that knows a possible solution to this issue ? I have went as far as to remove all custom config and go to complete splice all and it still occurs with or without cache enabled and or squid guard enabled. It is something I just don’t know how to correct it. I worked on testing it in command line a while back but could not find a way to get the status page working again. Bug #15410: cache_object://URL Scheme is removed in Squid-6 - pfSense Packages - pfSense bugtracker <https://redmine.pfsense.org/issues/15410> As discussed in that bug report the "cache_object://" scheme has been replaced by "http://(visible_hostname):3128/squid-internal-mgr/" * The scheme can be "https://" so long as the proxy listening port is configured with the https_port directive. * visible_hostname should be replaced by the contents of the visible_hostname directive, or listening IP address. This is just one of the many reasons that directive **needs** to be a DNS resolvable domain name. * The port 3128 can be another forward-proxy or an 'accel' mode port if you wish. Cannot be an 'intercept' or 'tproxy' *_port, nor an https_port with SSL-Bump enabled. FTR; What we are familiar with as an "index page" is not provided by the Squid cache manager by default. I provide a basic UI at <https://github.com/yadij/cachemgr.js> that makes accessing the reports a bit easier for humans. HTH Amos _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users

_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users