<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Attention: Any Squid for Windows support<o:p></o:p></p>
<p class="MsoNormal">Re: Squid upgrade failure support questions<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi there,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We were using Squid proxy for Windows v3.5.26 on a Windows Server 2016 Standard server, and we finally upgraded to v4.14. However, we noticed it wasn’t listening on the default Squid http port of 3128, even though the ‘Squid Cache Server’
Windows firewall inbound rule is there and enabled.<o:p></o:p></p>
<p class="MsoNormal"><img width="1026" height="74" style="width:10.6875in;height:.7708in" id="Picture_x0020_1" src="cid:image001.png@01D7C8D7.F5ABCD80"><o:p></o:p></p>
<p class="MsoNormal">When I try to open a web browser and go to the ‘http://localhost:3128’ URL on the local Squid server, it shows the following message “This page can’t be displayed. Make sure the web address
<a href="http://localhost:3128">http://localhost:3128</a> is correct.”. It’s as though the Squid server isn’t listening on that URL and port 3128 anymore. It was working before the upgrade to v4.14.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As a test to see if it was Squid v4.14 causing the problem, we installed the same fresh new copy of Squid v4.14 on another server (with no Squid installed, running on Windows Server 2019 Standard), it installs fine, it’s listening on the
TCP port 3128 and I can get to the ‘http://localhost:3128’ page fine as expected. So, something with the Squid upgrade from v3.5.26 to v4.14 on the non-working server caused the Squid to not work/listen on port 3128 anymore. The ‘C:\Squid\etc\squid\squid.conf’
on the non-working/upgraded Squid server looks fine and shows the following lines:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"># Squid normally listens to port 3128<o:p></o:p></p>
<p class="MsoNormal">http_port 3128<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The ‘Squid for Windows’ service is set to ‘Automatic’ startup type and shows the ‘Running’ status. So it can’t be that. I can telnet to port 3128 on the new working Squid v4.14 server. But I can’t telnet to the same port 3128 on the upgraded/non-working
Squid server. When I do, it doesn’t work and errors out like this:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">C:\>telnet Squid-01 3128<o:p></o:p></p>
<p class="MsoNormal">Connecting To Squid-01...Could not open connection to the host, on port 3128: Connect failed<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Lastly, as a last resort, we uninstalled the existing non-working Squid v4.14 installation, deleted the old ‘C:\Squid’ folder after, removed as many mentions of the old Squid installation from the Windows registry, then installed a fresh
new Squid v4.14 and it still didn’t work. It had the same issue.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Are there any known issues like what I’m describing concerning the upgrade from Squid v3.5.26 to v4.14? I’m hoping you can help me and point me to the right direction to resolve this. I couldn’t find anything from a search on Google and
I also tried unsuccessfully on your Squid-cache wiki page at ‘https://wiki.squid-cache.org’. This can be a problem in the near future, as we have other Squid servers to upgrade and we don’t want to face the same problem as this one. Please forward to the right
team, group, user(s) as needed. If you have any questions, please let me know. Thanks for any help in advance.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
</div>
<div><div>-----------------------------------------<div>Moody's monitors email communications through its networks for regulatory compliance purposes and to protect its customers, employees and business and where allowed to do so by applicable law. The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Every effort is made to keep our network free from viruses. You should, however, review this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message. <br></div><div>-----------------------------------------</div></div></div></body>
</html>