Errors that belong to no broker
Node.js network error codes explained
5 entries decoded. These are system error codes Node.js reports when a network call fails before any reply arrives. Each page says what the entry means, what it means in trading API work and what to do next, and links to the place it is defined: Node.js documentation, Errors.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
System error codes
5 entries
Raised in your own program, from the operating system.
ECONNREFUSEDConnection refused: no connection could be made because the target machine actively refused it.ECONNRESETConnection reset by peer: a connection was forcibly closed by a peer.ENOTFOUNDDNS lookup failed: a DNS failure of either EAI_NODATA or EAI_NONAME.EPIPEBroken pipe: a write on a pipe, socket or FIFO for which there is no process to read the data.ETIMEDOUTOperation timed out: a connect or send request failed because the connected party did not properly respond after a period of time.
How to cite this
Node.js network error codes explained. Broker API Hub, https://openbrokerapi.com/errors/nodejs, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.