Stumped with issue of Nginx passing requests to php-fpm while using SSL


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

OK, the problem is that you’re listening on http on port 443. You need
to use

listen 443 ssl [default];

for ssl.

As an aside, you can combine the http: and https: configs, using the two
listen statements, and dropping the ‘ssl on’ in a single block. Makes
admin simpler… havn’t checked but the two look pretty similar.

hth,

Steve

On Thu, 2013-09-26 at 22:34 +0000, Eric Tyrer wrote:

built by gcc 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC)
–http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp
–param=ssp-buffer-size=4 -m64 -mtune=generic’

<?php * @var bool

and my nginx conf is
Associate Director – Web Systems
§ 718-262-2466


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx


Steve H. BSc(Hons) MIITP
http://www.greengecko.co.nz
Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa

Hello!

On Thu, Sep 26, 2013 at 10:34:46PM +0000, Eric Tyrer wrote:

Problem i have is that after attempting to login to wordpress over SSL php is
not being processed/executed.

I’ve got a Wordpress 3.5 multi-site using subdirectories.

[…]

nginx handles requests fine through port 80 images, css, etc are
processed normally. however, logging into to a blog results in
no php being processed like ….

<?php

[…]

my host.conf is here http://pastie.org/private/lmr05yxem5psyemzbwukig

and my nginx conf is here http://pastie.org/private/9gwjgvslwspg17frbus3g

i am at my wits end trying to figure it out by myself… It would
be great if another pair of eyes could look this over

It looks like you only have *.php handling configured inside
“location ~ /wp-(admin|login)” in your ssl server{} block.


Maxim D.
http://nginx.org/en/donation.html

Hello!

On Fri, Sep 27, 2013 at 10:45:34AM +1200, Steve H. wrote:

OK, the problem is that you’re listening on http on port 443. You need
to use

listen 443 ssl [default];

for ssl.

The config posted uses “ssl on”, which is a valid way to configure
ssl on all sockets used in a server{} block, see
http://nginx.org/r/ssl.

While it is recommended to use “listen … ssl” instead as it
allows to combine ssl and non-ssl listens in one server{} block,
it’s not something required.


Maxim D.
http://nginx.org/en/donation.html

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs