# General error messages

This page helps you identify the page you reached and match an error type with its message.

| If you need to… | Go to |
| --- | --- |
| Recognize the page you reached | [Recognize the error page](#recognize-the-error-page) |
| Match an error type to its message | [Match an error message](#match-an-error-message) |
| Handle a route that does not reach its test page | [When the error page cannot be reached](#when-the-error-page-cannot-be-reached) |
| Get help with a wider application issue | [Getting help](doc:getting-help) |
| Work through common application problems | [Common issues and solutions](doc:common-issues-and-solutions) |

## Before you start

Use this page to identify the error type and read the exact message associated with its
route.

Prerequisites

- Have the route name or error class in front of you.
- Use the message table to identify the error type before you continue.

**Result:** You know the route name or error class to use in the message table.

## Recognize the error page

The error page is the page shown when the requested route cannot be found. Use its heading,
message, and error number to recognize the state before choosing what to do next.

The route path is `/test_error_view`. It displayed `Page not found`, followed by
`This page does not exist, but you can create it as you are editor of this site.` and
`Error 404`.

The page displayed **Search** and **Create Page**. The page read `Page not found`.

**Result:** You can identify the page state from the route path, `Page not found`, the
explanatory message, and `Error 404`. Next, use the message table to match the error type.

## Match an error message

An HTTP route returns an HTTP error response. An RPC route raises an error for an RPC request.
Use the error class and route type together when matching a message.

| If you need to identify… | Select the error link in the Error type column | Message |
| --- | --- | --- |
| An HTTP user error | `http UserError (400)` | `This is a user http test` |
| An HTTP validation error | `http ValidationError (400)` | `This is a validation http test` |
| An HTTP missing-record error | `http MissingError (400)` | `This is a missing http test` |
| An HTTP access error | `http AccessError (403)` | `This is an access http test` |
| An HTTP access-denied error | `http AccessDenied (403)` | `This is an access denied http test` |
| An HTTP internal-server error | `http InternalServerError (500)` | No explicit message is attached to this route. |
| An HTTP not-found error | `http NotFound (404)` | The error page displays `Page not found`. |
| An RPC user error | `rpc UserError` | `This is a user rpc test` |
| An RPC validation error | `rpc ValidationError` | `This is a validation rpc test` |
| An RPC missing-record error | `rpc MissingError` | `This is a missing rpc test` |
| An RPC access error | `rpc AccessError` | `This is an access rpc test` |
| An RPC access-denied error | `rpc AccessDenied` | `This is an access denied rpc test` |
| An RPC internal-server error | `rpc InternalServerError` | No explicit message is attached to this route. |

**Result:** You can match each error class with its message in the table. If the page shows
`Page not found`, continue with the route check below.

## When the error page cannot be reached

Use the `http NotFound (404)` row to identify the 404 page message.

1. Select an error link in the Error type column, then use the matching row:

   | If the page displays… | Read… |
   | --- | --- |
   | `Page not found` | The route path and `Error 404` |
   | Another error message | The matching message in the Message column |

**Result:** You can identify the error page from `Page not found` and `Error 404`, or match
another displayed message in the Message column. Continue to What to do next for broader help.

## What to do next

Use [Getting help](doc:getting-help) when you need help with an application issue. Use
[Common issues and solutions](doc:common-issues-and-solutions) when you need a broader
troubleshooting path.

The `Website test setting` belongs to website configuration rather than this reference.

**Result:** You have the matching error message and the next help page for the issue.