nextjs - 💡(How to fix) Fix Getting pushed back to previous page when trying to access a few pages. [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#88465Fetched 2026-04-08 02:04:50
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×3closed ×1commented ×1issue_type_added ×1

Code Example

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Thu Dec 18 22:18:24 UTC 2025
  Available memory (MB): 15867
  Available CPU cores: 4
Binaries:
  Node: 24.11.0
  npm: 11.6.1
  Yarn: 1.22.22
  pnpm: 10.15.0
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

apology: github url can't be given, due to it's a private repo of our organization

To Reproduce

  1. Start the application (requires authentication)
  2. Trying to visit /page-1, /page-2, /page-3, /page-4 from the home page ("/") or any other page
  3. It pushes me back to the previous route before or after page mounts and all API calls (Server Actions server + client) have been finished.
  4. After several attempt it sometimes keeps me on the page, sometimes not.
  5. I am using Next.js v16.1.1
  6. Turbopack, React Compiler True (Though turn it off, doesn't solve the issue), proxy (middleware)

Current vs. Expected behavior

Current behavior:

  • Push me back to the previous route always
  • It only works when I downgrade the Next.js version to 15, but it reduces the performance of the entire application as well.

Expected behavior:

  • Seamless routing, without interrupting the pushing back routing issue.
  • It should be worked in the latest Next.js version.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Thu Dec 18 22:18:24 UTC 2025
  Available memory (MB): 15867
  Available CPU cores: 4
Binaries:
  Node: 24.11.0
  npm: 11.6.1
  Yarn: 1.22.22
  pnpm: 10.15.0
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Webpack, Turbopack

Which stage(s) are affected? (Select all that apply)

next build (local), next dev (local), next start (local), Other (Deployed)

Additional context

I tested the issue in both the development environment and production. It remains the same.

NB: We've deployed our application in a self-hosted environment.

extent analysis

TL;DR

Downgrade Next.js to version 15 as a temporary workaround to resolve the routing issue.

Guidance

  • Verify the issue by testing the routing on different pages (/page-1, /page-2, etc.) and observe if the problem persists.
  • Check the Next.js documentation and release notes for version 16.1.1 to see if there are any known issues or breaking changes related to routing.
  • Test the application with Turbopack and React Compiler disabled to isolate if the issue is related to these features.
  • Consider opening an issue on the Next.js GitHub repository to report the problem and get assistance from the maintainers.

Notes

The provided information suggests that the issue is related to Next.js version 16.1.1, as downgrading to version 15 resolves the problem. However, this workaround reduces the application's performance.

Recommendation

Apply workaround: Downgrade Next.js to version 15, as it is the only known solution to resolve the routing issue, despite the performance reduction.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING