Connect to Bloxberg via websocket connections in web3j

[ghost]

first attempt to address this issue: draft pull request #43

[chinmay241]

More Information can be found here why to adopt WS: https://github.com/internet-sicherheit/caliper-docker/issues/10#issuecomment-638093717

Yes you're welcome 🥇

[chinmay241]

@moekappels Maybe I can help.

Just giving you a direction to think to check out compatibility.

• is Port 80 configured for WSS or WS? You can refer to our Project where we specified default WS Port is 8546

To make sure this project works before connecting and modifying our Bloxberg Node. I recommend the following:

• Run a local Docker of Parity locally. https://github.com/internet-sicherheit/bloxberg-clients/tree/master/parity-docker

You can use this command option in the docker-compose for Parity replacing the existing for your project: --chain bloxberg.json --reserved-peers bootnodes.txt --ws-interface all --ws-port=8546

More Information can be found on https://openethereum.github.io/wiki/Configuring-Parity-Ethereum especially flags

You might have to modify the URL for your project. with the above modification only ws:// is working not the wss://

OR

Refer to the Infrastructure WIKI of our team https://github.com/internet-sicherheit/brl-orga You can see we have a Bloxberg Node running with few ports open you can try those combinations too.