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

Eliezer

The line that was working but is now causing problems is;

https_port 10.x.x.95:443 accel
cert=/usr/newrprgate/CertAuth/cert/cert.crt
key=/usr/newrprgate/CertAuth/cert/key.pem
cipher=ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM
options=NO_SSLv2 defaultsite=server_1.uk

John

On 30 June 2014 12:06, John Gardner <jeg1972_at_gmail.com> wrote:
> Eliezer
>
> The line that was working but is now causing problems is;
>
> https_port 10.x.x.95:443 accel
> cert=/usr/newrprgate/CertAuth/cert/cert.crt
> key=/usr/newrprgate/CertAuth/cert/key.pem
> cipher=ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM
> options=NO_SSLv2 defaultsite=server_1.uk
>
> On 30 June 2014 01:49, Eliezer Croitoru <eliezer_at_ngtech.co.il> wrote:
>> On 06/29/2014 09:30 PM, John Gardner wrote:
>>>
>>> FATAL: No valid signing SSL certificate configured for https_port
>>> 10.x.x.95:443 and Squid terminates.
>>
>>
>> Can you share the relevant line from squid.conf?(replacing confidential
>> data)
>>
>> (I am planning for the next release 3.4.6 to release a Oracle version of the
>> RPM but it will be only 6.5 compatible)
>>
>> Eliezer
Received on Mon Jun 30 2014 - 11:07:57 MDT