Re: [squid-users] Kerberos - Cannot decrypt ticket for HTTP

Hi David, Thanks for your advice but it doesn't help me. I use AD account which haven't set these parameters. Misha. 17.11.2022, 10:07, "David Touzeau" :Hiperhaps this onehttps://wiki.articatech.com/en/proxy-service/troubleshooting/gss-cannot-decrypt-ticket Le 16/11/2022 à 0

[squid-users] Kerberos - Cannot decrypt ticket for HTTP

Hi everybody, Could you help me to setup my new squid server? I have a problem with keytab authorization. 2022/11/16 11:35:39| ERROR: Negotiate Authentication validating user. Result: {result=BH, notes={message: gss_accept_sec_context() failed: Unspecified GSS failure.  Minor code may provide more

[squid-users] CacheManager::ParseUrl: action 'digestauthenticator' not found

Hi everybody! Sometimes i get in cache.log this message: "CacheManager::ParseUrl: action 'digestauthenticator' not found" Tell me what it means? About my systems: Squid Cache: Version 3.5.25 Service Name: squid configure options: '--prefix=/usr' '--with-logdir=/var/log/squid/' '--includedir=/us

Re: [squid-users] ERROR: Cannot connect to 127.0.0.1:3128

Hi!Could you write me if you had managed to emulate the problem that I have? Best regards, Misha.   14.10.2016, 18:51, "Михаил" :Hi.Ready. # squidclient -vv mgr:info | head -n 40stub time| WARNING: BCP 177 violation. IPv6 transport forced OFF by build parameters.verbosity level set to 2R

Re: [squid-users] ERROR: Cannot connect to 127.0.0.1:3128

Hi.Ready. # squidclient -vv mgr:info | head -n 40stub time| WARNING: BCP 177 violation. IPv6 transport forced OFF by build parameters.verbosity level set to 2Request:GET cache_object://localhost/info HTTP/1.0Host: localhostUser-Agent: squidclient/3.5.21Accept: */*Connection: close .Transport detect

Re: [squid-users] ERROR: Cannot connect to 127.0.0.1:3128

loss, time 0msrtt min/avg/max/mdev = 0.051/0.051/0.051/0.000 ms And I tried to execute squidclient without specifying localhost. But I got a mistake again:# squidclient mgr:infostub time| WARNING: BCP 177 violation. IPv6 transport forced OFF by build parameters.HTTP/1.1 403 ForbiddenServer: squidM

Re: [squid-users] ERROR: Cannot connect to 127.0.0.1:3128

Hi! Please don't pay attention on this line. :)stub time| WARNING: BCP 177 violation. IPv6 transport forced OFF by build parameters. Best regards, Misha. 11.10.2016, 11:55, "Михаил" :I check version of squid 3.5.21 with my configuration and I faced with a problem. Early I used in

[squid-users] ERROR: Cannot connect to 127.0.0.1:3128

I check version of squid 3.5.21 with my configuration and I faced with a problem. Early I used in version 3.5.12 this line for connect localhost, but now it doesn't work.# squid.conf...http_access allow localhost managerhttp_access deny manager... # squidclient -p 3128 -h localhost mgr:infoHTTP/1.1

Re: [squid-users] Negotiateauthenticator processes are busy

faults with physical i/o: 12Best regards,Misha.15.10.2015, 06:29, "Markus Moeller" :What happens if you adjust the system time to be in sync with the AD server ? Markus  "Михаил" <maklek...@ya.ru> wrote in message news:1462781444845...@web15m.yandex.ru...Hi All!Sometime I get

[squid-users] Negotiateauthenticator processes are busy

Hi All!Sometime I get a error message and squid stop:2015/10/14 14:31:51| WARNING: All 300/300 negotiateauthenticator processes are busy.2015/10/14 14:31:51| WARNING: 300 pending requests queued2015/10/14 14:31:51| WARNING: Consider increasing the number of negotiateauthenticator processes in your

[squid-users] external_acl_type SPACE IN LOGIN

Hello!I found trouble in "squid version 3.5.0.4 and 3.5.1". If user account have space in login (sAMAccountName), the check doesn't pass successful.=Config file for NTLM authentication:auth_param ntlm program /usr/bin/n