error: Error: listen EADDRINUSE: address already in use 0.0.0.0:4567

[phenomlab]

@nodebbcomcast this would indicate that the address and port are in use. Do you have other applications or services running ?

[gotwf]

@nodebbcomcast

0.0.0.0 is the shorthand for all interfaces. You should restrict that to only those required, most likely a localhost address, e.g. 127.0.0.1

4567 is the "port" NodeBB is knocking on, which, for reasons unknown is already in use. There are more modern commands but kicking it old school, you can drive this one:

# netstat -na | grep  4567
tcp        0      0 127.0.0.1:4567          0.0.0.0:*               LISTEN  

The result above indicates something using tcp on the localhost interface 127.0.0.1 using port 4567. In this instance, NodeBB

Should you get any return for grepping on port 4567 and NodeBB is not running, your next step is to find out what is, wh/I will leave as an exercise.

Good luck and have fun!

[nodebbvenkata]

got in to new problem after launch please the screenshot. I am getting admin blocked for some reason.

Here is my deployemnt.yaml file

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nodebb-deployment
spec:
  selector:
    matchLabels:
      app: nodebb
  replicas: 1 # tells deployment to run 2 pods matching the template
  template:
    metadata:
      labels:
        app: nodebb
    spec:
      containers:
      - name: nodebb
        image: nodebb/docker:latest
        ports:
        - containerPort: 4567
--- 

apiVersion: v1
kind: Service
metadata:
  name: nodebb-service
spec:
  selector:
    app: nodebb
  ports:
    - protocol: TCP
      port: 80
      targetPort: 4567
```\

[phenomlab]

@nodebbvenkata do you have an ad or script blocker plugin in your browser that's active ?

[nodebbvenkata]

@phenomlab no I have nothing installed I even tried on a different browser.

[nodebbvenkata]

@phenomlab This blocked issue got resolved by adding https on the installation url while registering. Then new problem is socket url is giving 404.

[miguelmoreno]

@nodebbvenkata Hi, could you elaborate on how the issue got resolved for you? I have a very similar setup to the one you have (kubernetes service + deployment) and I'm experiencing the same behaviour:

2023-03-20T15:31:29.934Z [4567/228] - error: NodeBB address in use, exiting...
Error: listen EADDRINUSE: address already in use 0.0.0.0:4567
    at Server.setupListenHandle [as _listen2] (node:net:1740:16)
    at listenInCluster (node:net:1788:12)
    at doListen (node:net:1937:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
2023-03-20T15:31:29.936Z [4567/228] - error: uncaughtException: listen EADDRINUSE: address already in use 0.0.0.0:4567
Error: listen EADDRINUSE: address already in use 0.0.0.0:4567

[phenomlab]

@miguelmoreno That looks very much like you already have an instance of NodeBB running.

[Byungmin Kim]

I'm having the same problem as @nodebbvenkata
@phenomlab It seems to happen at the time of ‘trust proxy’, is there any workaround?
I share the logs below.

2024-08-16T10:46:59.145Z [4567/136] - info: [api] Adding 0 route(s) to api/v3/plugins
2024-08-16T10:46:59.169Z [4567/136] - info: [router] Routes added
2024-08-16T10:46:59.183Z [4567/136] - info: NodeBB Ready
2024-08-16T10:46:59.184Z [4567/136] - info: Enabling 'trust proxy'
2024-08-16T10:46:59.188Z [4567/136] - error: NodeBB address in use, exiting...
Error: listen EADDRINUSE: address already in use 0.0.0.0:4567
at Server.setupListenHandle [as _listen2] (node:net:1751:16)
at listenInCluster (node:net:1799:12)
at doListen (node:net:1948:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

[phenomlab]

@Byungmin-Kim this would indicate that port 4567 is already being used elsewhere. Do you have any existing nodebb processes currently running?

What is the output of

ps aux | grep nodebb