On Fri, Mar 20, 2015 at 08:57:10PM +0200, Gena Makhomed wrote:
>
> Probably "include ssl_common;" contains "ssl on;"
> directive, which forces nginx to use HTTPS on 50.250.218.168:80
>
Yup. This was right. I was shocked because I had thought I had omitted
this directive. But I looked and there it
On 20.03.2015 20:35, B.R. wrote:
You have a duplicate listen directive with same IP address and same port
in both server blocks.
I doubt that is a valid configuration.
Yes, this is valid configuration. See
http://nginx.org/en/docs/http/request_processing.html
http://nginx.org/en/docs/http/ser
On 20.03.2015 20:01, David Benfell wrote:
I am attempting to strip www. and force SSL. Here are the blocks I'm
using:
server {
listen 50.250.218.168:80;
listen 50.250.218.168:443 ssl;
listen [2001:470:67:2b5::10]:80;
l
You have a duplicate listen directive with same IP address and same port in
both server blocks.
I doubt that is a valid configuration. Have you checked nginx -t and error
logs on reload/start?
I suggest you have a server block listening for HTTP on port 80 and another
block reponsible for HTTPS tr
Hi all,
I am attempting to strip www. and force SSL. Here are the blocks I'm
using:
server {
listen 50.250.218.168:80;
listen 50.250.218.168:443 ssl;
listen [2001:470:67:2b5::10]:80;
listen [2001:470:67:2b5::10]:443 ssl;
