syncthing-hooks icon indicating copy to clipboard operation
syncthing-hooks copied to clipboard

can not start hook

Open frankenstein91 opened this issue 3 years ago • 5 comments

node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

GotError: connect ECONNREFUSED ::1:8384
    at onError (/usr/lib/node_modules/syncthing-hooks/node_modules/got/dist/source/request-as-event-emitter.js:140:29)
    at handleRequest (/usr/lib/node_modules/syncthing-hooks/node_modules/got/dist/source/request-as-event-emitter.js:173:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  name: 'RequestError',
  code: 'ECONNREFUSED'
}

Node.js v18.10.0

get this error on start

frankenstein91 avatar Oct 01 '22 20:10 frankenstein91

@frankenstein91 That error is the expected behaviour if syncthing is not running. Maybe you're running it on a different port?

aengl avatar Nov 24 '22 14:11 aengl

@aengl I use port 8384... not sure if it is default or not

frankenstein91 avatar Nov 25 '22 09:11 frankenstein91

That is the default port.

You can check if syncthing is indeed listening to that port by running lsof -i :8384, which should list the syncthing process.

aengl avatar Dec 07 '22 02:12 aengl

COMMAND   PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
syncthing 408 <username>   16u  IPv4  19810      0t0  TCP localhost:8384 (LISTEN)
syncthing 408 <username>   36u  IPv4 192144      0t0  TCP localhost:8384->localhost:58980 (ESTABLISHED)

frankenstein91 avatar Dec 11 '22 15:12 frankenstein91

Looks like everything is correct on your end, I'll investigate some more on my end 🙂

aengl avatar Dec 17 '22 20:12 aengl