Nginx either works with Wordpress or it doesn’t. That’s not very
friendly, or practical. Static websites are a minority these days.
[igor@igor ~ 585]$ curl -I http://wordpress.com/
HTTP/1.1 200 OK
Server: nginx/0.6.29
Date: Fri, 25 Apr 2008 09:54:19 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Vary: Cookie
X-hacker: If you’re reading this, you should visit Work With Us – Automattic
and apply to join the fun, mention this header.
X-Pingback: http://wordpress.com/xmlrpc.php
Nginx either works with Wordpress or it doesn’t. That’s not very
friendly, or practical. Static websites are a minority these days.
[igor@igor ~ 585]$ curl -I http://wordpress.com/
HTTP/1.1 200 OK
Server: nginx/0.6.29
Date: Fri, 25 Apr 2008 09:54:19 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Vary: Cookie
X-hacker: If you’re reading this, you should visit Work With Us – Automattic
and apply to join the fun, mention this header.
X-Pingback: http://wordpress.com/xmlrpc.php
The people coming here to post comments defending Nginx is very
nonproductive. In my first thread requesting the same assistance we
already established Wordpress migrated to Nginx, which only frustrates
me further.
Rather than beat a dead horse, make it easier to setup Wordpress to run
under Nginx by offering more suggestions to help people like me to get
it running. I’ve already tried the standard approaches, which is why I’m
here.
Like I said, Nginx either works, or it doesn’t, since no one is willing
to do a thorough documentation of the process. I would, and I would post
it on my tech site, but I can’t seem to get adequate help from the REAL
experts, only some who have succeeded in an simple way, and others who
simply want to defend Nginx, which I have used for a year to serve
images, rather than offering constructive help.
Is this an example of how helpful this forum is? I thought it was more
than that?
In my opinion, if Nginx doesn’t have a tutorial clearly explaining how
to configure and use Nginx with Wordpress, which is the number one blog
script software in the world, then Nginx isn’t ready for prime time.
Nginx won’t be widely accepted and used until it’s Wordpress friendly
with a proper tutorial, and support. I would love to write it and post
it on my tech site, but I can’t seem to even solve my own issue, and no
one appears to be able to help.
Just to have more details, have you tried to follow these directions?
The people coming here to post comments defending Nginx is very
nonproductive. In my first thread requesting the same assistance we
already established Wordpress migrated to Nginx, which only frustrates
me further.
Rather than beat a dead horse, make it easier to setup Wordpress to run
under Nginx by offering more suggestions to help people like me to get
it running. I’ve already tried the standard approaches, which is why I’m
here.
Like I said, Nginx either works, or it doesn’t, since no one is willing
to do a thorough documentation of the process. I would, and I would post
it on my tech site, but I can’t seem to get adequate help from the REAL
experts, only some who have succeeded in an simple way, and others who
simply want to defend Nginx, which I have used for a year to serve
images, rather than offering constructive help.
Is this an example of how helpful this forum is? I thought it was more
than that?
I simply pointed out that nginx clearly does work with Wordpress. If
you’re trying to get it to do so, you might take the knowledge that it
can be done as an indication that you don’t need to give up yet, or
indeed to start declaring quite so soon that “nginx isn’t ready for
prime time” because you can’t get one particular application to work
with it.
Regarding your particular problem, from my personal experience with
PHP and nginx, it doesn’t sound like a problem with nginx and
Wordpress per se, but rather a PHP/FCGI/nginx logging issue. I’ve had
the “blank page” error with PHP and nginx on a number of occasions,
and having spent a while tracking down the error, I’ve usually found
that it’s some PHP error which is being hidden for some reason, I
suspect related to fastcgi_intercept_errors or similar. PHP’s error
logging seems strangely unpredictable to me sometimes; first step is
obviously to make sure that log_errors is on, the error_reporting
setting is correct, and you set error_log to somewhere specific.
Incidentally, this isn’t a forum, it’s a mailing list which is
delivered to people’s personal inboxes, and you’re reading it through
a web-forum interface. That might be why you find you sometimes get
strong reactions when you make strong statements of opinion.
The webserver never just shows a blank page and if you have run web
application for years as you say you should know that PHP is the
problem here. If you get the admin panel to work and then you get
blank pages on the rest then of course it is PHP the problem. And
first you were asking for rewrite rules and people gave you the exact
rules and I am sure they work because I have the same in my config
and it took me less than 5 minutes to get my blog to run under Nginx,
why, because I was not bothering this list with problems related to my
PHP configuration. Please, hire a PHP developer or admin to fix your
problem because it is something specific to your PHP setup and just
stop posting. As Igor said it comes to my mailbox and I am tired of
deleting your emails…
I simply pointed out that nginx clearly does work with Wordpress. If
you’re trying to get it to do so, you might take the knowledge that it
can be done as an indication that you don’t need to give up yet, or
indeed to start declaring quite so soon that “nginx isn’t ready for
prime time” because you can’t get one particular application to work
with it.
Regarding your particular problem, from my personal experience with
PHP and nginx, it doesn’t sound like a problem with nginx and
Wordpress per se, but rather a PHP/FCGI/nginx logging issue. I’ve had
the “blank page” error with PHP and nginx on a number of occasions,
and having spent a while tracking down the error, I’ve usually found
that it’s some PHP error which is being hidden for some reason, I
suspect related to fastcgi_intercept_errors or similar. PHP’s error
logging seems strangely unpredictable to me sometimes; first step is
obviously to make sure that log_errors is on, the error_reporting
setting is correct, and you set error_log to somewhere specific.
Incidentally, this isn’t a forum, it’s a mailing list which is
delivered to people’s personal inboxes, and you’re reading it through
a web-forum interface. That might be why you find you sometimes get
strong reactions when you make strong statements of opinion.
Good luck getting it working.
Igor
Thank you Igor for making some good points. I won’t give up on Nginx,
which is why I’m still here. I will eventually solve this issue. I will
look into PHP further to see if I can get it to output an error that
will help resolve the blank page. You could very well be correct that
PHP could have been the culprit all along, and not my Nginx
configuration.
The webserver never just shows a blank page and if you have run web
application for years as you say you should know that PHP is the
problem here. If you get the admin panel to work and then you get
blank pages on the rest then of course it is PHP the problem. And
first you were asking for rewrite rules and people gave you the exact
rules and I am sure they work because I have the same in my config
and it took me less than 5 minutes to get my blog to run under Nginx,
why, because I was not bothering this list with problems related to my
PHP configuration. Please, hire a PHP developer or admin to fix your
problem because it is something specific to your PHP setup and just
stop posting. As Igor said it comes to my mailbox and I am tired of
deleting your emails…
You only have yourself to thank for creating one more email to delete.
Great mailing list. So many arrogant people here making the considerate
folks look bad.
FYI Kiril, I haven’t confirmed that my issue is related to my PHP
configuration. I only said I’d look into it as a possibility. In fact,
it’s reasonable to expect Wordpress to run properly under Nginx if it’s
running properly under Apache, especially when PHP executes when
accessing the control panel, but not the homepage of the site. Doesn’t
seem like a clear PHP problem. If Apache can do it, why can’t Nginx?
Next time you pull your head out of your butt, open your eyes before you
open your mouth. Your breath smells terrible.
I recommend swapping to Multi User Wordpress if you have more than one
blog to manage.
I don’t think I’d recommend it. It seems like too much of a hack
(unless they’ve matured it now)
You can easily support multiple blog instances just by using
conditionals inside of wp-config.php. We support multiple blogs (and
dev/prod instances of each) using the same codebase on all the blog
sites…
Well it seems to work for Wordpress.com which gets 150 million page
views per month.
Mu Wordpress runs some pretty massive multi user dynamic sites. I
don’t know how you could justify calling it a hack unless you want to
call any piece of open source software a hack.
I’ve met a guy who runs a site off Mu Wordpress who hosts a hundred
thousand blogs and gets 600,000 page views per day.
Well it seems to work for Wordpress.com which gets 150 million page
views per month.
Mu Wordpress runs some pretty massive multi user dynamic sites. I
don’t know how you could justify calling it a hack unless you want to
call any piece of open source software a hack.
I’ve met a guy who runs a site off Mu Wordpress who hosts a hundred
thousand blogs and gets 600,000 page views per day.
I’m not saying it doesn’t perform.
At the point I evaluated it, it was patchwork on top of the normal
wordpress install, had plugin incompatibilities, and seemed overly
complex and weird for how simple it could really be.
I’m sure it’s better now though. However, simple wp-config logic fits
our setup perfectly.
