[squid-users] Problem with cachemgr.cgi after upgrading to Stable10

Hi,

I upgraded to squid2.5 stable10 on Solaris 9.
Now when I connect to the cachemgr.cgi (which I placed in my cgi-bin dir.
from the newly compiled branch) I do not get the option of choosing the
port number. As you can see in my config summary, we do not use the
default port.

Only the following fields are present in the cachemgr.cgi:
Cache Server:
Manager name:
Password:

and what I try I get the message:
Cache Manager Error
connect: (146) Connection refused

Any help would be nice!
TIA
Martijn

Config summary:
http_port 8080
cache_mem 512 MB
maximum_object_size_in_memory 16 KB
ipcache_size 8192
fqdncache_size 8192
cache_dir ufs /usr/local/squid/cache 3000 16 256
cache_access_log /usr/local/squid/logs/access.log
cache_log /usr/local/squid/logs/cache.log
cache_store_log none
pid_filename /usr/local/squid/logs/squid.pid
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563 444 2000
acl Safe_ports port 80 81 82 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 119 443 563 444 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
acl PURGE method PURGE
http_access allow manager
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow PURGE localhost
http_access deny PURGE
...
...
http_access deny all
http_reply_access allow all
icp_access allow all
...
cachemgr_passwd secret all
Received on Tue Jul 26 2005 - 05:32:55 MDT