Gunbot error bind EADDRINUSE null


GUNBOT Error bind EADDRINUSE null:5001 – is a common Gunbot error and can easily easily be fixed by following the solutions below, to perform a system restart or to check for and kill Gunthy process.

Gunbot Error bind EADDRINUSE null LOG

Loading config…
{ Error: bind EADDRINUSE null:5001
at Object._errnoException (util.js:992:11)
at _exceptionWithHostPort (util.js:1014:20)
at listenOnMasterHandle (net.js:1415:16)
at rr (internal/cluster/child.js:121:12)
at Worker.send (internal/cluster/child.js:88:7)
at process.onInternalMessage (internal/cluster/utils.js:42:8)
at emitTwo (events.js:131:20)
at process.emit (events.js:214:7)
at emit (internal/child_process.js:772:12)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
errno: ‘EADDRINUSE’,
syscall: ‘bind’,
address: null,
port: 5001 } ‘Uncaught Exception thrown’

Gunbot Error bind EADDRINUSE Cause

Error: bind EADDRINUSE null usually indicates you are trying to run two Gunbot instances or that port is in use by another application, resulting in Gunbot / Gunthy GUI display this error when attempting to Launch.

Gunbot Error bind EADDRINUSE FAQ

  1. But I checked and there isn’t another Gunbot instance running, so why is this error showing?
    If you have checked and there is not another Gunbot / Gunthy GUI instance running then it’s possible there is another program using the port or a firewall blocking the port (unlikely if it was running before.)
  2. What if I want to run more than one instance of Gunbot?
    In order to run more than one Gunbot on a computer withotu seeing this error, you will need to adjust your config for the second Gunbot instance (so that both Gunbot copies don’t try to access the same port, causing the bind EADDRINUSE erorr.
  3. I am having problem changing port on linux VPS… Tried changing the port to 9000 in config.js and also tried the .BAT file.. But when i tried to run ./gunthy-gui it still says error: listen EADDRINUSE :5000
    Try rebooting the compter or VPS, If that doesn’t work, try force closing the existing Gunbot  instance or conflicting program (program already using port 5000) or as a last resort uninstalling any conflicting program (if not Gunbot) then once Gunbot is running re-install the conflicting program with a different port. Sometimes programs stuck in the memory don’t wanna give up space taken. 🙂


  1. Try rebooting the computer or VPS. If it’s a VPS: login to the dashboard, find your VPS instance, access the VPS control panel / dashboard and click “Reboot”. For a linux VPS you can also use root user or sudo command to reboot vps through terminal ssh connection using command “sudo reboot”.
  2. For Linux system use a task manager application or terminal command “ps” to check existing processes and see if gunthy process is running, then write down the pid and use in command “sudo kill pid_#.
  3. For Windows system use: click start menu, type CMD (command window), type in Command “netstat -a” which will show all ports open to see what ports are being used, you can go to task manager to check for Gunbot / Gunthy GUI process and kill gunthy process as well.
  4. As a last resort (or if trying to run more than one Gunbot instance, change websockets ports in Gunbot config.js file.

Has this article helped you?
Please leave a review and make your next Gunbot purchase or upgrade on
Visit Communities! Reddit: Discord:

Thank you for visiting Gunbot.Website

Leave a Comment

Your email address will not be published. Required fields are marked *