Custom 500 Error Page Examples
Contents |
All Topics Web design 30 brilliantly designed 404 error pages 30 brilliantly designed 404 error pages By Creative Bloq Staff Web design Clicking custom 500 error page nginx on a broken link is a pain, but a witty and well-designed
Apache Custom 500 Error Page
error page at least sweetens the pill. Here are some designs to inspire you. Shares Page 1
Rails Custom 500 Error Page
of 2: Page 1 Page 1 Page 2 If you're working on how to start a blog or website, don't forget the all-important 404 page – a standard response
Django Custom 500 Error Page
code in HTTP telling the user, in effect, that they've clicked on a broken link.It's traditionally been an immense source of frustration, but in recent years, creatives have taken up the challenge of designing bespoke 404 pages that at least sweeten the pill of finding you're in the wrong place.When done really well, they become mini-ambassadors for the website 500 error message examples itself, being shared on Twitter and blogs as an example of the site or service's keenness for customer service and unique approach to design. The 30 we present here have achieved all this and more, so take a look and be inspired to create your own bespoke 404 pages!01. Bluegg This noisy chap provides a hilarious notification that you're in the wrong placeThe 404 page of creative and digital design agency is simple, but so effective. Upon loading, you're greeted by a goat, who lets out the most almighty high-pitched scream, alerting you that the page doesn't exist. The inner child in us emerged and we must admit to playing this repeatedly, while crying a little with laughter. Bravo, guys.02. Hot Dot Production Hot Dog's 404 page is seriously addictiveHot Dot Productions has applied it's 'where design meets technology' tagline to its impressive 404 page, which features the three numbers made up of hundreds of tiny dots that change direction in response to mouse movements. Seriously cool.03. Airbnb If you drop ice cr
custom error pages Browse by products and services DV and VPS Hosting Grid Shared Hosting DV Developer Hosting Legacy DV Hosting Applies to: Grid Difficulty: Medium Time: 20 Tools needed: FTP Applies to: All DV Difficulty: Medium Time: 20 Tools needed: FTP sample 500 error page Overview This article explains how to set up custom error documents for your server. Instead custom 404 error page of a plain 404 Not Found or 500 Internal Server Error page, you can show your visitors a customized page that matches custom 401 error page your site design. READ ME FIRST The publishing of this information does not imply support of this article. This article is provided solely as a courtesy to our customers. Please take a moment to review the http://www.creativebloq.com/web-design/best-404-pages-812505 Statement of SupportStatement of Support. Results You should make these pages simple to generate - plain HTML is best. 404 pages especially are needed frequently, and the server will spend a lot of resources if it has to process a complex custom page every time someone generates a 404 request. Your .htaccess file will override the server default error pages, directing Apache to use custom pages instead. Using custom error pages NOTE: https://mediatemple.net/community/products/dv/204643020/creating-custom-error-pages You MUST add a "/" at the beginning of the path to your custom error document. The "/" references the document root of your server (/home/00000/domains/example.com/html/httpdocs by default). The path to your error document should be from the document root, regardless of whether you upload your .htaccess file to the document root directory or to a subdirectory. That's it! Your change will take affect within minutes. You can test your error handling by trying to generate the error yourself. For example, to test a new 404 Not Found page, try visiting http://example.com/this_subfolder_does_not_exist/. Replace example.com with your own domain name. You should see your custom Not Found page. Common client and server errors NOTE: For more information about different types of Status Codes, please see this page at w3.org: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Create your error pages. The documents can have any name. The example will use not_found.html. Upload your error pages to your server using FTP. These pages should go inside your html (/home/00000/domains/example.com/html/) directory or a subdirectory. The example will use the subdirectory errors/ (/home/00000/domains/example.com/html/errors/) for error documents. Upload your error pages to your server using FTP. These pages should go inside your httpdocs directory or a subdirectory. The example will use the subdirectory errors/ for error documents. Create an .htaccess file with the following lines, or ad
a free tool we're calling Better Error Pages! Better Error Pages is a mini-site that helps you build customizable 404, 500-level, and maintenance pages in 60 seconds. Here's how it works: http://blog.statuspage.io/level-up-your-400-500-maintenance-pages We ask you a few questions about your company (things like Homepage URL and https://www.digitalocean.com/community/tutorials/how-to-configure-apache-to-use-custom-error-pages-on-ubuntu-14-04 Support Email Address). You have the opportunity to personalize the look of your error pages. When you're done, we'll send you a link to download the flat HTML files for your shiny new 404, 503 and Maintenance pages. You should check out Better Error Pages for yourself...it's free! Why We Built Better Error Pages Giving error page Back We built Better Error Pages for the same reasons we built StatusPage.io: we saw an opportunity to take all of the work out of doing something that people wanted to do but just didn't have the time. Error pages are always the first thing to get neglected, but professional, informative error pages lend legitimacy and confidence to a product. We wanted to make it so easy that 500 error page people wouldn't think twice when it came to error pages. We use tons of free and open-source tools at StatusPage.io. This is our way of giving something back to the community that's helped us get to where we are today. Karma Based Marketing I would be lying if I said we didn't think we'd get some value out of releasing this. Colin from Customer.io wrote a post calling things like this "Karma Based Marketing". Here's how Colin describers Karma Based Marketing. Your Karma based marketing efforts are about building trust with people. Yes, ultimately I hope they’ll lead to sales for you. But today, as you help prospective customers solve their problems, help them as humanly as possible with genuine care. Good things will happen later. I promise. Better Error Pages is a perfect example of Karma Based Marketing. It's a completely free tool to use, even if you're not a StatusPage.io customer. Our hope is that people will have a good experience with our brand, and when the day comes that they realize they need a status page, they'll think of us. At the end of the day, people prefer doing business with people they like. We'll be investing more money and develo
In submit Tutorials Questions Projects Meetups Main Site logo-horizontal DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In submit View All Results By: Justin Ellingwood Subscribe Subscribed Share Contents Contents We hope you find this tutorial helpful. In addition to guides like this one, we provide simple cloud infrastructure for developers. Learn more → 6 How To Configure Apache to Use Custom Error Pages on Ubuntu 14.04 Posted Jun 9, 2015 45.6k views Apache Ubuntu Introduction Apache is the most popular web server in the world. It is well-supported, feature-rich, and flexible. When designing your web pages, it is often helpful to customize every piece of content that your users will see. This includes error pages for when they request content that is not available. In this guide, we'll demonstrate how to configure Apache to use custom error pages on Ubuntu 14.04. Prerequisites To get started on with this guide, you will need a non-root user with sudo privileges. You can set up a user of this type by following along with our initial set up guide for Ubuntu 14.04. You will also need to have Apache installed on your system. Learn how to set this up by following the first step of this guide. Creating Your Custom Error Pages We will create a few custom error pages for demonstration purposes, but your custom pages will obviously be different. We will put our custom error pages in the /var/www/html directory where Ubuntu's Apache installation sets its default document root. We'll make a page for 404 errors called custom_404.html and one for general 500-level errors called custom_50x.html. You can use the following lines if you are just testing. Otherwise, put your own content in these locations:
- echo "
Error 404: Not found :-(
" | sudo tee /var/www/html/custom_404.html - echo "
I have no idea where that file is, sorry. Are you sure you typed in the correct URL?
" | sudo tee -a /var/www/html/custom_404.html - echo "
Oops! Something went wrong...
" | sudo tee /var/www/html/custom_50x.html - echo "
We seem to be having some technical