Custom error pages

Server NGINX
1

I’m using nginx to reverse proxy my web server. I want to be able to
return a custom 503 page from nginx when I choose. I’m able to get
nginx
to return a 503 page by adding it to the top of the location. But that
just returns the default nginx error page. How to do change this to a
custom page?

Thanks.

2

On Tue, Mar 13, 2012 at 09:38:56AM -0400, Bai Shen wrote:

Hi there,

I’m able to get nginx
to return a 503 page by adding it to the top of the location. But that
just returns the default nginx error page. How to do change this to a
custom page?

Does Module ngx_http_core_module give the info you need?

f

Francis D. [email protected]

3

IIRC, I tried that but wasn’t able to get nginx to find my local error
page.

4

How do I get nginx to serve the page? I added in the line from the
link,
but I still get the default nginx page, not my custom one.

5

On Thu, Mar 15, 2012 at 10:48:13AM -0400, Bai Shen wrote:

Hi there,

How do I get nginx to serve the page? I added in the line from the link,
but I still get the default nginx page, not my custom one.

===
server {
error_page 503 /my-503-error.html;
location / {
return 503;
}
location = /my-503-error.html {
internal;
}
}

will serve the content of the file my-503-error.html in your document
root with a http status 503 for (almost) every request to this server.

f

Francis D. [email protected]

6

I added this into my config file, and put my-503-error.html in the same
location as the default 50x.html file, but all I get is a generic 404
error
page.

Is that not the document root for nginx?

7

I should still be able to use the listen and server_name directives to
have
this apply to certain servers, correct?

8

On Fri, Mar 16, 2012 at 09:43:39AM -0400, Bai Shen wrote:

Hi there,

I added this into my config file, and put my-503-error.html in the same
location as the default 50x.html file, but all I get is a generic 404 error
page.

You got an error page.

What does the error log say?

Either put your 503 file there; or configure “root” so that it is
correct
within this location{}.

If you’re still having problems, please follow the “debug” instructions
to make it easier for people to help you.

Details on the web site, but in brief:

what did you do?
what did you see?
what did you expect to see?

and the more specific you are, the easier it will be for someone else to
reproduce the problem you are reporting.

Good luck with it,

f

Francis D. [email protected]

9

I got my error page to show up. However, the css and image files don’t
load. I tried changing the location, but that doesn’t seem to work.

Any suggestions?

Thanks.

10

Doh! I forgot 'bout the error log.

Apparently, nginx is looking for the file in /etc/nginx//html However,
the
default html files were installed in /usr/share/nginx/html

I installed from the repo, so I’m not sure why it installed in one place
yet is looking in another. And I don’t have a root html directory set
in
any of the conf files.

11

On Wed, Mar 28, 2012 at 03:42:45PM -0400, Bai Shen wrote:

Hi there,

I got my error page to show up. However, the css and image files don’t
load. I tried changing the location, but that doesn’t seem to work.

Any suggestions?

Try changing the location again. Maybe it will work this time.

Or alternatively:

Please fill in the details:

what did you do?

That will be something like “curl -i http://myserver/myfile.css”

what did you see?

That will be whatever you got back – the content of
/var/tmp/myfile.css,
or the content of another file, or some error message. There might be
more details available in log files.

what did you expect to see?

That will be something like “http 200 and the content of
/usr/local/nginx/html/myfile.css”.

and the more specific you are, the easier it will be for someone else to
reproduce the problem you are reporting.

Provide the relevant part of nginx.conf from a machine where you saw
the problem. If you don’t know what is the relevant part, provide the
whole thing.

It doesn’t have to be your “live” config, but it should be a config that
you ran on a test machine. The smaller the config, the better.

If you make it easy for someone to run the same server config as you,
and run the same client commands as you, and see the same error output
as you; then you make it easy for that person to try to help resolve the
problem you saw.

If you don’t, you don’t.

f

Francis D. [email protected]

12

My conf looks like this.

server {
listen 192.168.1.1:80;
server_name example.com;

error_page 503 /maint/503.html;

location /maint/503.html {
internal;
}

location /maint/ {
root /etc/nginx/html;
}

server {
listen 192.168.1.1:80;
server_name example.com;

location / {
proxy_pass http://192.168.1.2;
}
}

To show the 503 page instead of my site, I uncomment the top server
block.
When I want to bring the site back, I comment the top block out. The
/maint/ location was what I changed to get the css and images to work.
However, I’m not sure that it’s the best solution. Also, I’m assuming
that
there’s a better way to show/hide the 503 page than commenting out the
whole server block.