Skip to content

What if your application could look nice even when it's crashing?

License

Notifications You must be signed in to change notification settings

joppuyo/nice-nginx-error-page

Repository files navigation

Nice Nginx Error Page

REUSE status

What if your application could look nice even when it's crashing? Try this custom error page for Nginx.

Preview

Installation

Copy templates/custom-error-page folder in your web root folder, for example /usr/share/nginx/html/custom-error-page.

Copy config/custom-error-page folder into your nginx config directory, for example /etc/nginx/conf.d/custom-error-page.

Edit custom-error-page/error-page.conf so the root values point to the correct folder on your server.

In your main nginx config file, include custom-error-page/http-statuses.conf inside the http block, outside the server block, like this:

include /etc/nginx/conf.d/custom-error-page/http-statuses.conf;
# ^ Add this line

server {
  listen 80;
  listen [::]:80;
  server_name localhost;
  # Your server configs here
}

In your nginx config file, include custom-error-page/error-page.conf inside your server block, like this:

include /etc/nginx/conf.d/custom-error-page/http-statuses.conf;

server {
  listen 80;
  listen [::]:80;
  server_name localhost;
  
  include /etc/nginx/conf.d/custom-error-page/error-page.conf;
  # ^ Add this line
  
  # Your server configs here
}

Restart Nginx and you're done.

Feel free to modify the error template to your liking!

FAQ

I'm using Nginx with fastcgi_pass or proxy_pass and I see an error page from the upstream instead of the custom one

By default, Nginx will use the error pages from upstream if they are available. Nginx will only show it's own error pages if it can't connect to the upstream server. For example in case of timeout or if the upstream is down. You can override this behavior by setting fastcgi_intercept_errors on; or proxy_intercept_errors on;.

I'm using xxx_intercept_errors but I would like to still show the custom 404 from my application server.

You can accomplish this by removing 404 from the list of statuses in error_page directive, in the file custom-error-page/error-page.conf. TODO: check if this actually works.

Thanks

I would like to thank the article One NGINX error page to rule them all for serving as inspiration. Using Server Side Includes drastically cuts down the number of required templates.

License

MIT.

For detailed license information, see the individual file headers and .reuse/dep5.

About

What if your application could look nice even when it's crashing?

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published