rsnext/errors/no-router-instance.mdx

---
title: No Router Instance
---

## Why This Error Occurred

During Pre-rendering (SSR or SSG) you tried to access a router method `push`, `replace`, `back`, which is not supported.

## Possible Ways to Fix It

In a function Component you can move the code into the `useEffect` hook.

In a class Component, move any calls to router methods to the `componentDidMount` lifecycle method.

This way the calls to the router methods are only executed in the browser.
docs: Migrate error messages to MDX and App Router. (#52038) This PR is part of a larger effort to migrate error messages to MDX and use App Router: https://github.com/vercel/front/pull/23459 2023-07-05 15:11:16 +02:00			`---`
			`title: No Router Instance`
			`---`
Throw error when router methods are used in SSR (#6550) * Update to use the correct router instance in withRouter so error is thrown when router method is used during SSR * Revert changes to with-router and add error to methods on direct router instance * Extend Router and override methods with error instead * Update ServerRouter, add err.sh, and add test 2019-03-07 17:13:38 +01:00
docs: Migrate error messages to MDX and App Router. (#52038) This PR is part of a larger effort to migrate error messages to MDX and use App Router: https://github.com/vercel/front/pull/23459 2023-07-05 15:11:16 +02:00			`## Why This Error Occurred`
Throw error when router methods are used in SSR (#6550) * Update to use the correct router instance in withRouter so error is thrown when router method is used during SSR * Revert changes to with-router and add error to methods on direct router instance * Extend Router and override methods with error instead * Update ServerRouter, add err.sh, and add test 2019-03-07 17:13:38 +01:00
expanded on No Router Instance (#21248) Added more detailed explanation of why there is no router instance, and other ways to fix the error 2021-01-26 11:27:53 +01:00			During Pre-rendering (SSR or SSG) you tried to access a router method `push`, `replace`, `back`, which is not supported.
Throw error when router methods are used in SSR (#6550) * Update to use the correct router instance in withRouter so error is thrown when router method is used during SSR * Revert changes to with-router and add error to methods on direct router instance * Extend Router and override methods with error instead * Update ServerRouter, add err.sh, and add test 2019-03-07 17:13:38 +01:00
docs: Migrate error messages to MDX and App Router. (#52038) This PR is part of a larger effort to migrate error messages to MDX and use App Router: https://github.com/vercel/front/pull/23459 2023-07-05 15:11:16 +02:00			`## Possible Ways to Fix It`
Throw error when router methods are used in SSR (#6550) * Update to use the correct router instance in withRouter so error is thrown when router method is used during SSR * Revert changes to with-router and add error to methods on direct router instance * Extend Router and override methods with error instead * Update ServerRouter, add err.sh, and add test 2019-03-07 17:13:38 +01:00
expanded on No Router Instance (#21248) Added more detailed explanation of why there is no router instance, and other ways to fix the error 2021-01-26 11:27:53 +01:00			In a function Component you can move the code into the `useEffect` hook.

			In a class Component, move any calls to router methods to the `componentDidMount` lifecycle method.

			`This way the calls to the router methods are only executed in the browser.`