Angular 4.x – Add a 404 page

For a frontend application like Angular, the 404 page is served by the frontend application rather than the web server. To make this work, we should always return the index.html of our angular application for all applications, except for asset files.


Adding 404 status code in header for the 404 page component using Angular Universal.

Configure Server

When I first deployed my first Angular app in production, I quickly realized that it throws the 404 error when I directly visit a page other than the home page, for example, the /projects page. This is because there is only one HTML file, which is the index.html and the rest are asset files.

According to the Angular deployment documentation, we need to route all requests into index.html unless the requested file actually exists in the dist directory.

Here is a simple nginx configuration for that:

try_files $uri $uri/ /index.html;

It simply tries to serve the requested resource but when not found, it serves the index.html instead. Below is the full configuration.

server {
    listen 80;
    root /data/www/html/sites/;
    index index.html index.htm index.nginx-debian.html;
    location / {
        try_files $uri $uri/ /index.html;
        autoindex on;

This way, when I visit /projects or /kung-fu, the nginx server will just serve the index.html file. Whether or not these routes actually exists now depends on the Angular application.

Add a 404 page Angular component

To handle 404 pages in Angular, we just need to make use of the ** routing path of Angular router and handle it with a 404 component.


// Other imports...
import { NotfoundComponent } from './notfound/notfound.component';

const routes: Routes = [
  // Other routes...
  { path: '**',  component: NotfoundComponent },

// The rest of the routing module here...

Note the path and the component used. We will create the component later.


// Other imports...
import { NotfoundComponent } from './notfound/notfound.component';

  imports: [
  declarations: [
    // Other components
  bootstrap: [
export class AppModule { }

We also need to declare the component in our app module.


<h1>Error 404</h1>
<p>Page not found</p>


import { Component } from '@angular/core';

  selector: 'app-notfound',
  templateUrl: './notfound.component.html'

export class NotfoundComponent { }

Restart the development server and we should have our 404 component working.

9 thoughts on “Angular 4.x – Add a 404 page”

  1. Hi,

    Thanks for the solution, but how so change the header response status to 404.

    Ramesh C

  2. Interesting question, deserves another post. It needs Angular Universal to make it work.

  3. I am stuck in this . It successfully set header to 404 but it does not show component template . I need a view along with header set 404. Please help.

  4. @divyansh – I used Angular Universal already as it gives me more control. Last time I checked, my template is loading but it does not send the 404 status code. I’ll revisit the other post and see if I can fix it.

Leave a reply

Your email address will not be published. Required fields are marked *