Cannot seem to successfully receive mainnet txs from websocket

Technical Discussion
#1

Hi all,

I’m working on this little tool that monitors/subscribes to incoming transactions, e.g.:

http://wishing-wall.surge.sh?address=NC64UFOWRO6AVMWFV2BFX2NT6W2GURK2EOX6FFMZ&sortByValue=false&max=25

Here I’m monitoring a Binance deposit address to test this out (interesting to see how many people forget messages), and I notice that both unconfirmed and confirmed websockets don’t seem to be working (Alice6, port 7778). But the block subscription websocket seems to be fine (shows the block number at the bottom of the page).

This works fine on the testnet node, but for some reason I can’t seem to get it to work properly with mainnet nodes. Is there anything I should be looking out for? Or is it pointless with Catapult around the corner?

Source if you need a peek.

Much appreciated. :slight_smile:

#2

Are you using nem-sdk? Looks similar problem to https://github.com/QuantumMechanics/NEM-sdk/issues/43

1 Like
#3

Thanks – yep! Does seem to be the same issue that I’m facing.

#4

I’ve even tried setting up websockets manually, but I don’t know how to successfully subscribe (as it’s stomp-based, isn’t it? Not strictly websocket-based?).

#5

Sorted it by connecting to the stomp server with a vanilla websocket rather than using sockjs.

ws://${hostAddress}:${port}/w/messages/websocket

All good.

2 Likes