next serve --hostname option is broken in 12.4.15

[EmilioAiolfi]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.17.1
      npm: 9.6.7
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.15
      eslint-config-next: 13.4.16
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue or a replay of the bug

https://github.com/EmilioAiolfi/test-hostname

To Reproduce

Add --hostname option to run next serve

Describe the Bug

next dev --port 3001 --hostname local.mydomain.com.br

Dont work and not return

- ready started server on local.mydomain.com:3001, url: http://local.mydomain.com:3001

but return

- ready started server on 127.0.0.1:3001, url: http://127.0.0.1:3001

Expected Behavior

next dev --port 3001 --hostname local.mydomain.com.br

- ready started server on local.mydomain.com:3001 , url: http://local.mydomain.com:3001

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[Rieranthony]

I've got the same issue, this is preventing me from upgrading to the latest next versions.

This option is super useful for multi tenant apps using wildcard subdomains

[Rieranthony]

I can confirm this is fixed in v13.4.20-canary.33!

Thanks for pushing that forward

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!