"Error: Port 5000 is not open, could not start functions emulator" when `npm run serve`
See original GitHub issue[REQUIRED] Environment info
node: 12.8.0 npm: 6.10.3
firebase-tools: 7.2.2
Platform: macOS
[REQUIRED] Test case
look step below
[REQUIRED] Steps to reproduce
run npm run serve
command
[REQUIRED] Expected behavior
Run simulator cloud functions successfully
[REQUIRED] Actual behavior
[2019-08-18T02:34:58.696Z] ----------------------------------------------------------------------
[2019-08-18T02:34:58.704Z] Command: /usr/local/Cellar/node/12.8.0/bin/node /usr/local/bin/firebase serve --only functions --debug
[2019-08-18T02:34:58.706Z] CLI Version: 7.2.2
[2019-08-18T02:34:58.706Z] Platform: darwin
[2019-08-18T02:34:58.706Z] Node Version: v12.8.0
[2019-08-18T02:34:58.707Z] Time: Sun Aug 18 2019 09:34:58 GMT+0700 (Indochina Time)
[2019-08-18T02:34:58.707Z] ----------------------------------------------------------------------
[2019-08-18T02:34:58.714Z] > command requires scopes: ["email","openid","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]
[2019-08-18T02:34:58.715Z] > authorizing via signed-in user
[2019-08-18T02:34:58.715Z] [iam] checking project jrt-shop-fc0f1 for permissions ["firebase.projects.get"]
[2019-08-18T02:34:58.717Z] >>> HTTP REQUEST POST https://cloudresourcemanager.googleapis.com/v1/projects/jrt-shop-fc0f1:testIamPermissions
permissions=[firebase.projects.get]
[2019-08-18T02:35:00.198Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Sun, 18 Aug 2019 02:35:02 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, server-timing=gfet4t7; dur=1140, alt-svc=quic=":443"; ma=2592000; v="46,43,39", accept-ranges=none, transfer-encoding=chunked
[2019-08-18T02:35:00.207Z] >>> HTTP REQUEST GET https://firebase.googleapis.com/v1beta1/projects/jrt-shop-fc0f1
[2019-08-18T02:35:00.720Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Sun, 18 Aug 2019 02:35:03 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="46,43,39", accept-ranges=none, transfer-encoding=chunked
Error: Port 5000 is not open, could not start functions emulator.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Firebase serve error: Port 5000 is not open. Could not start ...
first, close all tab restart VS code then just go in firebase.json file then change ui port ...
Read more >[Solved] Port 5000 is not open, could not start functions emulator
Firebase is a backend platform to build web, mobile apps. If you get the following error message "Port 5000 is not open, could...
Read more >Javascript – Firebase serve error: Port 5000 is not open. Could ...
I'm trying to serve firebase functions locally, but when I run firebase serve or firebase emulators:start the error message is: "Port 5000 is...
Read more >Could not start Functions Emulator, port taken Code Example
Port 5000 is not open on localhost, could not start functions emulator. Error: Port 5001 is not open on localhost, could not start...
Read more >Firebase serve error: Port 5000 is not open. Could not start ...
I'm trying to serve firebase functions locally, but when I run firebase serve or firebase emulators:start the error message is: "Port 5000 is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
this is fixed in
firebase-tools@7.2.3
for a quick fix see https://github.com/firebase/firebase-tools/issues/1606#issuecomment-522305234