@truedarkness, can you send me a listing of your environment variables? To get that list, just type this command:
set
I was able to produce a similar error by setting an environment variable called HTTPS_PROXY.
C:\Users\russe\AppData\Local\TRIGGERcmdAgent\app-1.0.23\resources\app>set HTTPS_PROXY=8.8.8.8
C:\Users\russe\AppData\Local\TRIGGERcmdAgent\app-1.0.23\resources\app>node src\agent.js --console
Daemon install: false
Logging in with saved token.
Checking if the 5cdde2c3ad333300188e83c4 computer exists.
Error while checking whether computer exists in your account.
Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:80
at ClientRequest.onError (C:\Users\russe\AppData\Local\TRIGGERcmdAgent\app-1.0.23\resources\app\node_modules\tunnel-agent\index.js:177:17)
at Object.onceWrapper (events.js:422:26)
at ClientRequest.emit (events.js:315:20)
at Socket.socketErrorListener (_http_client.js:426:9)
at Socket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
code: 'ECONNRESET'
}
If you do need HTTPS_PROXY set, you might be able to exclude www.triggercmd.com with the NO_PROXY variable:
set NO_PROXY=www.triggercmd.com
Another thing I don't understand - your screenshot shows the agent trying to connect to a host name 8888 on port instead of www.triggercmd.com on port 443.
You've probably already tried this, but maybe uninstall the agent and delete the C:\Users\David\AppData\Local\TRIGGERcmdAgent folder and re-install it.