Blank error pages with Nginx/Passenger

[Lee Huffman]

Hello everyone,

I'm currently experiencing an issue where the custom error pages we have
in place (public/404.html, public/500.html, etc) are not being used when
one of these errors is generated. Instead, I'm receiving a completely
blank page (even checked the source in my browser - it's blank). Has
anyone ever experienced this issue before? I'm not having any luck
finding a solution.

Thank you!

[Lee Huffman]

Nobody has any ideas? :\

[Marius Seritan]

I would check the apache error and access logs for clues. Do the
requests register in the logs?

Do you have multiple virtual servers? Maybe the requests end up in
another configuration.

Look in the request headers, for example with curl -I to see if there
are some unexpected headers there.

Marius

[Matt Van Horn]

I am also having this problem. I have not found a solution yet.
I can hit the error page directly, i.e. http://example.com/404.html
but when there is a real error, I just get a 200 statuc code and an
empty response body.
I'm using nginx with passenger, as well - so to the person suggesting
I check apache logs, I must say I don't think it will help.
my nginx access log looks like this (sanitized):

xxx.xxx.xxx.xxx - - [23/Feb/2010:20:16:37 +0000] "GET /bad/url/goes/
here HTTP/1.1" 200 1 "-" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X
10.5; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7"

I don't see anything relevant in the error log.

-- Matt