: Ambikapathy, Baskaran
Objet : RE: [squid-users] Squid Proxy timing out 500/503 errors
⚠ FR : Ce message provient de l'extérieur de l'organisation. N'ouvrez pas de
liens ou de pièces jointes à moins que vous ne sachiez que le contenu est
fiable. ⚠
Hi,
I used squidclient mgr:info to get
(CSS) ; squid-users@lists.squid-cache.org
Subject: RE: [squid-users] Squid Proxy timing out 500/503 errors
Hi Anitha,
Please check with "cat /proc/(pid)/limits" the Max open files limit for your
squid process.
You can also use "squidclient mgr:info" to display File descri
a part de M,
Anitha (CSS)
Envoyé : jeudi 7 mars 2024 18:20
À : Amos Jeffries ; squid-users@lists.squid-cache.org
Cc : Gopalsamy, Seetharam ; Ambikapathy, Baskaran
; TS, Savitha
Objet : Re: [squid-users] Squid Proxy timing out 500/503 errors
⚠ FR : Ce message provient de l'extérieur de l'organisat
memory_replacement_policy lru
minimum_object_size 0 KB
=
Regards,
Anitha.
-Original Message-
From: squid-users On Behalf Of Amos
Jeffries
Sent: Wednesday, March 6, 2024 1:07 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid Proxy timing out
effries
Sent: Wednesday, March 6, 2024 1:07 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid Proxy timing out 500/503 errors
On 6/03/24 07:23, M, Anitha (CSS) wrote:
> Hi team,
>
> We are using squid service deployed as a KVM VM on SLES 15 Sp5 os image.
&
On 6/03/24 07:23, M, Anitha (CSS) wrote:
Hi team,
We are using squid service deployed as a KVM VM on SLES 15 Sp5 os image.
We are using squid. Rpm: *squid-5.7-150400.3.20.1.x86_64*
**
We are seeing too many 503 errors with this version of squid.
This is the squid configuration file. Pls
Hi team,
We are using squid service deployed as a KVM VM on SLES 15 Sp5 os image.
We are using squid. Rpm: squid-5.7-150400.3.20.1.x86_64
We are seeing too many 503 errors with this version of squid.
This is the squid configuration file. Pls review it and let us know if issues.
We are performing
An: squid-users@lists.squid-cache.org
Betreff: Re: [squid-users] Squid Proxy - Block Access Why ?
On 7/21/23 04:46, Morad, Marc wrote:
> I am sending a request from Server A (IP: 192.10.16.20) via the squid
> proxy to Server B (IP: 192.10.16.21) in the same internal Subnet
> (192.1
On 7/21/23 04:46, Morad, Marc wrote:
I am sending a request from Server A (IP: 192.10.16.20) via the squid
proxy to Server B (IP: 192.10.16.21) in the same internal Subnet
(192.10.16.0/22). This request is getting blocked, which is a
behaviour we want to have. Why is it like that ? I read
Hello squid experts,
I have a question and I'm not quite sure if this is normal default behaviour or
part of my squid configuration.
The scenario is like this:
I am sending a request from Server A (IP: 192.10.16.20) via the squid proxy to
Server B (IP: 192.10.16.21) in the same internal
Hi Alessio,
Let us know if the suggested changes resolved the issue.
As for removing messages from the archive, I really hope this will
never be done as these archives are there to assist other users facing
similar issues. If you want to keep your request private and out of
archives, I
On 4/7/23 07:00, Alessio Ballarini (External) wrote:
- The TCP connections work inconsistently: sometimes they work (200) and
sometimes they do not (503).
Specifically in the access.log of the Squid we registered these 503 erros:
1680672739.134 59768 172.29.7.148 NONE/503 0 CONNECT
Hi Joost,
thank you so much for your help.
I am going to try to edit these configuration.
I would like to ask you to delete the thread we created from the archive :
[image: image.png]
Is it possible ?
Thanks
Alessio
Il giorno ven 7 apr 2023 alle ore 15:45 Joost Roeleveld
ha scritto:
> Hi
Hi Alessio,
The config file provided is incomplete. I don't see any definition of
"localnet"
Also, how are the connections through the proxy configured? Is this
done by configuring the client (SAP in this case) or is the firewall
forcing the connection through the proxy and the client is
Hi Antony,
thank you so much for the fats response.
The Operating System is:
SUSE Linux Enterprise Server 15 SP3 (x86_64)
The Squid Version is:
Squid Cache: Version 4.17
If you need more information, please let me know.
Kind regards
Alessio
Il giorno ven 7 apr 2023 alle ore 13:08 Antony
On Friday 07 April 2023 at 13:00:09, Alessio Ballarini (External) wrote:
> Hi Squid Support,
> we are facing a problem with Squid proxy
Which version of Squid, and running on which version of which operating
system?
Antony.
--
Normal people think "If it ain't broke, don't fix it".
Engineers
Hi Squid Support,
we are facing a problem with Squid proxy, configurated on our server named
"amiproxy".
I explain the role of this proxy in the infrastructure as follow:
- There are two SAP application server that need to use a Proxy to reach a
remote server out of our local network.
- The
On 9/20/22 00:53, Mark Schenk wrote:
We have a use case in which we need to do mutual TLS with an upstream
server. Our internal services are using their own certificates, and we
would like to use the SQUID proxy as a kind of gateway to which we send
requests for the upstream server. The squid
Hi squid community,
We have a use case in which we need to do mutual TLS with an upstream
server. Our internal services are using their own certificates, and we
would like to use the SQUID proxy as a kind of gateway to which we send
requests for the upstream server. The squid proxy will verify
roitoru
>
> NgTech, Tech Support
>
> Mobile: +972-5-28704261
>
> Email: ngtech1...@gmail.com
>
>
>
> *From:* robert k Wild
> *Sent:* Tuesday, February 22, 2022 10:38
> *To:* Eliezer Croitoru
> *Cc:* Squid Users
> *Subject:* Re: [squid-users] squid proxy re
liezer Croitoru
Cc: Squid Users
Subject: Re: [squid-users] squid proxy really slow for web requests
Hi Eliezer,
Thanks for the reply, in the end I had to restart our firewall, as our squid
server is on the dmz and squid users/clients accessing the squid server are on
the lan, so they have
com
>
>
>
> *From:* squid-users *On
> Behalf Of *robert k Wild
> *Sent:* Monday, February 21, 2022 18:42
> *To:* Squid Users
> *Subject:* [squid-users] squid proxy really slow for web requests
>
>
>
> hi all,
>
>
>
> today my squid responding
Croitoru
NgTech, Tech Support
Mobile: +972-5-28704261
Email: <mailto:ngtech1...@gmail.com> ngtech1...@gmail.com
From: squid-users On Behalf Of
robert k Wild
Sent: Monday, February 21, 2022 18:42
To: Squid Users
Subject: [squid-users] squid proxy really slow for web requests
hi all,
today my squid responding to web requests from different clients is really
slow
for example when i go on firefox/chrome and open multiple tabs to different
websites, it normally shows the "error url page" as ive denied all websites
apart from some
and some of the websites takes way to
On 16/10/21 12:33 am, Ryan Absolom wrote:
Hi All
Wondering if anyone can help - we've recently added a new subnet to
squid.conf (exactly the same layout / variables used as previous
subnets) however this doesn't get recognised.
What do you mean by "added" ?
With a default squid.conf it
Hi All
Wondering if anyone can help - we've recently added a new subnet to
squid.conf (exactly the same layout / variables used as previous subnets)
however this doesn't get recognised.
What makes this more confusing is we have to disable Selinux in order to be
able to pick up a connection to
Looking for a already made squid proxy/dashboard
Thank you
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
On 12/3/20 12:07 PM, Ob Rzwo wrote:
> I am reaching the performance limits of the Squid Proxy. I have a
> certain base load on one instance with 100 to 500 connections at the
> same time. First it gets slower then 503s are thrown.
>
> Now the question:
>
> Are there any squid.conf settings that
Hello,
I am reaching the performance limits of the Squid Proxy. I have a certain
base load on one instance with 100 to 500 connections at the same time.
First it gets slower then 503s are thrown.
Now the question:
Are there any squid.conf settings that could ease the situation? (Except
for
On 6/05/20 10:20 pm, Arjun K wrote:
> Hi Amos
>
> Could you please share a sample configuration file containing allow and
> deny sites defined in a text file so that I can put the same format with
> my acls and validate in my environment.
>
I did in my earlier post. If you want more search the
On 6/05/20 4:47 am, Arjun K wrote:
> Hi Amos
>
> Thanks for your response and suggestions and I will incorporate your
> inputs in the configuration.
> Please find the below contents of denylist as I am unable to attach as a
> document due to restrictions.
>
> .hotmail.com
The above is dstdomain
Hi Amos
Thanks for your response and suggestions and I will incorporate your inputs in
the configuration.Please find the below contents of denylist as I am unable to
attach as a document due to restrictions.
Hi All
Can any one help on the below issue.
I tried changing the order of deny and allow acl but it did not yield any
result.
RegardsArjun K
On Sunday, 3 May, 2020, 05:21:02 pm IST, Arjun K
wrote:
Hi All
The below is the configuration defined in the proxy server.The issue is that
On 6/05/20 12:58 am, Arjun K wrote:
> Hi All
>
> Can any one help on the below issue.
> I tried changing the order of deny and allow acl but it did not yield
> any result.
>
What is the contents of the denylist.txt file?
This usually happens when things in there are not the right dstdomain
Hi All
The below is the configuration defined in the proxy server.The issue is that
the proxy is not blocking the websites mentioned in a file named denylist.txt.
Kindly let me know what needs to be changed to block the websites.
IP Ranges allowed to use proxyacl localnet src 10.196.0.0/16
On 16/04/20 1:23 pm, Michael Leikind wrote:
> Greetings to the Squid community!
>
> I would like to get the recommendation on how to configure Squid (latest
> version) with client SSL termination.
>
> The requirement is to provide proxy access to the internet for the
> client who has no ability
Greetings to the Squid community!
I would like to get the recommendation on how to configure Squid (latest
version) with client SSL termination.
The requirement is to provide proxy access to the internet for the client
who has no ability to install a custom CA certificate.
Following the
On 3/18/20 1:22 PM, REED, JOHN wrote:
> I wanted to reach out and see if any work was being done on squid
> supporting routing based on this custom TLV field. I have done
> extensive searching online and I do see where logging this TLV is
> supported in version 5, but I haven't found anything
I am using Proxy Protocol V2 and I'm able to use the ACLs in the squid proxy to
route my traffic based on a source IP and destination IP/URL.
I have a use case where I may not have source IP uniqueness, however I will
have a unique identifier within the custom TLV field within the proxy
On 14.02.20 17:40, Patrícia Sousa wrote:
>It works now. There was a wrong iptables rule to redirect incoming traffic
>to the proxy.
Matus UHLAR - fantomas escreveu no dia sexta,
14/02/2020 à(s) 18:02:
incoming traffic? Do people from the world connect to your proxy?
On 16.02.20 14:27,
I mean, for example, all the traffic that comes to the port 80. Obviously,
ssh, for example, I can't.
Matus UHLAR - fantomas escreveu no dia sexta,
14/02/2020 à(s) 18:02:
> On 14.02.20 17:40, Patrícia Sousa wrote:
> >It works now. There was a wrong iptables rule to redirect incoming traffic
>
On 14.02.20 17:40, Patrícia Sousa wrote:
It works now. There was a wrong iptables rule to redirect incoming traffic
to the proxy.
incoming traffic? Do people from the world connect to your proxy?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to
Update:
It works now. There was a wrong iptables rule to redirect incoming traffic
to the proxy.
Amos Jeffries escreveu no dia sexta, 14/02/2020 à(s)
10:35:
> On 14/02/20 11:05 pm, Patrícia Sousa wrote:
> > I only configured the machine that has the squid proxy to use it.
>
> How did you
On 14/02/20 11:05 pm, Patrícia Sousa wrote:
> I only configured the machine that has the squid proxy to use it.
How did you configure an entire machine to use an HTTP-only proxy?
I think you mean something else. Details matter, so what *exactly* did
you configure?
And no squid.conf does not
I only configured the machine that has the squid proxy to use it. If I made
a wget from this machine to the another, it denies the request, as desired.
Only the reverse is not taken.
So, it's not possible to configure the http "incoming" connections to my
machine to go through the proxy?
Matus
On 13.02.20 12:29, Felipe Arturo Polanco wrote:
You only have one port open for Squid
http_port 3128
You need two ports, one for HTTP and another for HTTPS.
Also, if you are going to block HTTPS based on the domain name, you need to
do sslBump to get the SNI of the destination website and then
On 13.02.20 16:18, Patrícia Sousa wrote:
Enabling debug_options I can see that the wget from the machine computer to
the Squid machine does not goes through the proxy. Any idea why?
Because you apparently haven't configured anything to use the proxy.
Squid is a proxy, not a firewall, and it
You only have one port open for Squid
http_port 3128
You need two ports, one for HTTP and another for HTTPS.
Also, if you are going to block HTTPS based on the domain name, you need to
do sslBump to get the SNI of the destination website and then terminate the
SSL connection.
On Thu, Feb 13, 2020
I think so.
Here is the conf file: https://pastebin.com/DKMbwNV6
Felipe Arturo Polanco escreveu no dia quinta,
13/02/2020 à(s) 16:22:
> Did you configure Squid to accept both HTTP and HTTPS ports?
>
> Please share your squid.conf file.
>
> Thanks,
>
> On Thu, Feb 13, 2020 at 12:18 PM Patrícia
Did you configure Squid to accept both HTTP and HTTPS ports?
Please share your squid.conf file.
Thanks,
On Thu, Feb 13, 2020 at 12:18 PM Patrícia Sousa wrote:
> Hi,
>
> Thanks for the tip,
>
> Enabling debug_options I can see that the wget from the machine computer
> to the Squid machine does
Hi,
Thanks for the tip,
Enabling debug_options I can see that the wget from the machine computer to
the Squid machine does not goes through the proxy. Any idea why?
Felipe Arturo Polanco escreveu no dia quinta,
13/02/2020 à(s) 15:32:
> Hi,
>
> For this, you need to use IPtables to block at
On 2020-02-13 9:10 am, Patrícia Sousa wrote:
I'm using the squid proxy and I'm trying to block some connections (incoming and outcoming traffic) from a certain ip address. However, for example, if I deny all the connections (http_access deny all) it only blocks the connections that I made to
Hi,
For this, you need to use IPtables to block at the network level.
SSH uses port 22/tcp but wget uses HTTP, it should have been blocked by
squid.
Enabled debug_options in squid to see why it was allowed.
On Thu, Feb 13, 2020 at 11:10 AM Patrícia Sousa wrote:
> I'm using the squid proxy
I'm using the squid proxy and I'm trying to block some connections
(incoming and outcoming traffic) from a certain ip address. However, for
example, if I deny all the connections (http_access deny all) it only
blocks the connections that I made to websites for example, but if I use
another PC and
Right. that works now.
thanks.
- George
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
On 12/12/19 11:38 am, GeorgeShen wrote:
>
> did a 'openssl dhparam -out dhparams.pem 4096' to generate the dhparams.pem
> file, and added those into the squid.conf:
>
> http_port 3129 ssl-bump cert=/usr/local/squid/etc/ssl_cert/myCA.pem
> generate-host-certificates=on
did a 'openssl dhparam -out dhparams.pem 4096' to generate the dhparams.pem
file, and added those into the squid.conf:
http_port 3129 ssl-bump cert=/usr/local/squid/etc/ssl_cert/myCA.pem
generate-host-certificates=on dynamic_cert_mem_cache_size=4MB
*options=SINGLE_DH_USE:SINGLE_ECDH_USE
On 11/12/19 4:00 pm, GeorgeShen wrote:
> I'm running the squid latest from download site. 4.9
> Ok, i suspect that was related to my ^C running the process in foreground,
> but I also see before that there are warning messages in the log:
> 2019/12/09 19:23:12.116 kid1| WARNING:
>
I'm running the squid latest from download site. 4.9
Ok, i suspect that was related to my ^C running the process in foreground,
but I also see before that there are warning messages in the log:
2019/12/09 19:23:12.116 kid1| WARNING:
/usr/local/squid/libexec/security_file_certgen -s
On 12/9/19 12:56 PM, GeorgeShen wrote:
> and at the end, it is also saying security_file_certgen crashes rapidly!!!
I would ignore anything that happens _after_ you press ^C (i.e. send
Squid a shutdown signal). While a shutdown should not "crash" any
helpers, that is not the problem you are
On 10/12/19 6:46 pm, GeorgeShen wrote:
>
> I'm wondering if this issue reported last year is fixed:
> http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-4-4-security-file-certgen-helpers-crashing-td4687098.html
>
That question implies that you are not using the latest Squid release,
or
I'm wondering if this issue reported last year is fixed:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-4-4-security-file-certgen-helpers-crashing-td4687098.html
or is there a work around.
thanks.
- George
--
Sent from:
Hi Alex,
this time I tried, a little different, this is the log from got the server
certs to colose the
SSL with error, and at the end, it is also saying security_file_certgen
crashes rapidly!!!
below the output of log
thanks.
- George
On 12/8/19 1:53 AM, George Sheng wrote:
> From the debug I can also see the proxy connects towards the remote
> server, and proxy has negotiated fine with the server. the proxy
> receives 3 certificates from the server,
> and verification was fine to the server. But when the proxy trying to
>
On 9/12/19 10:41 am, GeorgeShen wrote:
> Hi Amos,
>
> i downloaded the 4.9 latest, and compiled with "./configure
> --with-default-user=proxy --with-openssl --enable-ssl-crtd", not redo the
> openssl and proxy certificate part, start squid with 4.9, still seeing
> failure. Have not debugged in
the version 4.9 has the same behavior, can not finish negotiate with the
client.
I have setup two different client machines, one is macOS, the other alpine
linux.
I finally got the macOS wget https to work through the squid 4.9 proxy with
ssl-bump.
So the squid config is ok.
The alpine linux,
Hi Amos,
i downloaded the 4.9 latest, and compiled with "./configure
--with-default-user=proxy --with-openssl --enable-ssl-crtd", not redo the
openssl and proxy certificate part, start squid with 4.9, still seeing
failure. Have not debugged in detail.
Quick question, when compile for the bump
Hi Amos,
thanks for the comments. I'll first try the later version as you pointed out
4.9 and see if I get the issues. Will report back.
thanks.
- George
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
On 8/12/19 7:53 pm, George Sheng wrote:
>
> Hi,
>
> I’m new to this group. I just setup a squid ver 4.5 on my ubuntu
When using SSL-Bump one does need to use the latest release. Which is
4.9 now.
Since this is a custom build (4.5 has never been a release in Ubuntu)
you may find Squid-5 has
Hi,
I’m new to this group. I just setup a squid ver 4.5 on my ubuntu machine. I
configured this proxy to receive
https packets from another device on the same LAN, and modified the iptables to
redirect the port 443 packets
to the squid proxy port 3130.
I can see the client https packet has
On 10/31/19 7:48 AM, Mark Bergman wrote:
> logformat combined2 ... %ru ... "%>h"
> example log line:
> ... http://www.google.com/ ... "...Orig-Host:
> someevilhost.appspot.com\r\nHost:
> www.google.com\r\n"
> I'm looking for a way to have Squid log the original request
You
reincluded the list for completeness and archiving.
We're building a setup where I want to be able to find domain fronting [
https://en.wikipedia.org/wiki/Domain_fronting] attempts in the logs
used test script:
>
> import requests
> proxies = {'http': 'http://10.0.0.4:8080',}
> headers =
On 31/10/19 8:48 pm, Mark Bergman wrote:
> Can i stop squid from 'repairing' host headers?
Yes.
For context:
RFC 7230 :
"If the target URI includes an authority component, then a
client MUST send a field-value for Host that is identical to that
authority component"
"If the target URI
Can i stop squid from 'repairing' host headers?
I've been all over this for hours, I can only lead this back to this change
in 1999
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=50292
I wan't this sample code to do trough squid what it would do without a
proxy at all and i want squid to log
On Friday 23 August 2019 at 00:21:48, jagadeesh am wrote:
> Hello,
>
> I have one query. Could you please suggest me what to do.
Read the documentation :)
> I have a requirement to access a web application running on Server 1 which
> is connected to Private network 192.168.2.2 network , from
Hello,
I have one query. Could you please suggest me what to do.
I have a requirement to access a web application running on Server 1 which is
connected to Private network 192.168.2.2 network , from Client machine which is
connected to Public network (16.x.x.x) using SQUID PROXY.
Is it
On Monday 20 May 2019 at 09:43:56, Peter Spencer wrote:
> Good morning
>
> Was hoping you could please advise.. we are looking to put a squid proxy in
> Azure. Reason being, we have two sites with network resilience. At the
> moment, we have one squid proxy on one of our local site DCs, and
On 3/1/19 1:47 PM, amlgp wrote:
> I have about 250 proxies/clients accessing squid and my cache deny all is on
> the first line in my squid.conf.
FYI: The position of the set of "cache" directives does not affect how
Squid works. Configuration is "compiled" at start time. At runtime,
Squid uses
I am running on a i7-7700k with 32GB of ram on Centos 6.
Squid 3.5.28 is the latest version Centos 6 can run.
I have about 250 proxies/clients accessing squid and my cache deny all is on
the first line in my squid.conf. No errors in my logs and "squid -k parse"
shows no "WARNING" messages.
On 30/10/18 4:15 PM, Angus J. wrote:
> Hi Amos
>
> Can I just copy the all squid configure file at /etc/squid/ from 2.7 to 3.5
> ?
>
Sometimes, but usually not *just* that.
The problem is that Squid-2.7 very old and also 2.6 & 2.7 was a fork of
the even older Squid-2.5 code. There have been
Hi Amos
Can I just copy the all squid configure file at /etc/squid/ from 2.7 to 3.5
?
Regards
Angus
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
On 29/10/18 3:26 PM, Angus J. wrote:
> Hi AMos
>
> Thanks for your information
>
> How to enable cache_peer configuration for any TLS/SSL for port 8005
>
Config line order is important to Squid.
Please *look* at the default squid.conf file provided here:
On 30/10/18 2:26 AM, Matus UHLAR - fantomas wrote:
> On 28.10.18 20:42, Angus J. wrote:
>> oul163:/var/log/squid # ls -rlt
>> total 84
>> -rw-r- 1 squid squid 0 Oct 22 12:21 access.log
>> -rw-r- 1 squid squid 0 Oct 22 13:02 netdb.state
>> -rw-r- 1 squid squid 17784 Oct 29 09:13
On 28.10.18 20:42, Angus J. wrote:
oul163:/var/log/squid # ls -rlt
total 84
-rw-r- 1 squid squid 0 Oct 22 12:21 access.log
-rw-r- 1 squid squid 0 Oct 22 13:02 netdb.state
-rw-r- 1 squid squid 17784 Oct 29 09:13 store.log
-rw-r- 1 squid squid 55296 Oct 29 09:33 cache.log
Hi AMos
Thanks for your information
How to enable cache_peer configuration for any TLS/SSL for port 8005
and the "allow all" 192.168.0.0 and 172.18.0.0 access permission of custom
access controls?
Regards
Angus
--
Sent from:
That shows a clean parse of the config.
Though you still have the cache_peer configuration not doing any TLS/SSL
and the "deny all" access permission above your custom access controls.
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
#
# Recommended minimum configuration:
#
# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
# RFC1918 possible internal network
# RFC1918 possible internal network
# RFC1918 possible internal network
# RFC
oul163:/etc/squid # squid -k parse
2018/10/29 10:01:46| Startup: Initializing Authentication Schemes ...
2018/10/29 10:01:46| Startup: Initialized Authentication Scheme 'basic'
2018/10/29 10:01:46| Startup: Initialized Authentication Scheme 'digest'
2018/10/29 10:01:46| Startup: Initialized
Hi Matus
The squid 3.5 cannot read the configure file of SUSE Linux 12 SP3
Regards
Angus
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squid-users@lists.squid-cache.org
Hi
oul163:/var/log/squid # ls -rlt
total 84
-rw-r- 1 squid squid 0 Oct 22 12:21 access.log
-rw-r- 1 squid squid 0 Oct 22 13:02 netdb.state
-rw-r- 1 squid squid 17784 Oct 29 09:13 store.log
-rw-r- 1 squid squid 55296 Oct 29 09:33 cache.log
oul163:/var/log/squid #
The squid.conf has been revised, i just want to 8005 port for ERP application
server.
acl localnet src 10.0.0.0/8
acl localnet src 172.16.0.0/12
acl localnet src 192.168.0.0/16
acl localnet src fc00::/7
acl localnet src fe80::/10
acl SSL_ports port 443 8000 8004 8005
acl Safe_ports port 80
acl
oul163:/var/log/squid # squid -k parse
2018/10/26 18:04:25| Startup: Initializing Authentication Schemes ...
2018/10/26 18:04:25| Startup: Initialized Authentication Scheme 'basic'
2018/10/26 18:04:25| Startup: Initialized Authentication Scheme 'digest'
2018/10/26 18:04:25| Startup: Initialized
On 26/10/18 10:49 PM, Angus J. wrote:
> https://uathrms.ouhk.edu.hk:8005/OA_HTML/AppsLogin
>
>
> the screen will shown
>
> This site can’t be reached
> uathrms.ouhk.edu.hk refused to connect.
> Try:
>
> Checking the connection
> Checking the proxy and the firewall
> ERR_CONNECTION_REFUSED
>
https://uathrms.ouhk.edu.hk:8005/OA_HTML/AppsLogin
the screen will shown
This site can’t be reached
uathrms.ouhk.edu.hk refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
--
Sent from:
I have updated the squid.conf as below:
# access control list
acl hrmsacl dstdomain .ouhk.edu.hk
http_access allow hrmsacl
#acl hrmsacl2 dstdomain devhrms.ouhk.edu.hk
#cache_peer_access devhrms allow hrmsacl2
#cache_peer_access prdhrms allow hrmsacl
#cache_peer_access uathrms allow hrmsacl
oul163:/etc/squid # squid -k parse
2018/10/26 17:44:42| Startup: Initializing Authentication Schemes ...
2018/10/26 17:44:42| Startup: Initialized Authentication Scheme 'basic'
2018/10/26 17:44:42| Startup: Initialized Authentication Scheme 'digest'
2018/10/26 17:44:42| Startup: Initialized
On 26/10/18 8:26 PM, Angus J. wrote:
> What's wrong of my squid.conf from 27 to 3.5?
> The port 3128 issue has been fixed
>
Yes that one is fixed. Now it is complaining about what you changed in
cache_peer lines.
>
> oul163:/etc/squid # squid -k parse...> 2018/10/26 10:14:14|
Processing:
What's wrong of my squid.conf from 27 to 3.5?
The port 3128 issue has been fixed
# multiling http
acl localnet src 10.0.0.0/8
acl localnet src 172.16.0.0/12
acl localnet src 192.168.0.0/16
acl localnet src fc00::/7
acl localnet src fe80::/10
acl SSL_ports port 443 8000 8004 8005
acl Safe_ports
oul163:/etc/squid # squid -k parse
2018/10/26 10:14:14| Startup: Initializing Authentication Schemes ...
2018/10/26 10:14:14| Startup: Initialized Authentication Scheme 'basic'
2018/10/26 10:14:14| Startup: Initialized Authentication Scheme 'digest'
2018/10/26 10:14:14| Startup: Initialized
I have remarked this line , the port 3128 problem is solved?
# Squid normally listens to port 3128
#http_port 3128
oul163:/var/log/squid # cat cache.log
2018/10/26 10:06:47| Set Current Directory to /var/cache/squid
2018/10/26 10:06:47 kid1| Set Current Directory to /var/cache/squid
1 - 100 of 344 matches
Mail list logo
