On 04/19/2017 06:44 PM, dij...@gmail.com wrote:
Do you recieve the same error while connecting to
https://www.wikipedia.org?
Yes I do.
I also tried to connect to the IP address as well; and that gives me the
same error.
The browser didn't say anything; it was squid that complained.
Regards,
Thanks Amos.As far as I can tell the only device upstream of the proxy is a relatively basic gateway/firewall. I doubt it's capable of messing with HTTP headers (and loading the site directly, as opposed to using the proxy lets it load fine behind the same gateway).I’ve attached the debug output yo
On 04/19/2017 05:35 PM, Olly Lennox wrote:
> I can confirm that disabling the ssl sesison cache seems to have resolved the
> issue.
Great!
> I found another post which references this patch to resolve the issue:
> http://www.squid-cache.org/Versions/v4/changesets/squid-4-13984.patch
I am not
Hi Alex,
Thanks for your response. I can confirm that disabling the ssl sesison cache
seems to have resolved the issue. I found another post which references this
patch to resolve the issue:
http://www.squid-cache.org/Versions/v4/changesets/squid-4-13984.patch
I've checked the source in main.
On 04/19/2017 04:48 PM, Olly Lennox wrote:
> After further investigation the problem is something to do with permissions
> related to ssl_crtd.
No, it is not (or at least not yet).
> I can run squid as root but using the default account (proxy?) it
> won't run and is giving this error in cache
Raspberry Pi (3) / Stretch repository (requird to build 3.5) / Squid 3.5.23
After further investigation the problem is something to do with permissions
related to ssl_crtd. I can run squid as root but using the default account
(proxy?) it won't run and is giving this error in cache.log:
2017/0
What OS are you using?
Eliezer
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Olly Lennox
Sent: Wednesday, April 19, 2017 7:30 PM
On 20/04/17 04:30, Olly Lennox wrote:
Sorry it's back,
I've narrowed down the problem, hopefully someone can help. When Squid starts
it creates the directory /var/run/squid as user proxy:proxy.
If I remove this or leave it as is then the application won't launch on
subsequent reboots.
If I
On 20/04/17 03:44, dij...@gmail.com wrote:
Do you recieve the same error while connecting to
https://www.wikipedia.org?
If you connect to https://91.198.174.192/* directly, your browser
schould warn you about ssl issue; that is because of:
CN = *.wikipedia.org
SAN=
*.wikipedia.org
wikiped
Sorry it's back,
I've narrowed down the problem, hopefully someone can help. When Squid starts
it creates the directory /var/run/squid as user proxy:proxy.
If I remove this or leave it as is then the application won't launch on
subsequent reboots.
If I chown the directory as root:root then t
Do you recieve the same error while connecting to
https://www.wikipedia.org?
If you connect to https://91.198.174.192/* directly, your browser
schould warn you about ssl issue; that is because of:
CN = *.wikipedia.org
SAN=
*.wikipedia.org
wikipedia.org
*.m.wikipedia.org
*.zero.wikipedia.org
On 19/04/17 18:49, turgut kalfaoğlu wrote:
Hi. Can I ask for assistance solving this problem. Many thanks!
Fedora # rpm -qa|grep squid
squid-4.0.17-1.fc25.x86_64
# uname -a
Linux www.kalfaoglu.net 4.10.10-200.fc25.x86_64 #1 SMP Thu Apr 13
01:11:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Never mind I've sorted it! The issue was due to the /var/run directory and the
program not being able to create squid.pid. I amended the permissions and seems
to be working fine now oli...@lennox-it.uk
lennox-it.uk
tel: 07900 648 252
From: Olly Lennox
To: L. P. H. van Belle ; "squid-user
Hi Louis,
Thanks a lot for the link, I'll implement that once I get this problem fixed.
Sadly the change hasn't worked. My current /etc/fstab looks like this:
proc/proc procdefaults 0 0
PARTUUID=0d001852-01 /boot vfatdefaults 0
Hai,
Im guess, squid is starting to soon, or there is not /dev/shm
Check/Try adding, if not already in /etc/fstab
none /dev/shmtmpfs defaults0 0
And reboot the server.
Or, i dont know and someone else can tell you. ;-)
But on my jessie with squid 3.5.24+ssl i dont
Thanks Amos, I'll install this. One last question if I may! Squid is working
fine now with both HTTP and HTTPS but for some reason it is refusing to launch
on boot.
It works perfectly when started with "service squid start" but not boot. The
error is:
squid.service - LSB: Squid HTTP Proxy vers
16 matches
Mail list logo