Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sample code fails #7

Open
Vasiliy-Bondarenko opened this issue May 26, 2018 · 3 comments
Open

sample code fails #7

Vasiliy-Bondarenko opened this issue May 26, 2018 · 3 comments
Labels

Comments

@Vasiliy-Bondarenko
Copy link

code from readme fails with error:

api error =>  https://t1readonly.eos.io/v1/chain/get_account {"account_name":"myaccount1231548489"}
{ FetchError: request to https://t1readonly.eos.io/v1/chain/get_account failed, reason: connect ETIMEDOUT 35.164.81.64:443
    at ClientRequest.<anonymous> (/Users/info/_sites/eos/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:115:13)
    at ClientRequest.emit (events.js:210:7)
    at TLSSocket.socketErrorListener (_http_client.js:385:9)
    at emitOne (events.js:115:13)
    at TLSSocket.emit (events.js:210:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'FetchError',
  message: 'request to https://t1readonly.eos.io/v1/chain/get_account failed, reason: connect ETIMEDOUT 35.164.81.64:443',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
{ FetchError: request to https://t1readonly.eos.io/v1/chain/get_account failed, reason: connect ETIMEDOUT 35.164.81.64:443
    at ClientRequest.<anonymous> (/Users/info/_sites/eos/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:115:13)
    at ClientRequest.emit (events.js:210:7)
    at TLSSocket.socketErrorListener (_http_client.js:385:9)
    at emitOne (events.js:115:13)
    at TLSSocket.emit (events.js:210:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'FetchError',
  message: 'request to https://t1readonly.eos.io/v1/chain/get_account failed, reason: connect ETIMEDOUT 35.164.81.64:443',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
Error:  { FetchError: request to https://t1readonly.eos.io/v1/chain/get_account failed, reason: connect ETIMEDOUT 35.164.81.64:443
    at ClientRequest.<anonymous> (/Users/info/_sites/eos/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:115:13)
    at ClientRequest.emit (events.js:210:7)
    at TLSSocket.socketErrorListener (_http_client.js:385:9)
    at emitOne (events.js:115:13)
    at TLSSocket.emit (events.js:210:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'FetchError',
  message: 'request to https://t1readonly.eos.io/v1/chain/get_account failed, reason: connect ETIMEDOUT 35.164.81.64:443',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
@jcalfee
Copy link
Contributor

jcalfee commented May 27, 2018

t1readonly.eos.io does not exist anymore .. You'll need a local node .. There is a jungle testnet but I'm not sure what the status is..

@jcalfee jcalfee added the help label May 27, 2018
@Vasiliy-Bondarenko
Copy link
Author

Ok. And how do i use my local node?
And why is it required at all?

@jcalfee
Copy link
Contributor

jcalfee commented May 27, 2018

This looks pretty cool: http://dev.cryptolions.io/

discussion: https://forums.eosgo.io/discussion/493/jungle-testnet

I'm looking for a URL that we can put into config.httpEndpoint...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants