vercel/next.js

--experimental-https does not work on the network url

FleetAdmiralJakob opened this issue · 0 comments

Link to the code that reproduces this issue

Works on ANY (canary too) Next.js app with any browser

To Reproduce

  1. Run a Next.js app in dev with --experimental-https
  2. Copy the network URL (e.g. 192.168.0.19:3000)
  3. Try to open it in the browser of your choice

Current behaviour: The site is considered insecure

Expected behaviour: HTTPS Certificate works for the network URL too

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:27 PDT 2024; root:xnu-11215.41.3~2/RELEASE_X86_64
  Available memory (MB): 8192
  Available CPU cores: 8
Binaries:
  Node: 20.18.0
  npm: 10.9.1
  Yarn: N/A
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.0 // Latest available version is detected (15.1.0).
  eslint-config-next: 15.1.0
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

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

Not sure

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

next dev (local)

Additional context

This feature is important when testing my app on my phone etc. as I use APIs like the Notifications API or the crypto API which otherwise don't work without HTTPS.

My current workaround is to use ngrok for testing dev builds on my other devices, which is not optimal.