Exchange Deleted itself & ERRORS AGAIN

Gunbot Shop Gunbot Forum Technical Support Exchange Deleted itself & ERRORS AGAIN

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #9900
    Paul Halliday
    Participant

      Hi

      On logging into my VPS I found that Gunbot had stopped trading. There was a message saying I needed to connect an exchange. On checking the previously connected exchange (Poloniex) was no longer there. I  re-entered all API and log in details and restarted but get the following error stream & I don’t know what it means

      All good…keep calm and Gunbot.
      {“errno”:-4077,”code”:”ECONNRESET”,”syscall”:”read”}
      Error: Error: read ECONNRESET
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.216.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.216.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      {“errno”:-4039,”code”:”ETIMEDOUT”,”syscall”:”connect”,”address”:”104.18.217.39″,”port”:443}
      Error: Error: connect ETIMEDOUT 104.18.217.39:443
      at errorHandler (C:\snapshot\test\Desktop\node14\ctx\js\poloniex.js)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)

      #9906
      Aitor
      Keymaster

        Hi Paul, I have never seen an exchange dissapear from GUI after adding it and clicking “save changes”. Are you sure you saved changes? On another note, that error is related to connection error. Maybe a node between your computer and Poloniex was broken or you or Poloniex was facing connection issues. I guess this was a temporary error, wasn’t it?

      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.
      Contact us