Hi all,
Problem found.
This really was caused by an SSL cert name mismatch.
> On 23 Jan 2018, at 20:27, Sophie Loewenthal wrote:
>
> Hi,
>
> Chrome and Firefox can connect to my webserver over https running http2.
> Safari 11 cannot, and gave no error messages
Hi,
Chrome and Firefox can connect to my webserver over https running http2.
Safari 11 cannot, and gave no error messages other than "cannot connect".
There is a certificate name mismatch, but I thought Safari would still let me
know why it did not connect. The SSL cert is otherwise valid.
I
That solved the problem. Thank-you Andreas.
> On 23 Jan 2018, at 15:52, A. Schulze wrote:
>
>
> Sophie Loewenthal:
>
>
>> ssl_ecdh_curvesecp521r1;
>
> I never used that curve, If there's no specific reason for secp521r1, try
> secp3
Hi,
Did I add or remove the wrong ciphers for http2, and are they in the correct
order? I found plenty of different documents on the Internet. Since mine is
now broken, I should ask here :) Any ideas?
Error message from Chrome:
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
My nginx.conf has,
Oh. the closing }
It’s been a long day <:-I
> On 4 Dec 2017, at 18:57, Ian Hobson wrote:
>
> Hi Sophie,
>
> On 04/12/2017 16:49, Sophie Loewenthal wrote:
>> Hi,
>> When I put this location block for case insensitive matching into the vhost
>>
Hi,
When I put this location block for case insensitive matching into the vhost
produced an error.
nginx: [emerg] location "/" is outside location
".(jpg|jpeg|png|gif|ico|css|js)$" in /etc/nginx/sites-enabled/example.conf:13
My vhost has this:
server {
…
location ~* .(jpg|jpeg|png
Hi,
Debian Wheezy had a package called nginx-naxsi that had the WAF NAXSI compiled.
I’ve not seen this on recent versions of Debian.
Does this still exist or was this moved to another repository?
Kind regards, Sophie
___
nginx mailing list
ngin
