Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Proxy does not work on Windows 11 in Next.js 16 when running next start [14 comments, 13 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#85243•Fetched 2026-04-08 02:16:51
View on GitHub
Comments
14
Participants
13
Timeline
34
Reactions
11
Author
resulggresulgg
Participants
DarkstarXDDDarkstarXDDdilwalashakibdilwalashakibgithub-actions[bot]github-actions[bot]icyJosephicyJosephMonkarekMonkarekRaenonXRaenonXresulggresulggrmstsdrmstsdsergev-magnetsusasergev-magnetsusatoakiryutoakiryutomx-shtomx-shVyldaVyldayzhe554yzhe554
Timeline (top)
commented ×14subscribed ×11labeled ×3closed ×1

Fix Action

Fix / Workaround

Workaround / Additional Observation:

Code Example

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32682
  Available CPU cores: 24
Binaries:
  Node: 22.15.0
  npm: 10.2.1
  Yarn: 1.22.22
  pnpm: 10.15.0
Relevant Packages:
  next: 16.0.0 // Latest available version is detected (16.0.0).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/resulgg/nextjs-proxy-bug.git

To Reproduce

  1. Create a fresh Next.js 16 project.
  2. Create a proxy.ts file.
  3. Run next build && next start on Windows 11.

Workaround / Additional Observation:

Renaming proxy.ts to middleware.ts makes it work.

Current vs. Expected behavior

On Windows 11, the proxy in Next.js 16 does not work when running next start. This happens even in a completely fresh project.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32682
  Available CPU cores: 24
Binaries:
  Node: 22.15.0
  npm: 10.2.1
  Yarn: 1.22.22
  pnpm: 10.15.0
Relevant Packages:
  next: 16.0.0 // Latest available version is detected (16.0.0).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Middleware

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

next start (local)

Additional context

No response

extent analysis

TL;DR

Renaming the proxy.ts file to middleware.ts may resolve the issue with Next.js 16 proxy not working on Windows 11.

Guidance

  • Verify that the issue is specific to the file name proxy.ts by attempting to rename it to middleware.ts as suggested in the workaround.
  • Check the Next.js documentation for any specific requirements or restrictions on file names for middleware and proxy configurations.
  • Test the application with the renamed file to confirm if the issue is resolved.
  • If the issue persists, investigate any potential conflicts with other middleware or proxy configurations in the project.

Example

No specific code example is provided as the issue seems to be related to file naming conventions rather than code syntax.

Notes

The provided workaround suggests a potential issue with file naming conventions in Next.js 16 on Windows 11. However, without further information or documentation from Next.js, it's uncertain if this is a bug or an intended behavior.

Recommendation

Apply the workaround by renaming proxy.ts to middleware.ts, as it has been observed to resolve the issue in the provided test case.

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…
#api#ssr#installation#tensor shape#autograd error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Proxy does not work on Windows 11 in Next.js 16 when running next start [14 comments, 13 participants]