NOTE: please dont use fancy quoting when posting through the Nabble
interface. It erases the critical information about your problem from
any other copy of the list:
On 3/12/2016 9:30 a.m., domshyra wrote:
> So I have changed the file to a sample conf file. Here is what it looks like
> now
>
>
>
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 ma
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.
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.
I am on wifi on the pi with a static ip address, and I
Bump for the mailing list...
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-DENIED-403-on-raspberrypi-tp4680706p4680710.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mail
