Notification server says ports are in use, when they aren't

i’m trying to set up notifications on my phabricator server, but when I try to run it, i get Error: listen EADDRINUSE: address already in use 127.0.0.1:22281. These ports are definitely not already in use so i have no idea what’s going on. has anyone had this before?
thanks,
- ben

logs n’ stuff

aphlict logs:

[10/7/2020, 7:57:14 PM] Configuration test OK.
[10/7/2020, 7:57:14 PM] Starting servers (service PID 49095).
[10/7/2020, 7:57:14 PM] Logging to "/var/www/ph/phabricator/conf/aphlict/log.log".
[10/7/2020, 7:57:14 PM] Started client server (Port 22280, With SSL).
[10/7/2020, 7:57:14 PM] Started admin server (Port 22281, With SSL).
[10/7/2020, 7:57:14 PM] This server has fingerprint "8XprmLhaqvPssT8E".
[10/7/2020, 7:57:14 PM] 
<<< UNCAUGHT EXCEPTION! >>>

Error: listen EADDRINUSE: address already in use 0.0.0.0:22280
    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
    at listenInCluster (net.js:1328:12)
    at doListen (net.js:1461:7)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
[10/7/2020, 7:57:14 PM] 
<<< UNCAUGHT EXCEPTION! >>>

Error: listen EADDRINUSE: address already in use 127.0.0.1:22281
    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
    at listenInCluster (net.js:1328:12)
    at doListen (net.js:1461:7)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)

aphlict config:

{
  "servers": [
    {
      "type": "client",
      "port": 22280,
      "listen": "0.0.0.0",
      "ssl.key": "/etc/letsencrypt/live/phabricator.[[REDACTED]]/privkey.pem",
      "ssl.cert": "/etc/letsencrypt/live/phabricator.[[REDACTED]]/cert.pem",
      "ssl.chain": "/etc/letsencrypt/live/phabricator.[[REDACTED]]/chain.pem"
    },
    {
      "type": "admin",
      "port": 22281,
      "listen": "127.0.0.1",
      "ssl.key": "/etc/letsencrypt/live/phabricator.[[REDACTED]]/privkey.pem",
      "ssl.cert": "/etc/letsencrypt/live/phabricator.[[REDACTED]]/cert.pem",
      "ssl.chain": "/etc/letsencrypt/live/phabricator.[[REDACTED]]/chain.pem"
    }
  ],
  "logs": [
    {
      "path": "/var/www/ph/phabricator/conf/aphlict/log.log"
    }
  ],
  "pidfile": "/var/tmp/aphlict/pid/aphlict.pid"
}

please do not laugh at how terribly i’ve set this up i am not very good at computer

managed to fix this by killing every process that i thought had to do with node. i don’t know why i didn’t think of that earlier.