Re: [squid-users] FATAL: No valid signing SSL certificate configured for https_port

What is the output of "squid -v" when using 3.4.3?
I am not sure what the issue is and I can test it with my own
certificate later on.

If you see that I have not tested it yet in the next week try to send me
an email to remind me that it was not verified yet.

Eliezer

On 07/01/2014 09:25 PM, John Gardner wrote:
> 2014/07/01 19:14:47| Initializing https_port X.X.X.95:443 SSL context
> 2014/07/01 19:14:47| Using certificate in
> /usr/newrprgate/CertAuth/www_domain_info/14735441.crt
> 2014/07/01 19:14:47| storeDirWriteCleanLogs: Starting...
> 2014/07/01 19:14:47| Finished. Wrote 0 entries.
> 2014/07/01 19:14:47| Took 0.00 seconds ( 0.00 entries/sec).
> FATAL: No valid signing SSL certificate configured for https_port X.X.X.95:443
> Squid Cache (Version 3.4.3): Terminated abnormally.
> CPU Usage: 0.064 seconds = 0.051 user + 0.013 sys
> Maximum Resident Size: 32032 KB
> Page faults with physical i/o: 0
>
> I think I might try the Oracle 6.5 repo version Squid 3.1 RPM which
> comes with the distro first, before I start compiling a new version of
> Squid.
>
> John
Received on Tue Jul 01 2014 - 18:41:29 MDT