Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #3719
Closed
Open
Issue created Jan 09, 2018 by Administrator@rootContributor

Inform user they've specified a HOST

Created by: everdrone

OS

macOS 10.13.2

Node

node -v: 9.3.0 npm -v: 5.6.0 yarn -v: 1.3.2

output:

$ yarn start                                                                                                                                                                                       06:51:09
yarn run v1.3.2
warning ../../../package.json: No license field
$ react-scripts start
Could not find an open port at Giorgios-MacBook-Pro.
Network error message: listen EADDRNOTAVAIL 54.72.52.58

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

rebooted many times, updated node and npm, updated yarn and create-react-app, but this only seems to works with sudo.

i also tried to reinstall node with nvm, after stumbling against many reports that suggested this was the cause of my issue.

this is probably a stupid bug, but it's driving me crazy since yesterday, please help.

Assignee
Assign to
Time tracking