Firebase serve error: Port 5000 is not open. Could not start functions emulator

Question

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 not open, could not start functions emulator."

I'm using Windows 10, so I've tried to change the port number, check if the port is blocked by Firewall and I create a new rule in Firewall to ports 5000-5010 but none of this approaches worked for me.

Have the same problem, on MacOS. Reverted to firebase-tools version 6.12.0 for now and that seems to work (although not a real solution to the problem). `npm i -g firebase-tools@6.12.0` — Iggy van Lith, Aug 17 '19 at 16:05
using firebase-tools@6.12.0 generated grpc related error in node module, the latest firebase-tools doesn't have this error. => reverting back to v6.12.0 did not work for me :( — Thr3e, Aug 17 '19 at 17:44
@Thr3e This happened to me, too. So, I installed the grpc module in functions folder and it worked again — Victor de Almeida, Aug 18 '19 at 18:57
In my case, I had `AirServer` running, which was using the `5001` port. So I closed it once I saw `publicmat`'s answer. — Ben Butterworth, Aug 04 '21 at 13:18

score 62 · Answer 1 · answered May 05 '20 at 05:06

62

For Mac/Linux, use the Terminal/Shell to find the Process ID (PID), then kill the process.

sudo lsof -i :5000
sudo kill -9 PID

answered May 05 '20 at 05:06

publicmat

781
5
6

27

`lsof -t -i tcp:5000 | xargs kill` - one line alternative that pipes the output of lsof to kill (h/t [@manav](https://stackoverflow.com/questions/3855127/find-and-kill-process-locking-port-3000-on-mac/3855359#3855359)) – warfield Aug 11 '20 at 18:02
27

If you are using macOS Monterey, the Airplay server now uses Port 5000 so you either need to change the port for your process or kill Airplay receiver in System Preferences > Sharing – Clive Townsend Nov 19 '21 at 15:50
1

@warfield lsof -t -i tcp:5000 | xargs kill didn't help :( – Liker777 Apr 23 '22 at 04:52

score 60 · Answer 2 · answered Nov 19 '21 at 08:45

60

In MacOS Monterey, port 5000 may be claimed by a new "AirPlay Receiver". This can be disabled in Settings -> Sharing:

Screenshot of settings panel for disabling AirPlay Receiver

Disabling the AirPlay Receiver (if you do not need it) frees up port 5000.

answered Nov 19 '21 at 08:45

ErikWittern

1,083
9
13

score 42 · Answer 3 · edited Apr 26 '22 at 05:33

42

Alternatively use a different port, it is a simple solution.

firebase serve -p 5001

edited Apr 26 '22 at 05:33

Gerry

1,159
1
14
29

answered Apr 24 '20 at 21:00

Ela

429
4
3

score 21 · Answer 4 · edited Sep 30 '20 at 16:55

21

For Windows Users:

netstat -ano|findstr "PID :5000"

And then with the Process ID (PID) found at the end of the line.

taskkill /pid FOUNDPID /F

Command taskkill does not work from within terminal of VS Code context. It needs an (elevated) CMD-prompt or equivalent Powershell environment in order to successfully terminate the listening on 127.0.0.1:5000.

edited Sep 30 '20 at 16:55

NearHuscarl

66,950
18
261
230

answered Aug 20 '20 at 23:20

Nestor Solalinde

563
4
15

score 15 · Answer 5 · answered Feb 13 '22 at 12:45

15

Port 5000 and 7000 are taken by airplay on MacOS Monterey.

Switch off Airplay Receiver as suggested here or

update firebase.json with a different port

"emulators": {
   
    "hosting": {
      "port": 5004
    }
}

answered Feb 13 '22 at 12:45

Venkat Kotra

10,413
3
49
53

score 14 · Answer 6 · edited Mar 10 '23 at 19:40

14

The thing here is your port No 5000 is running with some process. So, first, you need to kill that process.

Find process id in Ubuntu

sudo lsof -i :5000

Suppose you get PID 14541

Kill the process

sudo kill -9 14541

edited Mar 10 '23 at 19:40

Moritz Ringler

9,772
9
21
34

answered Jun 12 '20 at 12:29

alok kumar

317
3
11

score 13 · Answer 7 · edited Mar 10 '23 at 19:41

13

lsof -t -i tcp:5000 | xargs kill

A one-line alternative for Mac users that pipes the the process ID directly to kill. h/t @manav

Original question was for Windows, but might be useful for others as question is now ranked highly in search results.

edited Mar 10 '23 at 19:41

Moritz Ringler

9,772
9
21
34

answered Aug 11 '20 at 18:14

warfield

624
6
14

Wendigo · Answer 8 · 2019-08-19T10:39:46.123

4

A similiar problem has recently been reported in the official github repo: https://github.com/firebase/firebase-tools/issues/1606.

It is caused by a bug in a dependency (node portfinder), as you can see here. https://github.com/http-party/node-portfinder/pull/86

A quick fix to edit it might be to use the old version of node portfinder (v 1.0.21). Alternatively, you can do it by editing node_modules/firebase-tools/lib/emulator/controller.js and changing yield pf.getPortPromise({ port, stopPort: port }) to yield pf.getPortPromise({ port, stopPort: port + 1 }).

EDIT: As suggested by Mladen Skrbic, in order to find the firebase-tools folder, you should run npm root -g and find the firebase-tools folder in there.

This should fix the issue!

edited Aug 19 '19 at 10:39

answered Aug 18 '19 at 16:12

Wendigo

444
1
7
18

thank you it fixed my issue, i just want to say that npm root -g will tell you where to look – Mladen Skrbic Aug 19 '19 at 09:48
1

One line fix on OSX: `sed -i '' 's/stopPort: port/stopPort: port+1/' node_modules/firebase-tools/lib/emulator/controller.js` – Public Profile Aug 19 '19 at 10:21

score 4 · Answer 9 · answered Oct 29 '19 at 17:30

4

This worked for me.

Just restart your system.

answered Oct 29 '19 at 17:30

biggest_boy

381
4
23

2

Actually just restarting the code editor also worked fine, thanks though! – Fotios Tsakiris Feb 08 '20 at 10:03

score 4 · Answer 10 · edited Mar 10 '23 at 19:41

4

just run command

firebase serve --only functions --host 0.0.0.0

edited Mar 10 '23 at 19:41

Moritz Ringler

9,772
9
21
34

answered Jan 31 '20 at 06:18

Geetanshu Gulati

692
8
13

score 3 · Answer 11 · edited Mar 10 '23 at 19:42

3

Running this command did the trick for me:

firebase emulators:start --only firestore

also close this window:

edited Mar 10 '23 at 19:42

Moritz Ringler

9,772
9
21
34

answered Oct 23 '20 at 17:08

Itay Tur

683
1
15
40

score 3 · Answer 12 · edited Feb 10 '22 at 07:29

3

Try this way:

firebase serve --only functions -p 5002

edited Feb 10 '22 at 07:29

Syscall

19,327
10
37
52

answered Feb 10 '22 at 04:00

pa.duongdam

46
3

score 2 · Answer 13 · edited Mar 10 '23 at 19:42

2

Instead of latest firebase-functions(which is 3.2.0 currently), forcing it to stay at 3.0.2 solved in my case.

    "dependencies": {
        "firebase-admin": "^8.2.0",
        "firebase-functions": "3.0.2",
        ...
    }

(Also I am using firebase-tools version 7.0.2 atm, didnt check it with latest. If it doesnt work try reverting firebase-tools to 7.0.2)

edited Mar 10 '23 at 19:42

Moritz Ringler

9,772
9
21
34

answered Aug 17 '19 at 21:16

Mertcan Çüçen

466
3
13

1

Facing the problem in version 7.2.2 of firebase-tools, but working in version 7.0.2 as suggested (thanks) as well as latest version 7.2.4. – Bernardo Baumblatt Aug 22 '19 at 14:39
1

In any firebase-tools version, only works with firebase-functions 3.0.2. – Bernardo Baumblatt Aug 22 '19 at 15:07

score 2 · Answer 14 · edited Mar 10 '23 at 19:43

2

A quick fix

npm i -g firebase-tools@7.8.0

edited Mar 10 '23 at 19:43

Moritz Ringler

9,772
9
21
34

answered Nov 27 '19 at 18:17

jDev

21
4

score 2 · Answer 15 · answered Feb 09 '22 at 14:35

macOS Monterey 12.2 user here. I've simply changed the port to 5005 and it worked like a charm.

{
  "hosting": {
    "public": "functions/browser",
    "ignore": [
      "firebase.json",
      "**/.*",
      "**/node_modules/**"
    ],
    "rewrites": [
      {
        "source": "**",
        "function": "ssrapp"
      }
    ]
  },
  "emulators": {
    "hosting": {
      "port": "5005"
    }
  }
}

score 1 · Answer 16 · edited Mar 10 '23 at 19:45

SOLUTION TO:

Firebase serve error: Port 5000 is not open. Could not start functions emulator

If you get one of the following error messages when you run Firebase, you can easily resolve the problem by switching to another version of Firebase tools.

If you are using version 6 of Firebase Tools, you might switch to latest version (6.12.0), or you might try v7.2.2. To change to Firebase Tools version run to following node package manager command:

npm install -g firebase-tools@6.12.0

score 0 · Answer 17 · answered Jan 26 '21 at 10:11

0

If firebase serve --host 127.0.0.1 solves it for you; maybe you haven't set up your hosts file. Linux - Network configuration

answered Jan 26 '21 at 10:11

medo

66
6

score 0 · Answer 18 · edited Mar 10 '23 at 19:49

0

I faced the same issue not quite long ago.

I found out I had firebase running on another terminal on my computer.

So before you try firebase serve, check if it is running on another terminal.

I hope it solves your problem just like mine.

edited Mar 10 '23 at 19:49

Moritz Ringler

9,772
9
21
34

answered Aug 03 '21 at 13:18

Jay Stance

11
2

score 0 · Answer 19 · edited Mar 10 '23 at 19:46

0

first, close all tab restart VS code then just go in firebase.json file then change ui port number then start again, it will work!

    "ui": {
      "enabled": true,
      "port": "enter any number"
    }

edited Mar 10 '23 at 19:46

Moritz Ringler

9,772
9
21
34

answered Sep 18 '21 at 15:51

Sanjeev Gupta

1

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-ask). – Community Sep 18 '21 at 17:39

score 0 · Answer 20 · edited Dec 03 '21 at 05:47

0

As suggested here https://github.com/firebase/firebase-tools/issues/2856#issuecomment-902411134

Upgrading Node.js is working.

I just upgraded Node to 14.17.5. This solves the problem. I just press Ctrl+C to stop all emulators.

edited Dec 03 '21 at 05:47

karel

5,489
46
45
50

answered Oct 31 '21 at 18:18

preetk

189
4
12

score 0 · Answer 21 · answered Feb 05 '22 at 05:16

0

close everything, delete your "prefetch" and "%temp%" in "run" option and restart your PC. that worked for me

answered Feb 05 '22 at 05:16

A K M ALI HASAN

1
1
2

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Feb 05 '22 at 05:39

score 0 · Answer 22 · edited Mar 10 '23 at 19:47

{
  "firestore": {
    "rules": "firestore.rules",
    "indexes": "firestore.indexes.json"
  },
  "functions": {
    "source": "functions"
  },
  "hosting": {
    "public": "public",
    "ignore": [
      "firebase.json",
      "**/.*",
      "**/node_modules/**"
    ]
  },
  "emulators": {
    "auth": {
      "port": 9099
    },
    "functions": {
      "port": 5001
    },
    "firestore": {
      "port": 8080
    },
    "hosting": {
      "port": 5005
    }
  }
}

I'm using macOS Monterey 12.6 , I just changed the hosting port to "5005" , and it's working fine to me

score 0 · Answer 23 · answered Aug 07 '23 at 20:14

0

firebase serve --only functions --port

answered Aug 07 '23 at 20:14

Adilson Cruz

1

score -1 · Answer 24 · answered Aug 26 '22 at 09:32

-1

For me, it wasn't working when a VPN was on.

answered Aug 26 '22 at 09:32

DamjanDabo

97
3

Firebase serve error: Port 5000 is not open. Could not start functions emulator

24 Answers24

Linked