Closed ghost closed 5 years ago
@kushptlapigarage We have rerouted some links to new ones, apologies for the miscommunication. Please try to use any of the following:
I am still finding issue connecting with Node and seeing the same error.
$ node edgeware-connector.js
2019-07-25 10:27:40 API-WS: disconnected from wss://testnet4.edgewa.re code: '1006' reason: 'connection failed'
2019-07-25 10:27:41 API-WS: disconnected from wss://testnet4.edgewa.re code: '1006' reason: 'connection failed'
2019-07-25 10:27:42 API-WS: disconnected from wss://testnet4.edgewa.re code: '1006' reason: 'connection failed'
I tried with testnet1, testnet6 and testnet4. I can provide more information if you need.
The node is currently down but we will lyk when it is up and fixed!
Is this still an issue after the latest merges to the repo?
Yup, still an issue. Could not connect to any of the testnode listed above.
$ node edgeware-connector.js
2019-08-15 12:50:14 API-WS: disconnected from wss://testnet1.edgewa.re code: '1006' reason: 'connection failed'
2019-08-15 12:50:16 API-WS: disconnected from wss://testnet1.edgewa.re code: '1006' reason: 'connection failed'
2019-08-15 12:50:17 API-WS: disconnected from wss://testnet1.edgewa.re code: '1006' reason: 'connection failed'
Hi All, Just checking in for any updates.
We received some concerns on BlockX Faucet ( https://faucets.blockxlabs.com ) about Edgeware faucet not working.
Will be looking for some direction and happy to get on a call if that helps.
The testnets are up and should be working, but perhaps the API has changed that may warrant your attention. For example, you can see which testnets we are connected to on the Commonwealth UI: https://commonwealth.im/#!/edgeware-testnet/discussions by clicking the "Edgeware Testnet" button.
Connection was successful using WS instead of WSS and port 9944
We are supporting Edgeware by supporting their Faucet at https://faucets.blockxlabs.com
From last week we are finding issue to connect to Edgeware TestNode. We are following the example in Readme.md and using @polkadot/api version 0.80 ( because 0.81 has some issues )
We are seeing below in console log :
Could you please advise how can we fix this ?