Remix shows a route's ErrorBoundary in place of the route whenever its component, its loader (which fetches data) or its action (which handles form posts) throws. If you see the error boundary, or the root one if a route has none, the cause is usually in that route's loader or action: a failed database or API call. Those run on the server, so the full error is in your server logs.
What's the problem
A page shows your error boundary or a generic error, a form post fails, or the app returns 500s.
Why it happens
- A loader failed: a database or API call threw.
- An action failed while handling a form.
- A component threw while rendering.
- Intentionally thrown responses, such as 404s for missing records, landing in a boundary that doesn't handle them.
- Missing environment variables in production.
How to fix it
- Check which route's boundary showed.
- Read the server logs for the loader or action error.
- Add an
ErrorBoundaryto important routes so errors stay contained. - Handle expected cases (not found, unauthorised) by throwing responses and showing them clearly.
- Check environment variables in production.
What Preventionlabs checks
One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. With Cloudflare connected, it also shows which pages returned server errors (5xx) to visitors, and when; recent deploys and account changes, with their times. It doesn't read your server logs, so the exact error message is in your host's logs.
Run your free reportYour first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.
Sources
- Remix: ErrorBoundaryofficial docs
When there is an error in your route component, the ErrorBoundary will be rendered in its place, nested inside any parent routes.
- Remix: ErrorBoundaryofficial docs
ErrorBoundary components also render when there is an error in the loader or action functions for a route, so all errors for that route may be handled in one spot.
Preventionlabs is independent and not affiliated with Remix. Product names are used only to describe the problem.
← All of Frameworks