Open tacticalkeyboard opened 4 months ago
The docker container appears to stop on its own without interaction when installed on Docker/Unraid. The container needs to be manually started again.
Edit: Here's a copy of the logs before the container shut off.
node:events:491 throw er; // Unhandled 'error' event ^ Error: connect ETIMEDOUT 8.8.4.4:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) Emitted 'error' event on ClientRequest instance at: at TLSSocket.socketErrorListener (node:_http_client:494:9) at TLSSocket.emit (node:events:513:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '8.8.4.4', port: 443 } error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Also on Unraid, mine stops after each lookup. I'll start it and leave it unused to see if it stops on its own for me as well.
The docker container appears to stop on its own without interaction when installed on Docker/Unraid. The container needs to be manually started again.
Edit: Here's a copy of the logs before the container shut off.
node:events:491 throw er; // Unhandled 'error' event ^ Error: connect ETIMEDOUT 8.8.4.4:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) Emitted 'error' event on ClientRequest instance at: at TLSSocket.socketErrorListener (node:_http_client:494:9) at TLSSocket.emit (node:events:513:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '8.8.4.4', port: 443 } error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.