Hitch SSL chain issues with Google Chrome

[Andrei]

Chain order needs to be followed per RFC. While not all browsers may care,
quite a few payment gateways do.

On Wed, Oct 18, 2017 at 11:15 AM, Nicolas Delmas <colas.delmas at gmail.com>
wrote:

> Hello,
>
> I'm surprising, that we need to keep an order to merge all files. In my
> case I contact like this and never get a problem :
>
> cat /etc/letsencrypt/live/example.org/privkey.pem \
>       /etc/letsencrypt/live/example.org/fullchain.pem \
>       /etc/ssl/certs/dhparam.pem \ > /etc/hitch/example.org.pem
>
> chmod 0600 /etc/hitch/example.org.pem
>
> I think it was because you tried to merge the chain and fullchain
>
>
>
> *Nicolas Delmas*
> http://tutoandco.colas-delmas.fr/ <colas.delmas at gmail.com>
>
>
>
>
>
>
>
> 2017-10-18 17:13 GMT+02:00 Admin Beckspaced <admin at beckspaced.com>:
>
>>
>> On 18.10.2017 12:54, Angelo Höngens wrote:
>>
>>> Just do cert + chain + privkey, in that order.
>>>
>>> Thanks ;)
>>
>> re-merging the certs in that order solved the issue.
>>
>> Greetings
>> Becki
>>
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20171019/310ccd55/attachment.html>