Views: 10

The issue occurs because of the following command used to enable content cache:

/usr/iwss/AdminUI/cache_helper.sh EnableCache

The “cache_helper.sh” configures Squid to use port 3128, so the port reverts to it every time content cache is enabled.

To retain your custom port for Squid:

  1. Open ../usr/iwss/AdminUI/cache_helper.sh.
  2. Search for port 3128. You will find two entries.
  3. Change port 3128 to the desired port.
  4. Save the changes.
  5. Disable and then enable content cache.

The specified port will be the value of the “http_port” parameter in the ../etc/squid/squid.conf file, and this port will be retained when you enable content cache.

Keywords: squid port changes,http port goes to back to old,wrong port after content change turned on,turn off content cache,configure custom squid port number,set different port for squid,content caching feature