Repository: create-react-app
Issue: Localhost Refused to Connect
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

Localhost refuses to connect after creating a fresh react application and running `npm start`. I first used `npx create-react-app appname`. 

### Did you try recovering your dependencies?
Yes, no effect.

<!--
  Your module tree might be corrupted, and that might be causing the issues.
  Let's try to recover it. First, delete these files and folders in your project:

    * node_modules
    * package-lock.json
    * yarn.lock

  Then you need to decide which package manager you prefer to use.
  We support both npm (https://npmjs.com) and yarn (http://yarnpkg.com/).
  However, **they can't be used together in one project** so you need to pick one.

  If you decided to use npm, run this in your project directory:

    npm install -g npm@latest
    npm install

  This should fix your project.

  If you decided to use yarn, update it first (https://yarnpkg.com/en/docs/install).
  Then run in your project directory:

    yarn

  This should fix your project.

  Importantly, **if you decided to use yarn, you should never run `npm install` in the project**.
  For example, yarn users should run `yarn add <library>` instead of `npm install <library>`.
  Otherwise your project will break again.

  Have you done all these steps and still see the issue?
  Please paste the output of `npm --version` and/or `yarn --version` to confirm.
-->

`npm --version` 6.14.11

### Which terms did you search for in User Guide?

<!--
  There are a few common documented problems, such as watcher not detecting changes, or build failing.
  They are described in the Troubleshooting section of the User Guide:

  https://facebook.github.io/create-react-app/docs/troubleshooting

  Please scan these few sections for common problems.
  Additionally, you can search the User Guide itself for something you're having issues with:

  https://facebook.github.io/create-react-app/

  If you didn't find the solution, please share which words you searched for.
  This helps us improve documentation for future readers who might encounter the same problem.
-->

Followed instructions from https://create-react-app.dev/docs/getting-started/.
This didn't help https://stackoverflow.com/questions/39959900/npm-start-error-with-create-react-app
Searched "failed at start react app".

### Environment

<!--
  To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
  This enables the maintainers quickly reproduce the issue and give feedback.

  Run the following command in your React app's folder in terminal.
  Note: The result is copied to your clipboard directly.

  `npx create-react-app --info`

  Paste the output of the command in the section below.
-->
```
  current version of create-react-app: 4.0.1
  running from /Users/alexis/.nvm/versions/node/v14.15.4/lib/node_modules/create-react-app

  System:
    OS: macOS 11.1
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: Not Found
    npm: 6.14.11 - ~/.nvm/versions/node/v14.15.4/bin/npm
  Browsers:
    Chrome: 88.0.4324.96
    Edge: Not Found
    Firefox: Not Found
    Safari: 14.0.2
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.1 => 4.0.1 
  npmGlobalPackages:
    create-react-app: 4.0.1
```

### Steps to reproduce

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
-->

(Write your steps here:)

1. run `npx create-react-app portfolio`
2. `cd portfolio`
3. `npm start`

### Expected behavior

<!--
  How did you expect the tool to behave?
  It’s fine if you’re not sure your understanding is correct.
  Just write down what you thought would happen.
-->

I expected to see the starting template for a react application.

### Actual behavior

<!--
  Did something go wrong?
  Is something broken, or not behaving as you expected?
  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->

Chrome opened to local host with could not connect to localhost. 

Debug Log:
```0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/Users/alexis/.nvm/versions/node/v14.15.4/bin/node',
1 verbose cli   '/Users/alexis/.nvm/versions/node/v14.15.4/bin/npm',
1 verbose cli   'start'
1 verbose cli ]
2 info using npm@6.14.11
3 info using node@v14.15.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle portfolio@0.1.0~prestart: portfolio@0.1.0
6 info lifecycle portfolio@0.1.0~start: portfolio@0.1.0
7 verbose lifecycle portfolio@0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle portfolio@0.1.0~start: PATH: /Users/alexis/.nvm/versions/node/v14.15.4/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/alexis/projects/portfolio/node_modules/.bin:/Users/alexis/.nvm/versions/node/v14.15.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/alexis/.nvm/versions/node/v14.15.4/bin:/opt/homebrew/bin:/Users/alexis/Library/Python/3.8/bin:/opt/homebrew/bin:/Users/alexis/Library/Python/3.8/bin
9 verbose lifecycle portfolio@0.1.0~start: CWD: /Users/alexis/projects/portfolio
10 silly lifecycle portfolio@0.1.0~start: Args: [ '-c', 'react-scripts start' ]
11 silly lifecycle portfolio@0.1.0~start: Returned: code: 1  signal: null
12 info lifecycle portfolio@0.1.0~start: Failed to exec start script
13 verbose stack Error: portfolio@0.1.0 start: `react-scripts start`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/Users/alexis/.nvm/versions/node/v14.15.4/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (/Users/alexis/.nvm/versions/node/v14.15.4/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1048:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid portfolio@0.1.0
15 verbose cwd /Users/alexis/projects/portfolio
16 verbose Darwin 20.2.0
17 verbose argv "/Users/alexis/.nvm/versions/node/v14.15.4/bin/node" "/Users/alexis/.nvm/versions/node/v14.15.4/bin/npm" "start"
18 verbose node v14.15.4
19 verbose npm  v6.14.11
20 error code ELIFECYCLE
21 error errno 1
22 error portfolio@0.1.0 start: `react-scripts start`
22 error Exit status 1
23 error Failed at the portfolio@0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
```

I'm using a new Macbook Air running macOS Big Sur version 11.1.