@José-Ángel-Rey-Liñares said:
@julian thanks for your reply. Yes I know. But i checked and there isn't another instance of nodebb running on 4567 or another app, the port is not in use. In fact i can run (not debug) nodebb without any problem from the IDE using port 4567, or using ./nodebb script in a shell.
After some searching on google, seem that it might be related to some issues since node.js 11 (i'm using node 12.0.3). So i was wondering if anyone around here faced the same problem.
Thanks!
PS: 4 hours trying to get this to work on webstorm, but i'm not able to make it debug. Always getting EADDRINUSE. Anyone using webstorm?
it happens sometimes...
ps aux | grep node
kill -9 process_id
@exodo said:
ps aux | grep node
Hi! Thanks for your reply. I've checked again the port usage according your suggestion and before running the webstorm debugger, 0 node instances are running.
After i run the debugger and obtain the EADDRINUSE error, 2 node processes appear:
jose 3147 73.3 4.6 1768556 178156 ? Sl 19:58 0:52 /usr/bin/node --debug-brk=49749 --nolazy --debug app.js
jose 3185 1.1 0.5 686968 19812 ? Sl 19:59 0:00 /usr/bin/nodejs --debug-brk=49749 --nolazy --debug minifier.js
If i kill, in this example pids 3147 and 3185 and run the debugger again, same result. Always obtaining the mentioned EADDRINUSE.
As i said, i can run nodebb without any problem from webstorm, without debugging.
Thanks for your time.
EDIT: I've tried with a simple node.js/express/mongo app, (https://github.com/ijason/NodeJS-Sample-App) and i can debg it without a problem. Could it be something related with nodebb? Does anyone debug nodebb with webstorm succesfully? @3rd-Party-Developers ?
Looks like webstorm is starting two node processes.
Old but could be relevant.
@a_5mith @pitaj thanks for your replies. In fact i found a very similar issue on the webstorm issues: https://youtrack.jetbrains.com/issue/WEB-15470
I think this case is very similar to the one i'm facing. I'm trying to reproduce the error on console, and even i'm not able to, i would swear that i have seen the same error on console yesterday :S.
yeah im having the same EADDRINUSE error when trying to run NodBB in debugger mode (WebStorm)
Could be possible to disable the minifier process during the startup of the debbugger? I suppose is started from nodebb engine, isn't it?
I'm referring to this process: /usr/bin/nodejs --debug-brk=49749 --nolazy --debug minifier.js
I would love a solution or a workaround because I've been trying for a couple days to try and get this working. I just want to be able to debug NodeBB's plugins and core components 
PS. I've tried WebStorm, node-inspector and strong-cli. I've tried them all with latest node.js and also version 0.10
@agarcia17 do you get the EADRRINUSE with all of them?
@José-Ángel-Rey-Liñares yeah same error with all of them
Anyone could provide any details, guides or something related to debug node.js applications using mentioned tools or different ones? What about expecifically nodebb? How do you debug your plugins/nodebb developments? Do you only use logs or use another kind of tools?
Thanks in advance.
I'm using PHPStorm/Intellij Ultimate and the only way it seems to work for me (on Windows, can't remember if it worked on OS X) is to use a remote Node.js debugging session. If I don't do this, it get's stuck on the minifier stage.
Here is my run configuration and there is my remote debug configuration. These are configurations in a plugin project so this only allows your to debug your project files. To debug NodeBB modules you have to run/debug from the NodeBB project.
After that you just run the Run configuration and debug the remote debug configuration when needed.
FYI: Visual Studio Code worked with debugging right out of the box.
@Schamper thanks you very much! I would give a try to the remote debugging on webstorm. And could try the Visual Studio approach too. Thanks again!
@José-Ángel-Rey-Liñares note that only Visual Studio Code works right out of the box, Visual Studio itself does not.
@Schamper I have just tried Visual Studio Code, and i keep getting the same error EADDERINUSE. Could you tell me what version of node are you running? Thanks!
@José-Ángel-Rey-Liñares I was getting the same error with the master version of NodeBB then I tried a fresh install of NodeBB 0.7.x and got it working without changing any settings
PS. I'm using Visual Studio Code 0.3.0
@agarcia17 thanks, will give it a try. 
@agarcia17 i've just tried with visual studio code 0.3.0 and nodebb master on commit 96526a37a3cd64a866f3fc14a71cc327234d9a7d. And i'm getting the same EADDERINUSE; maybe could you point something I miss?
I've been struggling with this all day and no luck.
Even when I run from the command line I still get the error:
@Fidelix same here.
Imgur
