You're right, Matus. That was the issue.
I replace as you suggested:
acl ads dstdom_regex "/etc/squid/ad_block.txt"
by
acl ads dstdomain "/etc/squid/ad_block.txt"
and now it works.
Thank you very much, Matus !
Have a nice day.
Nicolas.
Le 03/12/2022 à 15:02, Matus UHLAR - fantomas a écrit :
On 03.12.22 13:52, Nicolas wrote:
I installed squid on one of my servers, in order to block ads.
When I do not activate ads blocking, it works fine.
However, when I do activate ads blocking, some website are not accessible.
I can browse www.google.com for example, but I can't access
On 6/01/21 6:21 am, Wolfgang Paul Rauchholz wrote:
I run a home server under Centos 7 and squid 3.5.20. The config is still
work in progress as I started only today. Any tipps are welcomed
The function is as expected when working from my LAN. But when I tested
today from my cell phone from
I tried that but still 403 :/.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-DENIED-403-on-raspberrypi-tp4680711p4680723.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users
On Friday 02 December 2016 at 21:30:57, domshyra wrote:
> So I have changed the file to a sample conf file. Here is what it looks
> like now
http_access allow all
Looks to me to be your biggest problem.
Standard security practice is "allow what you specifically know you want to
allow,
So I have changed the file to a sample conf file. Here is what it looks like
now
authenticated_ips is a list of ip addresses that are going to be outgoing
ips and 192.168.1.25 isn't part of it. I have received a new 403 error which
is this below
192.168.1.25 is my macbook which is SSH'd into
On 2/12/2016 4:36 a.m., domshyra wrote:
> Hello. I have looked for countless hours to solve this problem.
> I have tried reordering the config file so that
> are all in different orders
>
> I've messed with http_access deny !Safe_ports
>
> None of the regular trouble shooting issues helped.
On 15/10/2015 8:42 p.m., Filip Maroul wrote:
> Hello I am try to configure squid3 on debian 8 x64 version of squid is 3.4.8
> Here is the conf file:
How certain are you that is the config file being used?
The access.log says things are explicitly being denied, which that
config says are allowed.
On Wednesday 05 November 2014 at 10:39:19 (EU time), navari.lore...@gmail.com
wrote:
I'm configuring a Squid Web Proxy Cache and I apply the deny policy to some
sites. This is the problem:
when people access sites with GET they have the right html error page
ERR_ACCES_DENIED
(LOG =
Hello Navari,
Just my two cents -
http://docs.diladele.com/faq/squid.html#why-i-see-cannot-connect-to-site-using-https-browser-message-instead-of-usual-site-is-blocked
Raf
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of
thank for replay
SO = CentOS 7
squid-3.4.6-1.el7.centos.x86_64
=
[root@lv-034-005 squid]# cat squid.conf
#
# Recommended minimum configuration:
#
#Default: debug_options ALL,1
#more: debug_options ALL,1 33,2 28,9
debug_options ALL,1 28,3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/11/2014 10:39 p.m., navari.lore...@gmail.com wrote:
Good day today. I' m configuring a Squid Web Proxy Cache and I
apply the deny policy to some sites l this is the problem:
when people accesses sites with GET they have the right html error
Entry created in bugzilla:
http://bugs.squid-cache.org/show_bug.cgi?id=4122
On Mon, Oct 20, 2014 at 7:25 AM, Amos Jeffries squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/10/2014 6:18 p.m., Tom Tom wrote:
Hi Amos
Do you have new findings? Should I open a
Hi Amos
Do you have new findings? Should I open a bug for better tracking?
Kind regards,
Tom
On Mon, Oct 13, 2014 at 8:16 AM, Amos Jeffries squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/10/2014 6:26 p.m., Tom Tom wrote:
Hi
Does anyone have some
Thanks Eliezer.
I think the server is the rejecting squid's IP as you pointed out,
with http_access not blocked for any machine.
Regards,
Satish
On Wed, Jun 5, 2013 at 1:51 AM, Eliezer Croitoru elie...@ngtech.co.il wrote:
Sorry Satish Thareja,
This post is outdated since squid is not in
On 4/06/2013 11:17 p.m., Satish Thareja wrote:
Hi,
I have configured my squid box without restricting 'http_access' on
any resource.
But when I try to access a resource 'host.domain.com' using the
hostname (i.e. host ) directly, I am getting TCP_DENIED/403 response
code.
I able to resolve
Amos,
The config is to allow http access for all but this case.
I came across this link :
http://www.linuxquestions.org/questions/linux-networking-3/so-many-tcp_denied-in-squid-access-log-469574/
but I do not have anything blocked in my configuration.
Is it possible that, if the 'host' does not
Sorry Satish Thareja,
This post is outdated since squid is not in 2.5\6 but on 3.3.
If you will share more from squid.conf lines we can try to help you.
if you can share the access.log we can try to understand.
please share IP etc..
if you are getting 403 it means that the server is rejecting
Have you specified
https_port 443 ... cert=
http://www.squid-cache.org/Versions/v2/2.7/cfgman/https_port.html
Regards,
Andrew
-Original Message-
From: Mike Muir [mailto:mm...@uniqueltd.com]
Sent: Tuesday, October 16, 2012 3:41 PM
To: squid-users@squid-cache.org
Subject: [squid-users]
On 10/16/2012 9:41 PM, Mike Muir wrote:
Hello,
I'm getting a TCP DENIED/403 in the access log when trying to access
all HTTPS sites via web browser. The browser displays: Error 111
(net::ERR_TUNNEL_CONNECTION_FAILED): Unknown error.
I've included the following in my squid.conf (I'm using Squid
My acl section and http_access:
acl manager proto cache_object COAP
acl localhost src 127.0.0.1/32 ::1
acl Whitelist dstdomain /etc/squid/whitelist_sites
acl ncsa_users proxy_auth REQUIRED
acl SSL_ports port 443
acl Safe_ports port 80
acl CONNECT method CONNECT
acl all src all
# cachemgr access
On 17.10.2012 09:49, Mike Muir wrote:
My acl section and http_access:
acl manager proto cache_object COAP
acl localhost src 127.0.0.1/32 ::1
acl Whitelist dstdomain /etc/squid/whitelist_sites
acl ncsa_users proxy_auth REQUIRED
acl SSL_ports port 443
acl Safe_ports port 80
acl CONNECT method
On 8/27/2012 11:09 PM, grant lowe wrote:
What am I doing wrong?
squid does exactly what the squid.conf saying..
##start
http_access allow localhost manager
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localnet
http_access allow
On May 24, 2004, at 1:15 PM, Jose Nathaniel Nengasca wrote:
And by the way, 192.168.0.0/255.255.0.0 is correct? are you using
class B on
192.168? instead of using class C?
I'm using more than one /24 in 192.168, so I just mask it off at /16.
:)
smime.p7s
Description: S/MIME cryptographic
On Sun, May 23, 2004 at 03:35:13PM -0500, jorn wrote:
Hello,
I searched the archives, edited my ACLs, but I can't figure this one
out. A Version 2.5.STABLE5 that seemed to be working fine is now
rejecting users with an access denied message. My access log has
entries like the following:
On May 23, 2004, at 3:57 PM, Christoph Haas wrote:
Try this:
debug_options ALL,1 33,2
and watch your cache.log to see which ACL blocks you.
Christoph
--
My cache.log seemed to show no more interesting data than before, which
is essentially startup data and nothing else. Even when I set :
On May 23, 2004, at 3:57 PM, Christoph Haas wrote:
Try this:
debug_options ALL,1 33,2
and watch your cache.log to see which ACL blocks you.
Christoph
--
My cache.log seemed to show no more interesting data than before, which
is essentially startup data and nothing else. Even when I set :
On Sun, May 23, 2004 at 04:32:23PM -0500, jorn wrote:
On May 23, 2004, at 3:57 PM, Christoph Haas wrote:
Try this:
debug_options ALL,1 33,2
and watch your cache.log to see which ACL blocks you.
Christoph
My cache.log seemed to show no more interesting data than before, which
is
On May 23, 2004, at 4:49 PM, Christoph Haas wrote:
May I assume you have restarted squid?
Christoph
A fair question. :) The answer is yes, several times. I even started
it and kept it from running in the background:
squid -N -d 9
Nothing useful came up on my console; nothing. I'm a
It seems that your netmask ACL on ALL is a bit messy, try not to use
255.255.255.255, use 0.0.0.0 instead...
Hello,
I searched the archives, edited my ACLs, but I can't figure this one
out. A Version 2.5.STABLE5 that seemed to be working fine is now
rejecting users with an access denied
The request is denied by your http_access rules.
CONNECT is a request for SSL tunneling. Most likely this is a SSL site
running on a non-standard SSL port (if SSL at all...). See your
squid.conf, especially the Safe_Ports and SSL_Ports definitions..
Regards
Henrik
mån 2003-02-24 klockan 16.17
31 matches
Mail list logo
