No error when port is already in use in (macOS)

[frandiox]

Describe the bug

Vite normally starts the server in the next available port when the default one is already in use. However, this seems to fail in some circumstances when running on a Mac (intel, at least).

Reported originally in Shopify/hydrogen#155

Reproduction

Run node -e 'require("http").createServer(function (req, res) {}).listen(3000);' in a terminal and then start any Vite server in the same port. Vite will show the port is 3000 instead of the expected 3001 but it won't be able to serve anything.

This, but run in on on macOS: https://stackblitz.com/edit/vitejs-vite-yhqcxn?file=package.json

System Info

System:
    OS: macOS 12.0.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 5.91 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.5.0 - /opt/dev/sh/nvm/versions/node/v16.5.0/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 7.19.1 - /opt/dev/sh/nvm/versions/node/v16.5.0/bin/npm
    Watchman: 2021.10.18.00 - /usr/local/bin/watchman
  Browsers:
    Chrome: 95.0.4638.69
    Safari: 15.1

Used Package Manager

yarn

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https:/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[haoqunjiang]

Could you check if it's a duplicate of #5241 (comment)?

[frandiox]

@sodatea Thanks! It looks indeed similar to what you describe in that comment. It works on 127.0.0.1:3000. Closing this as you are already tracking it there 👍