Search squid archive

Re: Squid upgrade failure support questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Be sure to also check the actual squid.exe is running - not just the service wrapper, you might be facing the https://github.com/diladele/squid-windows/issues/101 bug (4.14 does not work on older processors)

Best regards,
Rafael

-----Original Message-----
From: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> On Behalf Of Amos Jeffries
Sent: Sunday, 24 October 2021 22:45
To: squid-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Squid upgrade failure support questions

On 25/10/21 6:33 am, Yuen, John wrote:
> 
> http_port 3128
> 
> 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:
> 
> C:\>telnet Squid-01 3128
> 
> Connecting To Squid-01...Could not open connection to the host, on 
> port
> 3128: Connect failed
> 

At no point in your post do I see any mention of what the IP addresses are. Can you please indicate what "localhost", "Squid-01" resolve to on both the machine used as client and the Squid machine. And what IP(s) those firewall rules by Local subnet "Any" and Remote address "local subnet".


Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux