thanks. i finally figured things out -- the error was being generated by an upstream backend that openresty was connected to. it was supposed to be down, but was somehow up.
the error page just happened to be *almost identical* to the standard nginx error -- there were just a few blank lines added in.
this drove me crazy.