unable to get websocket errors

[jorisadri]

When opening the listener and connecting to a wrong url, an error is expected.
Currently only a log is thrown in the console.

To reproduce the behaviour try to connect the listener to a server that does not host a catapult server.

Using javascript and nem2-sdk-typescript-javascript

[dgarcia360]

More information: The error is console logged, but there is no error thrown.

[baskaranc]

Had similar issue, seems only one container started
Check all the 5 containers are running if not clean the data and start again
./clean-data
and start the docker-compose up -d

catapult-service-bootstrap_api-node-0
catapult-service-bootstrap_peer-node-1
techbureau/catapult-rest-server:1.0.7
catapult-service-bootstrap_peer-node-0
mongo

[jorisadri]

I think the issue you descibe is something different than this issue

[evias]

Fixed in PR #63