Docs Menu
Docs Home
/ /
Atlas App Services
/ /

Use a Custom 404 Page

On this page

  • Overview
  • Procedure
  • Create a Custom 404 Page File
  • Host the 404 File in App Services
  • Configure the 404 Resource Path in App Services
  • Pull the Latest Version of Your App
  • Create a Custom 404 Page HTML File
  • Host the HTML File in App Services
  • Specify the 404 Page in the Application Configuration
  • Deploy the Updated Hosting Configuration

You can replace the default 404 page that Atlas App Services displays when a user tries to access a resource that does not exist with a custom HTML document. You can specify this custom 404 page from the App Services UI or by importing an application configuration directory that includes the page in its hosting directory. Select the tab below that corresponds to the method you want to use.

Note

404 Errors in Single-Page Apps

When single-page application hosting is enabled, App Services always returns an HTTP 200 response with the app root regardless of the requested route. This means that you cannot specify a custom 404 page for a SPA. Instead, you should include custom code in your application to handle invalid routes.

1

You can use any hosted file as your custom 404 page. It's common to use an HTML file that incorporates the following elements:

  • A short message indicating the error, e.g. "This page does not exist."

  • Alternative links or options for the user to continue navigating.

2

Once you've created the custom 404 file, you need to upload it to App Services. To upload the file, navigate to the Hosting screen of the App Services UI, click Upload Files, and select the custom HTML file.

3

Once you have successfully uploaded the 404 file, all that's left is to configure App Services to serve that file instead of the default 404 page.

  1. On the Hosting page, click the Settings tab.

  2. Under Custom 404 Page, click Choose File.

  3. Select your custom 404 file from the list.

  4. Click Save.

Once you have updated the Hosting configuration, App Services will begin serving your custom file instead of the default 404 page.

1

To configure a custom 404 page with the App Services CLI, you need a local copy of your application's configuration files.

To pull a local copy of the latest version of your app, run the following:

appservices pull --remote="<Your App ID>"

Tip

You can also download a copy of your application's configuration files from the Deploy > Import/Export App screen in the App Services UI.

2

You can use any valid HTML file for your application's 404 page. Consider incorporating the following elements:

  • A short message indicating the error, e.g. "This page does not exist."

  • Alternative links or options for the user to continue navigating.

3

Once you've created the custom HTML file, you need to host it in App Services.

If you aren't already hosting the HTML file in App Services, add it to the hosting/files/ directory.

4

In hosting/config.json, set default_error_path to the resource path of the 404 page HTML file then save the configuration file.

"hosting": {
"enabled": true,
"default_error_path": "/pages/custom_404.html"
}
5

Once you've updated hosting/config.json you can push the updated config to your remote app. If you also added the 404 page, make sure to use the --include-hosting flag. App Services CLI immediately starts to serve your custom 404 page on push.

appservices push --remote="<Your App ID>" --include-hosting

Back

Upload Content to Atlas App Services